I realise the following is for different devices, and also not exactly lined up with what we have been discussing previously... but some random googling while out and about pulled up some interesting results. Not saying they are useful!
I include it as it seems to add credit to Francs research, and possibly provides some more insight to the format, if the "Roland Two-Byte Model ID" talk is relevant here.
https://mididesigner.com/qa/3881/how-to-send-roland-jx-305-nibbles-2-values-in-sysex-message?show=4693#c4693Code:
From what I see in the 305 manual the sysex messages needs 1 byte for the checksum. This means that the
byte before F7 is the checksum byte. And the 2 bytes before the checksum byte will be the V.
So your syxex message you will have to enter will be something like bla bla 03 V, I think.
To me, the talk on this page seem like the peek and poke commands we used to do on the Dick Smith Wizard computer back in the 80's.
Quote:
Yes, Each sound/patch/part (whatever you call it) is made up of four waveforms that roland calls "tones"
the sysex string i am sending changes the first of the four tones on part 1 of the synth.
Hope that makes sense.
The 10 in the address means the first tone 12 = 2, 14 = 3, 16 = 4.
Also interesting to note that a Roland device can also respond to SysEx .. which I guess is obvious, but may be useful to investigate.
looking at exactly what the SysEx command table is would be interesting. looks like there may be a few:
https://mididesigner.com/qa/3789Quote:
Controls all 313 parameters editable by Sysex,
https://mididesigner.com/qa/3470Code:
-In order to use it you must set unit ID number to "17"
-In order to use it you must set "receive incoming sysex msg" to "On" in global settings
-This template uses massive SYSEX messaging, you should check your midi bus in order to be sure it manages Sysex in the right way.