gustebeast Thinking more about this, I don't think what I suggested is what you want. I need to gather my thoughts on this, but the problem is that CC bindings use the "value" of the midi event as a way to determine the Press or Release of a physical button. The value is not passed on to be used for interesting things by a script. The words I've used in the UI are confusing but we're dealing with three things in the MIDI event:
* MIDI channel number
* CC number
* CC value
In the Mobius binding UI the number you see in the "Value" field is actually the CC number, I should change that.
What scripts have access to are the channel number and the CC number. They don't have access to the CC value since that was used as the press/release indicator, it is not actionable data that is passed on through the system.
For all of the MIDI controllers I use with momentary switches, there would only be two values anyway, 0 and 127. If you wanted a row of switches to send values 1,2,3,4 you would need to program each one independently to send different values on "down" and zero on "up". If you're going to do that, you might as well just use different CC numbers for each one and stick to 0,127 as the value.
It's different for sweepable knobs or sliders that can have a range of values, and the CC value is passed through when the binding is to a parameter. But those are difficult to use with a function binding since you could be calling a script dozens of times each time you touch a control. It would also mean that the script would not be able to use #sustain or #repeat, you're giving up the concept of press/release/sustain in return for just getting the raw CC value and having the script fire every time an event for that CC number is received.
