Hello,

You don't give much info about the problem.

This sort of thing is more likely to be a problem with the midi interface/connection you're using. USB?? What data are you sending? Possible that the data you send is not getting through, completely, and the bits that ARE getting through are being resolved as a system reset or something.

Geoff

I don't use USB, only classic midi connections. A lots of people said that the rebooting of the akai MPX16 is because of too much midi information coming to him. My plan is to filter all the data messages with the miditech thru box excepted notes and velocity.
But I don't understand how to use the software to configure it.

Hello,

If you're using standard midi cables/connection, then there should not be any problem. Why do you think there MIGHT be a problem with too much data? What quantity of data is being sent?

I have heard (on this forum) of a case where a keyboard was sending a VAST amount of controller info, something (a pedal) was generating way too much, but I think that was a setup involving USB connections which added an extra level of processing

Do you have any means of reporting on the data being sent?

Oh, where is the midi data coming from? What device is generating the data?

Geoff

I don't know if it's a problem of quantity or type of midi message. The fact is that bug is known by akai. But they don't fix that bug. There is a lot of thread on the akai pro forum :
https://c.getsatisfaction.com/akai_professional/topics/mpx-16-how-to-stop-it-constantly-crashing-resetting-in-a-midi-setup

The device who generate the data is a Yamaha MOXF8.

As I understand it, the MOXF8 is a keyboard. I assume you are playing it, and sending the midi data out. Directly, or via computer?

I note from the Akai thread that the akai device is receivind data on Channel 1 only, but may be 'listening' to data on other channels even though it's supposed to be taking no notice of such data. So, which channels are your keyboard using? Make sure it's sending data on Channel 1 ONLY. There may be settings on the keyboard to do this, maybe a 'mode' setting (omni ?)as well.

Apart from that, the problem is most likely to be with the 'continuous' controllers. These can send a LOT of midi data. If you can try NOT to use these controllers, or maybe there's a setting to reduce the resolution of such data, i.e. send one message every 100ms rather than once every 10ms (for example).

I don't know anything about the filter box, so I cannot help re programming that. However, if you're prepared to try filtering out all midi events except notes (which includes velocity anyway) then maybe you'd be OK with trying to turn off the continuous controllers. To see what that does?

Geoff

The MOXF plays solo because I’m playing guitar (I have a source audio soleman to drive it with my foot). The MOXF plays differents channels for sending midi messages to differents midi devices ( no usb, no computer). The channels who plays for the internal generator of the MOXF have the midi out off. I send only midi messages for different devices (Akai MPX16, korg electribe, midi Yamaha Bluetooth for an ipad, strymon timeline, syncman, stonedeaf tremotron) and of course the real-time midi messages (play stop, clocks) are also generate by the MOXF. I don’t use continuous controler.

OK, you're not using any continuous controllers. Hm, I suspect that you may be, and don't realise it.

Apart from that, you have a fairly complicated set-up, and any one of the devices you mention may be your problem, or a number of them together may be making the problem.

Of course, the problem may really be the Akai, which as you know from the thread you refer to, has a firmware problem with the way it copes (or fails to cope) with incoming messages that it OUGHT to be disregarding. Totally.

A number of the devices on your setup may be generating midi data, and all this data is moving through the cables. Different devices may or may not be responding to this data, but all devices will have to at least 'look at' each piece of data even if just to decide if it's something they respond to, or disregard. I assume that most devices do this more cleverly that the Akai, and therefore don't have a problem. The Akai falls over if it gets too much data!

The filter box you have MAY help, it depends on how flexible it is relative to all the devices you have, and how selective it can be as to what it filters out. And of course how 'easy' it is to set up/program (it may not be easy at all?) If you cannot determine the source of any excess data, then you'll have no option but to try to do something with the filter.

Geoff