You’re right. @yairadix should maybe edit this comment. it was very early before we had a product with AudioProcessorValueTreeState released.
TL;DR:
The implantation on the gist is agnostic to your parameter system. we use it on older products and newer with great success.
Few caveats to remember:
-
it based on AudioProcessorListener. I’m not sure about future changes as seen here . but it simply keeps track on any parameter changes within the plug-in (not from the host, which is a good thing).
-
you should use begin/end gestures properly for sliders to get a proper behavior. (same goes with AudioProcessorValueTree from my experience).
-
A/B switch or single transaction for entire states aren’t being registered that way.