I'm not sure. Haven't tested anything. But I noticed a significant increase when linking a Peak Controller to Brainworx SSL 4000 E that was unexpected. It could well be the VST itself. Most obvious difference in functionality between VST2 and 3 is that you can right click VST3 parameters and link directly - whereas you have to go through drop down menus to access the same with VST2. But I wondered if there might then be some difference in how the processing is addressed.MogwaiBoy wrote: ↑Fri May 15, 2020 3:56 amWhat's the deal? I've never heard of VST2 vs VST3 for CPU performance - I always just assumed they were identical.Unaspected wrote: ↑Thu May 14, 2020 8:26 pmIndeed, I enjoyed the recent performance boost of FL 20.the-machine wrote: ↑Thu May 14, 2020 7:44 pmIf you mean by performance improvements, FL has improved significantly since around v20.5 or so. Some of my projects CPU usaged dropped 30-60%Unaspected wrote: ↑Thu May 14, 2020 6:18 pm I really hope Image-Line were able to look at efficiency here and improve the system
I mean the CPU load for automation. It can rocket up fast using plugins that are otherwise very efficient during a mix. I have yet to A/B vst 2 with 3 to see if there's an issue there, as I suspect - not with vst 3 itself but FL Studio's handling of such plugins.
I'll have to load up the same plugin as VST2 and see if the increase is the same - in which case, it's the plugin.
Though I've been reporting a number of bugs with VST3s in FL Studio to plugin companies - whereas the VST2 version will work as expected. Things like plugins not being able to save or recall states - this occurred after a recent FL Studio update for certain plugins previously working. Sandman Pro only allows me to automate a single parameter - that's the weirdest bug.
So there's something going on, even if it isn't impacting on performance. In all instances, switching to VST 2 versions solved the issues.