AudioProcessorValueTreeState - Possible additions?

[jucemarler]

Just as an aside did a getUnnormalizedValue() ever get any approval?

Suggestion: AudioProcessorValueTreeState AudioProcessorParameter getUnnormalizedValue

@jules: can you please give a sign, if this is a safe approach, or are there problems reading the values directly from the AudioProcessorValueTreeState? I use it as a replacement for this kind: https://github.com/ffAudio/ffTapeDelay/blob/master/Source/PluginProcessor.cpp#L135 But it would be more efficient, if I don’t have to do the lookup for the range way more readable code maybe the perfect place to make it thread safe: if the range changes and the value is about to change, I get complet…

It’d be a pretty useful addition for updating some GUI elements in some circumstances as getValue() obviously only returns normalized. It is possible to get around this by overriding the getText() function in some cases to return a textual representation of the full range value but getUnnormalizedValue would be super handy.

I gather this might only be applicable to the classes with a NormalisableRange though like AudioProcessorParameterFloat.

It would be very useful as a virtual function though. Particularly when creating component classes similar to the parameter slider in the demo plugin. So that it is possible to refer to the generalise base class AudioProcessorParameter rather than the specialised versions.

EDIT: I can see the SliderAttachment class sort of handles this situation already via the call to state.getParameterRange(). So doing this may be overkill. Still I think the std::atomic and lambda additions could still be worth some thought ?