+- Conductive Labs Support Forum (https://conductivelabs.com/forum)
+-- Forum: MRCC - MIDI Router Control Center (https://conductivelabs.com/forum/forumdisplay.php?fid=13)
+--- Forum: MRCC Advanced Configuration (https://conductivelabs.com/forum/forumdisplay.php?fid=24)
+--- Thread: USB sysex issues (/showthread.php?tid=1719)
RE: USB sysex issues - _marco_ - 06-06-2025
Hello I am a newbee with the MRCC and got my routings working so far. With the sysex I do not get warm with this device but maybe you have an idea to solve my issue.
Setup:
- v1.1.075
- Laptop Windows11
- microKORG S with SoundEditor
- some Audio interfaces with DIN MIDI ports
The soundeditor is quite old but works fine with my focusrite device or tascam midi interfaces. Actually I bought the MRCC mainly not to recable everything and also use the sysex librarian.
I have read about using lower ports for that so I have connected the USB-B PC to Windows and connected:
- 1 -> P01
- P01 -> 1
When loading all patches with the SoundEditor it works in 1 of 10... cases. It stops in the communication as you can see in the fotos because the patch names are not there but the number of patches. I have restarted the program, restarted the MRCC, restarted the microKORG and it seems there is no dependency. The microKorg shows that it is transmitting data, and also on main MRCC screen there is a green light in the little squares. On the MRCC Routing page I can see some symbols: 0>sX. I have tried also microKorgs external MIDI clock, because with internal sysex seems not to work at all.
There is no other routing then this for the microKorg, and I have saved sysex config in "User 2".
What is also funny is that the more I execute the SoundEditor the higher the current MRCC Preset that is selected but not loaded (because red and not saved yet) when I move to the menu.
I definitely do not have changed the preset with the MRCC GUI.
I also have a WIDI jack bluetooth device connected to MRCC IN2 and OUT2 and Windows 11 bluetooth. The soundeditor crashes if I select the WIDI jack so the MRCC does not just route the communication between WIDI and microKorg. But probably this is another issue.
Do you have an idea what to try to get sysex properly working? Thanks a lot in advance!
RE: USB sysex issues - Jesse Johannesen - 06-12-2025
Usually Sysex issues come up because of a couple of different related reasons. Sometimes they can be solves but nor always. The fact that it sometimes works, but not always seems to indicate that the issue probably lies in SysEx timing and package size. If the data is small (like one packet) then things usually work, but if the packet is big or if the time between packets is too short (as can be the case with USB data) then it gets backed up and overruns the ring buffer. In many cases software like this has options to set package size or adjust the time between packets. If that is the case here I'd shoot for 256 bit packets and 25 - 40ms delay between packets and see if that works. If not increase the delay incrementally and hopefully we hit a sweet spot.
If the librarian doesn't have that capability it may not be possible to get things working in any efficient way.
RE: USB sysex issues - MR.E - 07-17-2025
Sysex works only if sysex librarian is very slow and with lot of pause between sysex blocks. seems like a buffer overflow to me
i have all ports full of vintage synths and sending patchdata or even transmitting synth controller sysex data is a pain...
when i use midiquest i have to use an old emagic interface
pls update soon or i have to find another solution as well...
RE: USB sysex issues - crx091081gb - 09-07-2025
I have a problem with the sysex buffer in that when I try and get bulk dumps back from old hardware synths it drops bytes. I can slow down the flow of midi bytes from soundquest to my hardware rack fine but I can't control how fast the TX81Z chucks back its data. It's 2500 ish bytes for a patch dump. How are people dealing with this? Being able to read in patch data is kind of a deal breaker.
RE: USB sysex issues - Darryl - 09-08-2025
(09-07-2025, 04:03 AM)crx091081gb Wrote: I have a problem with the sysex buffer in that when I try and get bulk dumps back from old hardware synths it drops bytes. I can slow down the flow of midi bytes from soundquest to my hardware rack fine but I can't control how fast the TX81Z chucks back its data. It's 2500 ish bytes for a patch dump. How are people dealing with this? Being able to read in patch data is kind of a deal breaker.
Hello, we've got an updated firmware with completely reworked SysEx buffering, but we've not had time to thoroughly test it so we haven't shared it yet. If anyone wants to give it a try, I'll make a post with the firmware. I'm sure it won't hurt anything, we've been using it day to day for a while now. Look for my next post in this thread.
I'll warn though, that if you are doing a big SysEx dump, you probably will have to stop clock and any other MIDI traffic to prevent issues. Especially if you are merging inputs to the output of the device receiving the SysEx.
All the best,
Darryl
RE: USB sysex issues - Darryl - 09-08-2025
MRCC beta firmware with reworked SysEx buffering. We went deep into the serial buffer setup and adjusted some other buffers that may have been inadvertently changed when we updated some libraries a while back.
There's a code change to adjust the LED brightness method, but that's the only change between this firmware and the last posted beta, otherwise it's just the MIDI and serial buffer adjustments.
Please give it a try and reply on this thread any good or problematic results. Thanks for your patience, we're just a couple of guys and juggling a lot of projects.
MRCC_1.1.094_07-28-2025.zip (Size: 291.82 KB / Downloads: 1)