Vst Vst3 Difference

[Marine Farinha]

Whenit comes to digital audio and DAWs (digital audio workstations), one of the great advantages they have over physical hardware is how flexible they are. Rather than having to go out and purchase a new piece of kit when you need a new effect, all you have to do is load a plug-in, and off you go.

The first, VST effects, are used to allow the processing of voices or instruments to add effects for improved performance. Imagine you have a vocal that you want to add some reverb to or a guitar that needs some wah-wah on a big solo. You would choose a particular plug-in to apply changes. Some will allow you to apply this during recording, but others will need to be applied afterward to a single or multiple inputs and outputs.

VST3 plugins are a more recent VST version with new features. It was implemented in 2008 and continues the development of the standard. However, there are some important differences between the older VST standard and the newer VST3 one.

When it comes to music production, VST3 plug-ins are also better at sample-accurate automation. Automation is the process of being able to apply changes to your track automatically over a period of time.

For example, if you want to have a fade-out at the end of your track, you might use sample-accurate automation parameters to gradually reduce the volume rather than having to physically move a slider. Sample accurate automation means these changes can be applied with much finer control and accuracy because of better automation data.

MIDI handling is noticeably superior in the VST3 standard. This can range from an entire track right down to a specific note. Additionally, there is enough detail that a specific note can now have a unique ID associated with it to ensure only that note is affected by changes.

Delving deeper into MIDI's new features, VST3 now also features support for multiple MIDI inputs and multiple outputs. This means that multiple MIDI inputs and output ports are supported at once and can be easily changed.

One other big advantage of VST3 is that audio data, as well as MIDI data, can now be passed through a plug-in as audio signals. With the old VST standard, MIDI was the only way to go, but with the VST3 implementation, you can send any kind of audio signal to your plug-in and read it as audio data.

The older VST plug-in had a limit on the number of audio inputs and outputs and MIDI ports that could be handled. Even getting stereo required separate versions of the plug-ins to be installed, with audio inputs and outputs required for each stereo channel.

With VST3 plug-ins that is no longer the case. The new standard can change and adapt to any kind of channel configuration. This makes the process of using VST3 plug-ins with multiple inputs more resource efficient when compared with the older version.

One pro of using VST plug-ins is that it is a long-established technology. This means its biggest advantage is that it's reliable and dependable, and there are a lot of people with a lot of experience with it.

This also relates to the stability of plug-ins. In the early days of VST3, there were concerns that if the plug-in crashed it could pull your whole DAW down with it, with the resultant potential loss of work. The stability of the older VST plug-ins is one reason for their continued longevity.

There are a lot of VST and VST3 plug-ins available for various DAWs. The range and power of VST3 is undeniable, yet there is still plenty of life left in VSTs. Officially, Steinberg has stopped developing the VST standard and is now wholly focused on the VST3 version.

But whether you opt for the newer VST3 or the older VST standard, be sure to make informed decisions. The range and flexibility and improved performance that VST and VST3 plug-ins give to any type of podcast or music production is almost endlessly flexible. The only real limit is your imagination - just plug in and off you go!

The main difference between AU and VST is that AUs are limited to running on Macs only. Other than that, AU plug-ins work in the same way and provide the same type of functionality and improved performance as VST.

Good afternoon. I have bought and downloaded some iZotope plug-ins to help remove mouth noise from my voiceover recordings, but Audition has loaded all of said plug-ins in three separate areas under "Effects": VST, VST3, and AU. (As in, all the same plug-ins are available for me to use in all three areas.)

Would anyone happen to know what the difference is between those three, and what exactly they are? I have tried to Google which one I should use, but can't make heads or tails of all the technical jargon users post on Reddit and Quora. I'm not too fancy with vocal editing yet, and I'm only trying to get rid of a bit of noise without ruining the quality of the recordings. Is there anyone who could possibly explain the differences between those three?

Basically they're different ways of accessing exactly the same plugins - except for AU, which is Mac-only and proprietary. In theory on a Mac, using AU is better because it has lower latency, but you are unlikely to notice the difference in reality. The main obvious differences in the industry-standard VST options is how they are listed in your DAW. In other words, don't worry about it!

I don't know if this is the reason, but I just realized that when I upgraded to this win10 (from win8.1) system I decided to start using vst3 versions of everything when available. Not for need, only to be more current...

sounds consistent with my experience as well. however, in W11, i'm using almost VST3 exclusively and maybe it's the CPU etc but even with stuff that didn't run reliably on W10 on an older machine, the usage meters barely move with either VST2 or 3... that said some products (i've found the Cherry Audio VST3 to consume more resources, not an issue on the new machine, and the Waves Abbey Road Chambers, unusable on W10 & older laptop, now, virtually no resources appear to be consumed on W11 and new machine). so most times, my latency is done to 64-128 samples for recording, sometimes 256, and some old 32-bit ones need 512. mix is still always 2048...

My usage meters hardly light yet I get problems relieved only by increasing the latency. I'm running 12 cores with multi-threading which Cake shows as 24 cores. Mine barely show any height. A nudge up from none. So it's not my processor having the difficulty. I'm believing it's the audio interface itself. Mine is somewhat old, but claims a latency of 5ms peak. I can run very little at 64 but run normally at 128 for most things. Some of the new Synths coming out are proving to be very vst3 resource hungry so that's changing things. I'm very happy with running the vst2 versions instead where available. I have no known need of the vst3 features such as side-chaining very often if ever...

I freeze all my tracks prior to mixing so I mix most of my stuff at 128 as well. Only some of these new issues spoken of have begun upsetting that but now knowing to default to vst2 when possible, I should do better... I hope. This latency dancing is just too much constant fidgeting!

You gotta realize the company responsible is Steinberg. A very Mac eccentric company. And they just like Mac love to force you to keep spending money if you want stuff to be completely compatible.

this is why i only exclude the VST2 in CW when i have the VST3 (i can't remember who else said to do that? ?) but always install the all the 64-bit versions - even aax versions (in case i need them in PT) - then if the VST3 is merely a wrapper (without proper memory management that allows it to degrade nicely when it's corresponding VST2 is missing thus tearing holes in protected memory), at least the file is there even if CW has it on its exclude list...

I've had to avoid using Guitar Sims in real time because my Motu M4 would stutter at any setting below 256 even on a fresh project. My new Zoom L8 can easily do 64 now. I've always used 256 but I think I could now safely go with 128 as a working setting because of the new computer.

Running Cakewalk generally seems no different but I made a video yesterday to see and it was mind blowing editing and rendering. On old machine if I didn't save every 3rd edit Movie Maker ( Vegas) Plat 17 would freeze. The preview was always real slow to refresh and you couldn't preview things like transitions. And rendering ( export) would be 10 plus minutes for a 3 minute video. Yesterday I worked for hours and only saved randomly no freezing, The preview was perfect, and export of a 3 minute video took exactly 80 seconds, I timed it. This is probably mostly because I now have a real Video card. I'm sure it will be a good thing to have with the new Graphics in Sonar.

just an immediate thought is that no demand when audio not passing may save something, but that doesn't mean the plugin will perform better. Needing to constantly turn on/off may have it's own issues. All the calls needed to do this may actually increase the system demands. But I'm not a programmer. I don't know...

3a8082e126