I'm still thinking about option 1: "Controlling external plugins from Qtractor faders."
1_
There's really no need to color code faders and plugins.
Thanks to the new Alias feature it would be clear just by naming the plugins appropriately.
There's also no need to create a plugin tailored to the Qtractor scale, just choose a plugin that gives you a scale you're comfortable with.
2_
However, if we assign a fader, the boxes that show the value should change to a generic one.
They would no longer be "dB" or "%" but a generic value that admits positive and negative values with at least 2 decimals from the plugins.
This option is perhaps the easiest to develop.
But I find it more confusing than my initial proposal, "Faders in plugins"
I'm still thinking about option 1: "Controlling external plugins from Qtractor faders."
1_
There's really no need to color code faders and plugins.
Thanks to the new Alias feature it would be clear just by naming the plugins appropriately.
There's also no need to create a plugin tailored to the Qtractor scale, just choose a plugin that gives you a scale you're comfortable with.
2_
However, if we assign a fader, the boxes that show the value should change to a generic one.
They would no longer be "dB" or "%" but a generic value that admits positive and negative values with at least 2 decimals from the plugins.
This option is perhaps the easiest to develop.
But I find it more confusing than my initial proposal, "Faders in plugins"