Page 1 of 1

Document the SysEx messages

Posted: Tue Sep 18, 2012 10:11 am
by slinky
Please!

E.g. what does this mean:
F0 00 01 5F 7A 1E 00 01 00 02 30 09 7E 1C 00 00 F7

Re: Document the SysEx messages

Posted: Tue Sep 18, 2012 2:10 pm
by TheSupport@KMI
Which SysEx messages are you referring to exactly?

Re: Document the SysEx messages

Posted: Wed Sep 19, 2012 9:32 am
by slinky
SupportzKMI wrote:Which SysEx messages are you referring to exactly?


Well, what I'm after is some way to modify the pads, sliders, buttons, etc. without using the Windows/OSX programs. I.e. some way to configure the note, pressure, sensitivity, x, y, x/y return and so on.

I presume the programs just send SysEx messages to modify the preset data stored on the device.

Perhaps this is not the case - how does the preset editor then communicate the new values?

Re: Document the SysEx messages

Posted: Tue Dec 23, 2014 1:40 am
by runtoo75
is there going to be any sort of Max6 SDK or template to use allowing easy mapping of sensor values, I know you guys are pretty nifty Max users and just wondered if there were plans for this. I find this a valuable tool when using my Softstep with Max and this would be great with the QuNeo too.

Re: Document the SysEx messages

Posted: Thu Dec 25, 2014 8:59 am
by jscott
slinky wrote:Please!

E.g. what does this mean:
F0 00 01 5F 7A 1E 00 01 00 02 30 09 7E 1C 00 00 F7


The message "F0 00 01 5F 7A 1E 00 01 00 02 30 09 7E 1C 00 00 F7" means load preset #10.

The documented sysex messages so far are load presets 1-16, tether mode on, tether mode off, and LED toggle.

All of these start with "F0 00 01 5F 7A 1E 00 01 00 02" so that is something of a header.

Fields seem likely to include actually memory addresses in the firmware that are targeted for writing, so it is possible there is not a consistent mapping between firmware versions as new fields are added, and thus documenting everything would be problematic.

Detailed patch data seems to be writable only in bulk, as a complete patch.

Plus a small number of global parameters such as patch select and tether mode, as mentioned. It seems these global parameters can be presumed to remain constant across firmware releases.