OTO BAM has an input gain control with values from 0 to +15dB. The CC for this function uses the standard 0-127 values. So, these 16 distinct dB values are spread over the 128 CC values as 0dB = CC0, +1dB = CC10, +2dB = CC19, +3dB = CC26…+15dB = CC122.
To cycle back and forth through these dB input gain values requires tediously turning Electra’s knob round and round and round to get from one end of the scale to the other. Is there a way to program a fader to skip the intervening values and only hit the actual dB input gain CC values?
(I do have these 16 dB values entered into the “text overlay” section of the control.)
Here’s an example on how to set it up: create a new control of type ‘LIST’, copy your already made list items to it (with the symbols at the right of the encircled ‘EDIT’), and give it the same message type and parameter as your existing fader. You can then test it side by side.
It still takes about 1/4 turn of the Electra knob to get from one value to the next. What I’d like to have happen is, turning the fader immediately goes from one of my assigned values to the next. Instead, it hits the first value, then stays on that value while I continue to spin the knob until the next value appears. I wish it would allow me to turn the knob less and cycle through the values quicker. The reason I prefer a fader rather than a list control type is, the list starts over at the beginning after I’ve past the highest value. The vid shows what I’m experiencing. (Again, it’s the excessive spinning and spinning of the knob I am wanting to eliminate.)
There may be another way to deal with this, by providing an additional gain list control, that just has fewer (untitled) options, like only 4 or 5 (the nearest correct values to 0, 30, 60, 90 ,120). You use it to change the coarse gain quickly then use the other list control (with titled options) to finetune.
I’m not a fan of lists for various reasons, so I tend not to use those.
Here’s a quick example of using a virtual function, Lua, and a MIDI command to do what you want.
The control in the bottom left corner is the one to play with for this example.
If you look at the Lua code, I am allowing 3 steps between values. If that’s still too much turning, you can drop it to 2 steps (I can talk you through the math if necessary)
3 steps is much better, but it would be interesting to try 2. I poked around the Lua code and changed some 2 values to 3, but it didn’t seem to work. Also, is there a way to add a “+” plus sign in front of the dB values on the display? (Just picking nits here, this is marvelous as-is…)
