I read that the current SysEx message limit in Lemur is 256 bytes.
Is there any existing way around this? I am trying to write a Lemur interface for my MicroKorg, and am trying to get the patch loading right.
I am able to send a SysEx message to the MicroKorg to trigger it to send a dump of its current program, however the size of the current program is always 297 bytes, and the MIDI implementation for the MicroKorg doesn't allow you to get the patch information in any smaller chunks.
I was thinking that if there isn't a workaround, I will write a MIDI intercept daemon that will catch the incoming SysEx message, and split it apart into smaller custom SysEx messages the Lemur could handle...
SysEx messages too big?
Re: SysEx messages too big?
Currently, that seems to be the only approach.
Max is probably the handiest way to build yr daemon, unless you've got the chops to straight code that suckah. In which case . . . actually in either or any case, there's a few folk working on SysEx stuff on the forum that are currently stymied by the limitation would be absolutely delighted if you make this happen.
Like Santa Claus.
But remember kids! SysEx . . . it's not just for Christmas.
Max is probably the handiest way to build yr daemon, unless you've got the chops to straight code that suckah. In which case . . . actually in either or any case, there's a few folk working on SysEx stuff on the forum that are currently stymied by the limitation would be absolutely delighted if you make this happen.
Like Santa Claus.
But remember kids! SysEx . . . it's not just for Christmas.
Re: SysEx messages too big?
I did a little more research and found this:
http://www.orderedbytes.com/controllermate/
There might not be any real programming involved if this works like I think. It looks like you can have it set up to intercept MIDI messages(or anything else) and then create new MIDI messages(or anything else).
So hopefully I could use it to split the SysEx messages into smaller ones.
The other question is -- is the array size limit in Lemur in general 256 bytes, or is 256 bytes just the maximum size of MIDI_ARGS?
If the general array size limit for Lemur is larger than 256 bytes, it might be possible to write a handler in Lemur to re-join the SysEx chunks into a repaired array.
If the general array size limit for Lemur is only 256 bytes, then you'd have to write some sort of "indicators" into the SysEx message chunks to indicate which data they contained, and write a series of if statements in Lemur based on those to figure out which data it's parsing.
I'm going to play around tonight and see if I get anything...
http://www.orderedbytes.com/controllermate/
There might not be any real programming involved if this works like I think. It looks like you can have it set up to intercept MIDI messages(or anything else) and then create new MIDI messages(or anything else).
So hopefully I could use it to split the SysEx messages into smaller ones.
The other question is -- is the array size limit in Lemur in general 256 bytes, or is 256 bytes just the maximum size of MIDI_ARGS?
If the general array size limit for Lemur is larger than 256 bytes, it might be possible to write a handler in Lemur to re-join the SysEx chunks into a repaired array.
If the general array size limit for Lemur is only 256 bytes, then you'd have to write some sort of "indicators" into the SysEx message chunks to indicate which data they contained, and write a series of if statements in Lemur based on those to figure out which data it's parsing.
I'm going to play around tonight and see if I get anything...
Re: SysEx messages too big?
256 bytes is the array size limit globally I believe, not just MIDI_ARGS.