On 18/11/2019 16:02, andy2no via Groups.Io wrote:
I've seen MIDI-OX mess up handling of sysex dumps - from my Behringer DeepMind 6.? Bome's SendSX worked perfectly.
That's why I tried various programs.
I seem to have read somewhere that Windows MIDI drivers expand "running status" - so that software receives entire self contained MIDI messages instead of a status message followed by a stream of values for it.? If it was receiving a sysex dump but didn't see the header, for example, it could then mangle the data considerably, thinking some of it was running status messages, and adding the extra status bytes.
Possible... Let's see if I can get any hardware to directly read and display the data on the MIDI cables as raw serial input before a solution is found.
I've had success using JSynthLib with my TX7, so I'd try that, to see if it can receive a dump from your DX7:
I'll try that when I come home. But I also do have a TX7 and there is no communication problem with that one at all, in any of the programs I tried. Okay, I haven't sent sysex via MIDI-Ox to it though. But the TX7 can send and receive banks without any issue.
Maybe just connect the DX7 direct to the PC via your no name USB-MIDI cable?? I'm not familiar with the MOTU but it sounds complicated enough to be part of the problem.
Yes, but as I already mentioned in my first post "It's the same if I plug the interfaces directly into the DX7 (the MOTU helps sometimes, my no-name cable for example has issues talking to a CS1x directly, but all is fine if the MOTU relays the data)."
So, yes, of course, always trying to remove as many variables from the equation as possible.
Cheers, Florian
