[Jsynthlib-devel] Standard ways of dealing with varying sysex formats

[Joe E. <jo...@em...>]

Have the JSL developers, as a community, developed some standard ways of 
dealing with various sysex formats?

For example, I've written a rudimentary driver for a device that 
transmits all of its patches in a single sysex message. For this type, 
if I want to move patches around in a bank, I have to move them around 
within that single sysex message.

However, with a device I'm working on now, each patch is sent as roughly 
8 smaller sysex messages. So, for a single patch, I'll have to deal with 
8 separate sysex messages... each containing the settings for a certain 
aspect of that patch. Understandably, each of these sysex messages has 
to contain the patch number and parameter number of what they contain 
data for. So, conceivably, I could swap two patches by merely changing 
the patch numbers contained in the sysex messages themselves... in other 
words, never actually swapping the whole sysex messages to new 
locations. Granted, if I then sent this bank of sysex messages out to 
the actual synth device, the device would receive the patches in a 
non-sequential order... but I don't think the device has a problem with 
that. However, I'm wondering if there's a "gotcha" to this method that 
I'm overlooking.

So, I thought I'd ask if the group has ever discussed (and possibly 
agreed upon) things like "When your synth device dumps it's patches in 
this way, we've found that the easiest way to handle those patches in 
JSL is to write your driver like this....".

Well?

- Joe