EDITOR BUG Not accepting a value [Solved]

Bug reports
1

Hi, When attempting to enter a parameter of 10 when creating a SYSEX message it transmits a value of B. Changing the decimal value to 9 generates a 9 as expected. Changing the decimal value to 11 generates a C.

Screenshot 2026-03-31 at 5.36.46 PM
Screenshot 2026-03-31 at 5.36.46 PM458Ă—542 15.7 KB

Here is the MIDI out.

17:38:16.137 From Electra Controller Electra Port 1 SysEx Waldorf 11 bytes F0 3E 00 00 60 00 00 0B 01 7F F7
17:38:16.185 From Electra Controller Electra Port 1 SysEx Waldorf 11 bytes F0 3E 00 00 60 00 00 0B 02 7F F7

Thanks!

2

Can you add the sysex construction you made as well in the thread, so we see what you are actually wanting to send?

3

Hi, I am new to this, but this is what I am trying to send and I think is what you are asking for.

[

  "F0",
  "3e",
  "00",
  "00",
  "60",
  "00",
  "00",
  "0A",
  {
    "type": "value",
    "rules": [
      {
        "type": "sysex",
        "parameterNumber": 10,
        "parameterBitPosition": 0,
        "byteBitPosition": 0,
        "bitWidth": 7
      }
    ]
  },
  "7F"
]
4

Hi Dave,

welcome here.

I think what you are seeing is a decimal number (10, 11, 12) being translated to hexadecimal format (0A, 0B, 0C). It is Quite common to use hexadecimal when writing SysEx strings, the F0, 3E, and 60 in your message are hex numbers too.

You can find more info on this at Number Systems and Binary Concepts | Electra One Documentation

Let me know if it helps,

Martin

5

In a sysex message assigned to a control, there is no need to add the prefix “F0” nor the suffix “F7”, as they’re being added automatically, but if you mention them (or only one as in this case) it shouldn’t do any harm either.
In any case, I recreated your case (same control with same sysex construction), and I do get the expected 11 bytes:

image
image484Ă—248 4.33 KB

If you are 100% sure your preset is transmitting “B” instead of “A”, please share the preset itself so we can have a closer look what might cause it.

image
image257Ă—494 3.66 KB

image
image435Ă—625 7.5 KB

6

Hello again,

I have posted it as Waldorf uWAVE V.001.

Please look, I am pretty sure I am not mixing up HEX/DEC but I could be.

This is the 1st time I have done sysex on this device and I could have many problems you could all make me aware of. :slight_smile: Thank you so much.

Dave

7

And again I am trying to send an 0A. Ten in decimal. 10.

8

The first example and this preset don’t match up: parameter 10 is a different control type. In the preset it’s an option list but in the first message it was a fader. So I can already guess what is going on…

image
image244Ă—534 5.06 KB

And sure enough, in this control’s sysex an “0B” is mentioned:
[
“F0”,
“3E”,
“00”,
“00”,
“60”,
“00”,
“00”,
“0B”,
{
“type”: “value”,
“rules”: [
{
“type”: “sysex”,
“parameterNumber”: 10,
“parameterBitPosition”: 0,
“byteBitPosition”: 0,
“bitWidth”: 7
}
]
},
“7F”
]

The reason for this mystery is that you have 2 controls with different sysex but the same parameter #10: there is

image
image477Ă—125 2.37 KB

and there is

image
image483Ă—123 3.22 KB

Just ensure you assign different parameters a different number, and your problem will be solved.
I guess your option list should have been given #11 instead of #10 and the one adjacent to it (currently #12, but transmitting “0C”) should have been granted #13 ?

Nicely looking preset by the way!

9

THANK YOU!

I found a couple of other errors too! Thank you for the clarification and the fix.

Dave

1 Like