|
||
Title: problems with incoming sysex dumps >256 bytes Post by tux99 on Jan 23rd, 2019, 6:55pm My scenario: Yamaha RM50 drum synth connected via DIN MIDI to a M-Audio Midisport 4x4 which in turn is connected via USB to a PC running Windows 7 64bit with the latest M-Audio Midisport drivers installed. MIDI-OX (current version) is listening to the MIDI IN device where the RM50 is connected to. When I trigger a rhythm kit sysex dump (468 bytes long including F0 and F7) from the front panel of the RM50, MIDI-OX occasionally (on average once every 3 or 4 attempts) only receives the first 256 bytes. I have tried a different MIDI interface and the problem is the same. Other RM50 users that I have been in contact with report the same issue. To be fair if I try the same thing with the Elektron C6 sysex utility the same problem occurs, so I'm aware that this is not a bug exclusive to MIDI-OX but i wanted to report this here in case you might have an idea what is causing this. What is unusual with the RM50 is that the dump is a single F0->F7 block which is larger than 256 bytes (468 bytes). I checked a few other synths and even though they do dumps of a much larger total size, these dumps never contain single F0-F7 blocks larger than 256 bytes. Is there maybe some kind of bug in the winmm.dll that causes this intermittent problem with sysex blocks larger than 256 bytes? On Linux I have no problem receiving these 468 byte dumps from the RM50 (using the same PC and MIDI interface). |
||
Title: Re: problems with incoming sysex dumps >256 byt Post by tux99 on Jan 24th, 2019, 9:56am Just to add, I have tried changing the incoming buffer size in MIDI-OX but that didn't solve the problem, with 32 bytes buffer, the incoming RM50 sysex dumps still frequently stop at 256 bytes, just like with the default 256 bytes buffer, and increasing the buffer to 512 bytes causes MIDI OX to frequently not show any bytes at all. |
||
MIDI-OX User Forum » Powered by YaBB 1 Gold - SP 1.3.1! YaBB © 2000-2003. All Rights Reserved. |