I’ve read here that, for non-automatable parameters, it’s better to simply not add a parameter to the AudioProcessorValueTreeState object than to create a sub-class that overrides isAutomatable(), because DAWs may totally ignore that flag. Ok, I get that (for some DAWs, anyway).
But then how do I attach a UI object to the parameter? The various attachments, such as SliderAttachment, use the APVTS to link the Slider to the parameter, including its range and current value, making it much easier to control the slider and set the parameter from it.
Is there another convenient way to tie a parameter and a Slider together, if I can’t make the parameter non-automatable?
In the past, we’ve always been able to set parameters as automatable, meta, discrete, and/or binary, via the constructor for the parameter. But now I don’t see how to do any of this. Why did we lose so much existing functionality? I want to update from JUCE 5.3.2 to 5.4.7, but I’m having trouble making my plugin behave the same way as it did under 5.3.2.