(03-08-2022, 06:03 AM)Stratblue Wrote:(03-04-2022, 03:23 PM)Jesse Johannesen Wrote: Steve is currently working on a solution for this and is very close to having a beta. Do you want to reach out to me via email (support@conductivelabs.com). I would be happy to send it your way once it's ready to try out.
Jesse
Being a complete sysex know nothing, I'm hoping this will be a 'what goes in is what comes out' solution and any chance of getting rid of the 256k limit on chunks I saw referenced elsewhere? Thanks for getting onto this.
Most MIDI devices have limited SysEx buffer sizes, which is why most programs that send large SysEx files have a setting for the max buffer size. For instance, in MIDI-OX you set the SysEx low level output buffer in the SysEx settings, which looks like this:
Once that output buffer size is set, the application will break up the SysEx messages into chunks no bigger than the buffer size so it will pass through MRCC without a problem.
The MRCC isn't a Windows PC, it doesn't even have an operating system. SysEx buffers have to be pre-allocated for every input and there's only so much memory free on a microcontroller. We had space to bump it up to 512 byte buffers.
We also recommend following the manufactures recommendation when they suggest connecting the device directly to the PC for firmware updates, such as Moog does.