In the following example, Sysex values from some controls are only partially transmitted, and I can’t explain why this is happening.
The controls were created using the Sysex Editor. I’m using version 4.0.
Level 2 and Play Mode 1 send correct data across the full value range. The remaining controls only send part of the value range.
Level 1: F0 52 00 00 31 07 00 V F7
Level 2: F0 52 00 00 31 07 01 V F7
Level 3: F0 52 00 00 31 07 02 V F7
Level 4: F0 52 00 00 31 07 03 V F7
Play Mode 1: F0 52 00 00 31 06 00 V F7
Play Mode 2: F0 52 00 00 31 06 01 V F7
Play Mode 3: F0 52 00 00 31 06 02 V F7
Play Mode 4: F0 52 00 00 31 06 03 V F7
V = value
Error found. You must have copied around the sysEx somehow, and at the first look all seems right. But then check the underlying json because that is what is sent to the E1.
And for sure, something went wrong : allthough in all the Visual Sysex editors you had assigned each fader to resp. parameter 850, 851, 852 and 853, when looking to the Json of each Sysex, they all kept being assigned to 851.
Same with the selection lists.
I’ve corrected Level 3 and Play mode 2, but left the other ones untouched for you to find out and correct.
Try to reproduce how you got to that result and then inform Martin !
1 Like
Great, thanks for taking the time to check this.
I didn’t make any manual adjustments in the JSON. When creating it, I copied an existing controller and adjusted the SysEx values. Afterwards, I changed the parameter in the value attribute, assuming this would also be automatically updated in the JSON. I didn’t realize there are two separate entries for it, but only one of them has changed.
@martin To reproduce the issue:
- Create a fader with message type SysEx
- Edit the SysEx data with a value
- Change the parameter number
