06-12-2025, 08:25 PM
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.
If the librarian doesn't have that capability it may not be possible to get things working in any efficient way.