--- In
AN1x-list@yahoogroups.com, "jammie" <jammie.emma@...> wrote:
>
> some usb to midi devices dont totally impliment the sysex protocol so that they dont send sysex properly
Ah, that's interesting, and this is the bit I really don't understand. Isn't the protocol only something that the synthesizer and PC software need to know about?
To my understanding, a MIDI adapter needs to convert the MIDI electrical signal into a sequence of bytes, and vice versa. If it can do that for "normal" MIDI messages why can't it do it for SysEx messages?
In other words, why should the content of the data being passed have any relevance to the MIDI adapter?
Derek suggested that the problem might be due to the sheer size of SysEx messages, and I can understand that badly-designed buffering might cause data to be lost, but the problem occurs even with a 6-byte identity request message, and I'm having trouble believing such a short message would be affected by buffering problems.
Can you tell me whether the "SX" LED on the output port shown in Midi-Ox's "Midi Port Activity" window lights up when you're sending SysEx commands? I'm not sure how Midi-Ox detects the SX status, but I find it odd that it will show the SysEx F0 status byte going out in the Output Monitor window, but the SX LED doesn't even flicker.
> i use a midisport 8x8 a 4x4 and a 2x2
Thanks for the recommendation.