Lists Are Actually Broken!

I already reported a bug

Wrong Values Sent on “Send Current”

But the issue is with the list control itself.
The user function receives value of the INDEX of the list. And we cannot access the Message Value because the user function is called before setting the value internally.

See the following example:

index - Label - MidiValue
0 - Option A - 0
1 - Option B - 10
2 - Option C - 20

Default Value: 0

I turn the pot slowly to the right:

10959888 lua: ValueFromMessage: 0 Value from function:0.0 
10962298 lua: ValueFromMessage: 0 Value from function:1.0 
10964898 lua: ValueFromMessage: 10 Value from function:2.0
10967098 lua: ValueFromMessage: 20 Value from function:2.0

You can see it returns ValueFromMessage is the previous value. So we have no way to access those values from a LUA script.

If Im doing something wrong, please let me know!

1 Like

You’re not doing anything wrong. I’ve reported the same issue as well already.
The message value indeed lags one behind. I can’t remember my own work around, but check if you are able to trigger the message a second time somehow, to get to the expected value


I tried many things but none worked. This one is really a bummer!


Fixed in the 3.0 testing branch. The Lua values should be 100% in sync with the message values.

1494007 lua: valueFromMessage 0 functionValue : 0.0
1494887 lua: valueFromMessage 10 functionValue : 1.0
1495217 lua: valueFromMessage 20 functionValue : 2.0
1 Like

Thanks! This will make them usable at last!