Some time ago
AudioProcessorParameter(WithID) did not exist.
So I’m curious what you used in the last plugin you coded :
- Classes inheriting AudioProcessorParameterWithID
- Classes inheriting AudioProcessorParameter
- Your own classes (not inheriting AudioProcessorParameter)
And what would you recommend using :
- I’m not sure
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)
I’m a huge fan of ValueTreeState, mostly because you basically get parameter save/restore and undo/redo for free. But like @chkn said, it definitely has some flaws that have to be worked around.
You can try this for undo/redo - https://gist.github.com/yairchu/0a70e553af6176b2f6af
It provides a class
AudioProcessorUndoAttachment which listens to an
AudioProcessor and adds all the parameter changes to an
Thanks everyone !
(I will not close the poll before a few days/weeks, so feel free to vote until then if you haven’t)