Okay, I’m really interested in perfect control of a plugin block parameter, but “The Perfect Widget” is a better hook. Also, this isn’t a feature request. I want to solve this with today’s features.
Here’s the use case… We have a parameter that we want to control differently in different variations, depending on the situation.
Case 1: Hardware. We have a pedal, knob or button. Classic use case.
Case 2: Variations. Now, we want to disable the hardware (but track the hardware state), and we want the control to have a specific, value. We want the value to be locked in and not get bumped or saved with an unintended value.
Case 3: Automation. This is similar to the hardware situation, but we follow a different MIDI message from a MIDI sequence. Best practice is likely to start with a default value, until the CC value takes over.
Of course, the hardware use case has the usual sub-cases of continuous rotary knobs vs, absolute value knobs, buttons with and without state indicators, etc.
To start, I expect to have three radio buttons, one for each use case. Next, I might have a widget for each case. One follows hardware, another is the variation widget, and the third is the automation default for each variation. Maybe I hide or lock them. I could add a fourth widget that is large and visible, and tracks the actual state of the parameter.
The final piece of the puzzle is a script that ties the desired widget, value, or MIDI message to the plugin block parameter, depending on the use case.
Is this approach sensible, or would you approach it differently?
All input is appreciated!