Currently i use AudioProcessorParameter, but i want to use AudioProcessorParameterWithID in the future.
I can’t use AudioProcessorValueTreeState, because it think it has a few design flaws.
- if the parameter uses a interval, the quantized (stepped) values are stored internally.
I think this is problematic, from a hosts perspective, it sets a certain float value, and gets a quantized value back.
(correct me if i’m wrong)
- A function for storing normalized frequency values in a logarithmic way is missing (not skew)
NormalisableRange suggestions