Quote:
Originally Posted by MixMonkey
Been giving a bit of thought to the whole encoder/FX paramater situation regarding the need for both stepped values and upper and lower bounds.
I think it might be a better approach to define the SteppedFXParam using 3 values: LowerBound / UpperBound / StepSize.
So, your example would be:
Code:
Widget3 SteppedFXParam 3 0.0 1.0 0.34
The advantages of doing it this way would be:
i) The bounds issue is inherently resolved; the intervening code never outputs a value above 1.0 or below 0.0 (or whatever bounds are set between 0.0 and 1.0). The inc/dec ticks from the encoder are no longer sent directly to the plugin, pnly the absolute values from the intervening code.
ii) It effectively allows control scaling on a per parameter basis; if I set a step size of 0.34, I get 3 steps. If set a step size of 0.005, I get two hundred.
What do you think?
|
Oh the surface it looks great, and indeed I've tried this in the past, but then you run into your favourite and mine -- 3rd party manufacturers
It turns out you need to be able to specify exactly whatever nutso thing they provide