Hi! , Is there any performance differences between VST and VST3 plugins.
Just interested for practical usage reasons. Thanks.

https://www.steinberg.net/en/company...gies/vst3.html

I install both versions, some VST 3's can have quirky, strange behavior. Certain mfgs. don't play nice together & can cause freezing, crashing. Swapping out the vst3 for vst2 can fix the problem.

Thanks for the info ceemusic. I've had problems with VST3 in the past and found I had to use VST's in one of my DAW's, so I was wanting to just go with VST in my plugin folder to also get rid of as many plugin references in DAW as possible.
Thanks again, much appreciated. John.

I avoid VST3 like the plague

Great question! The DSP code itself will be the same (unless a plugin specifically takes advantage of the VST3 enhancements). Otherwise, the VST2/VST3 is just a difference in the way the plugin and DAW communicate. But the DSP code will be the same and hence, should sound identical and perform identically.

It may be, however, that some plugins are more stable as VST2, or some behave better as VST3, you just have to experiment. I should think though that is down to the developers of the plugin and the DAW rather than the differences between VST2 and VST3.

Thanks very much for the info. So it seems I can clear out my VST3 folder and leave it to the VST for my purposes.

I should think 99% of the time, yes! The real big differences in VST3 are (I think) some MIDI features, some sidechaining features and the ability to bypass processing when there is no audio coming in. However, those must all be coded specifically in the VST3 version of the plugin and none of the plugins I use use those features (I've A/Bed the CPU usage of the VST2/3 variants of the same plugins both in use and during silence and never seen any difference).

I keep loading the VST3 versions of plugins sometimes in the hope that something magical will happen, but of course it won't and I use the VST2 versions practically all the time. I don't even think I have any VST3-only plugins and so yeah, if you don't need them, delete them (<== I should follow my own advice!).

VST3 support is a bit spotty on some DAWs. Some features such as factory presets may elicit strange behavior. As for performance, DSP code is often the same across all targets.

One thing I like, according to the Steinberg page is VST3 only uses CPU when audio is passing through and not when audio is not present on the track. Also for those doing surround any plugin can now be configured for surround and not just those plugins who's outputs are configured for it. Those who do surround should like that.

Now for what I don't like. My VST 2 folder is a custom folder on a separate drive with sub folders separated by brand with instruments in yet another sub folder. VST3 puts everything in the same folder separated by category and not where I direct it. Not letting me utilize my own separate custom VST3 folder and sub folders is confusing to me and destroys my work flow. Other than that I like the way they utilize CPU.

Just like to say Thanks lads for your help.
VST3 =
Well! for now anyway.

I always choose VST3, for less CPU usage (it only uses CPU when audio is running through it), and for side chain access.

Where it is filed in the computer is no big deal to me, especially as my DAW lets me create a "greatest hits" list of plug-ins.

Does CPU bypass apply to VST3 instruments too or only FX?

This ^

______________

Also it's to do with side chaining in cubase. VST3, you just click a button on the gui, only in steinberg products though. There is no VST3 only plug in and there is never likely to be.

We all know there's no sonic difference, only aax plug ins have better audio...









troll.jpg

I know certain ToneBooster plugins VST2 version lack Side-chain feature, whilst their VST3 versions have them. This is really strange imo.

I hope this is more of an exception than a rule, cause eventually I'd like to only have VST2 plugins.

Waves plugins are all vst aren't they?

I'm pretty certain only vst3 plugins have the sidechain button.

Does anyone know whether Komplete Kontrol can host VST3 yet??

"The Plague" sounds like a great name for a new VST3 plugin ...

No

Actually, they do VST, VST3 AAX & AU

https://www.waves.com/support/tech-s...upported-hosts

The thread is VST versus VST3.
As answer to " they are vst?" , "no" means : Yes, they are VST3.


Haha, simple but complicated.

Ah!! Well, in that case it was an ambiguous question as I thought they were asking if Waves were VST/VST3 ONLY.

Which is fair to think that way, because quite a lot of indie developers are VST only.

Well, I am getting confused now!

Keep well!

I am using VST3 always. Especially because of CPU. I think that VST3 is probably released for that Feature. Other features like "windows resizing" and "Language support that is standardized" is a little bit more geeky for my taste.

I found a very clean article on the first page when I was in the research process for this topic.
https://inmusician.com/difference-between-vst-and-vst3/

But, as I said, the most important for me in the VST3 was CPU usage.