Almost 2 years and it seems like Undo/Redo with AudioProcessorValueTree is still isn’t ready for “prime-time” or am I missing something?
AudioProcessorValueTree looked very promising but still I see that those threads are still left open and all gets to pretty much same recursive calls (getting asserts), broken redo functionality, etc…
(here @fabian explicitly mentioned there’s something funky due to multiple value changes).
So should I simply create my own UndoManager and avoid using the AudioProcessorValueTree.
That way I can get only relevant calls. since undo/redo is related only to UI elements rather than actual parameters.
(since if you listen to parameter changes also automation might register…)
