Is AudioProcessorParameter compatible to an AudioProcessorValueTreeState

[john_henry]

Hi there,

I’m diving in to the parameters and I don’t see a clear picture of how to use Plugin parameters correctly. Is the AudioProcessorParameter (e.g. AudioParameterChoice) compatible with the AudioProcessorValueTreeState for example?

With the AudioProcessorValueTreeState, I only experienced a 0.0 to 1.0 range in all DAWs automation (AU, VST, VST3) and the interval only worked for AU and VST, not VST3, so I’m not sure what’s the best way to…

1. Display Parameters in the DAW parameters with the full range and a Unit
2. For Dropdown menus, etc. show a String in the DAW parameters from a String list

Any hint for resources on this topic would be greatly appreciated.

Johannes

[ttg]

You should’ve dig a little

Restrictions of AudioParameterFloat/Bool/Choice

One of my favorite new features in JUCE 4 is the AudioParameter classes - however there seems to be a major shortcoming with them. Things like getting the raw normalized value and setting the unit label seem to be arbitrarily made private without any way to access them either during or after construction. It seems like it would make a lot more sense to make them either protected (so I can subclass and set the values myself) or make public methods to set these. As it stands now, it seems the only…

If you wish to have simple management you should use AudioProcessorValueTreeState but then you’ll write a lot of lambda (also restrict your code to C++11 supported compilers if that’s something you care about).
If you have few parameters you can enjoy the pre-configured AudioProcessorParameters you’ve suggested but you’ll need to write more management code.
Currently they’re not working as a whole.