Can we build a written spec?

[SeanLuke]

I'm finding it difficult to extract from your code what the actual sysex commands are and their interpretation and data embedding. Was thinking of building an editor for Edisyn but didn't want to have to completely reverse engineer the spec. Have you had any opportunity to write down the spec in a formal and human-readable fashion? Here's hoping...

[mungewell]

For the patch file, the format is pretty much explained in the code from line:
https://github.com/mungewell/uno-synth-utils/blob/master/uno_synth.py#L46

There's a parameter count (43 for everything), follow by each parameter in the form of:

• length (0x00 byte data or 0x20 word data)
• address (ie which setting)
• data (byte or word, signed or unsigned)

The rest of the python here is to do conversion into one or two 7bit bytes (cause we're midi) and to wrap in a default value so that you can make a preset out of thin air.

The 'raw' value in the patch file is not necessarily a direct encoding of how the official VST would represent, you will need to do some beautification of the values.

After the settings, there is another block which represents the sequencer pattern which is a little more convoluted. If you use --dump you get a python object/dictionary which also represents how the sequencer elements are stacked together...