Well, in VST3 parameter changes (and thus MIDI mapped to parameters) are handled in the process call. This was seen as progress, as it removes threading issues. Yay! However, if the plug-in stops processing, it also can't process parameter changes anymore. This has caused so many bug reports that I guess quite a few plug-in developers prefer to simply process all the time, and do their own "I do nothing if I don't make any noise". Which then is the same as in VST2. Just a wild - but educated - guess.krans wrote: Wed Aug 31, 2022 8:21 amFor years I've been under the impression that vst3 handles cpu management better than vst2.#rob wrote: Wed Apr 24, 2019 11:05 am But there should be no difference in performance or quality that would make one format preferable over the other.
I thought that a vst3 plugin is shut off when not used, while a vst2 plugin is always a bit on.
My source for this is pretty much any web page regarding vst2 versus vst3, for example this comparison which came up as one of my first search results.
Have I been misled?
(but yes, it was always possible to go into hibernation for a plug-in while there wasn't any audio...)
