Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
MIDI routing to >2 destinations breaks sysex transfer
#3
I was wondering if you can try to put 'space" between the blocks of data you are sending.
This is particularly helpful for older synths, but might also help with the MRCC.

It is highly likely that the excellent Bome software would have an adjustment to allow it, but if not MidiOx certainly does.

Many synths send there sysex in groups of blocks (often 255 bytes as MS likes that).
MidiOx can separate the blocks with a settable time interval.

Menu View / Sysex then on the Sysex dialog menu Sysex / Configure
You can set a "Delay After F7" (end of sysex / block) in mSec.

If you are sending large sized blocks of Sysex then you can make the Low Level Buffers (output in this case) small - and have quite a few buffers.
Then you can try various times of "Delay between Buffers" to give time for the MRCC to do its stuff.

The Midi 1.0 spec allows certain Midi messages to break the flow of the sysex so machines should be able to cope and not have any problems with breaking up sysex blocks.

I usually try overly large delays just to see if this approach helps.
Then reduce the numbers till it stops working so you know the minimum needed.
Worth the effort as the 'spaces' can slow down the transfers to annoying levels..
 

Hope that helps.
Royce
Reply


Messages In This Thread
RE: MIDI routing to >2 destinations breaks sysex transfer - by Royce - 07-24-2024, 07:59 PM

Forum Jump:


Users browsing this thread:
2 Guest(s)