not really, because my “AnotherProcessorClass” constructor is expecting the AudioProcessorValueTreeState as parameter.
Of course I could change that, do things differently, but I wanted to stress the point that the new way can imply quite a few changes.
I just hope you will keep the old constructor around for a while… (I’m really not against the latest changes, which are most likely an improvement, but it’s quite some work to stay up to date with changes and depreciations lately)