(Edited to clarify my question a bit)
I’m using an AudioProcessorValueTreeState to handle the parameters in my audio plugin. I’m guessing this is still the recommended best practice for this sort of thing? If not, I’m open for suggestions!
What is considered best practice regarding ranges and units for parameters in audio plugins in JUCE?
What I’ve done so far is that I’ve given all unipolar parameters the range 0.0 - 1.0, all bipolar parameters -1.0 - 1.0, and stepped parameters are A…B with step 1 (i e
NormalisableRange<float> (A, B, 1.0f)).
In my editor I create my Sliders and SliderAttachments, and I enable popup displays on my Sliders by calling
Slider.setPopupDisplayEnabled(true, true, nullptr).
But the tooltip will of course only show the “normalized value” of each parameter. So it will say “0.244375”, although I’d prefer to have it say something like “Room Mix: 24%” instead.
I thought that implementing the
textToValue functions when adding the parameters to the value tree would have an effect on the tooltips, but they seem to stay the same?
What would be the recommended way to change the formatting of the tooltips? Maybe I have overlooked something obvious in the API, or maybe I am going the wrong way about this entirely?
I don’t mind completely redoing the way I handle parameters if there’s a better way to do it.