Hi Florian (it's like talking to myself, just better),

On 17/11/2019 20:28, Florian Anwander wrote:

1.) no-name USB-MIDI have only one feature: they increase the income of some chinese factory manager. They don't provide the feature to transfer MIDI (at least they reach the end of their abilities with sysex). So: put it to the dumpster.

Yeah, well... most of the time that one does its job, quite some programming work with a YS200 showed no issues (when relayed through the MOTU), also sending and receiving full dumps to/from an M1 worked out. Also I already have filled their pockets, as long as there is no pressing need, I won't fill the garbage can with it . Anyway, that's why I used the FCA1616 in parallel to test. And also the cheap cable uses class drivers, and the Behringer has its own, different drivers.

2.) what software do you use? for receiving / analysing / sending the sysex data?

Usually / mainly something I have written myself using the WebMidiApi in Chrome. Also DX Manager 5 - I installed that to verify my suspicions, no experience with that, except that I successfully tested if it could talk to my TX7 - and also MIDI-Ox, SoundDiver and "MIDI Sysex file transfer utility". But except for the first, I'm no expert in any of these. I only know that with the cheap USB cable, I can't send bigger sysex with MIDI-Ox (that's why I installed the "MIDI Sysex file transfer utility").

I would usually believe that my own code would be the best source of truth for me, as I know what happens there. But then again, I don't know if the web midi api might already filter out stuff that it doesn't understand, and also of course I don't know if the Windows drivers might hide 'dirty' data.

I have not tried using Linux or a Mac yet - if there is a realistic chance that Windows is to blame, I'll give it shot.

Cheers, Florian