Quote:
Originally Posted by MixMonkey
... It turns out these FX parameters (which usually take the form of a multiway switch or selections from a menu) don't respond to increment/decrement encoders, no matter how many ticks they send. When they are mapped to a Fader7Bit control, they respond just fine.
Which is a problem if your surface only has inc/dec encoders.
Could we have a bit of intervening code to translate the inc/dec ticks (or several ticks) into a series of fixed values (that we can set, both in number and value)? and have this set in the FX map?
With that in place, I think the FX parameter mapping is pretty much put to bed
I'll start adding stuff back to the new build, will let you know when I find out what makes it fall over.
|
Aha !
We need new widgets -- Stepped -- FB_Stepped:
Code:
Widget A3ValStepper
Stepped B0 05 00 40 7f
FB_Stepped B0 05 00 40 7f
widgetEnd
Widget A4ValStepper
Stepped B0 05 00 28 50 7f
FB_Stepped B0 05 00 28 50 7f
widgetEnd
Intended usage -- hardware->Widget -- any hardware widget that has a Press only notion (switch, encoder, etc.)
See any holes ?