I have narrowed it down to two recording platforms.I have equal knowledge of both (which is minimal, I'm a Logic/Mac guy) When that happens, you can simply revert to the VST2 version and carry on.I am trying to put together a PC rig for loop construction and virtual synth usage. Consequently, many newly-reported bugs turn out to apply only to the VST3 version of a plugin. Being a new standard, many developers have hit snags while adapting to it. We've been doing it in SONAR for more than a decade, long before the advent of VST3. There is a myth that only VST3 plugins can use external sidechains, but that only applies to Cubase users. VST3 does add some new capabilities, mostly relevant to soft synths, such as support for multiple MIDI ports that can be switched on the fly. It does not dictate how plugins work internally. To answer the original question (what is the difference between VST and VST3?), they are two versions of a written specification describing how hosts (DAWs) and plugins (VSTs) communicate with one another. But even then, your existing VST2 plugins will still work. Eventually, VST3 may be the only choice for new products. Eventually, vendors may decide to stop developing new VST2 plugins just to simplify things for themselves.
But as long as the host supports the VST2 standard, your VST2 plugins will continue to work.
Some new products, in particular those from Steinberg/Yamaha, will only be available as VST3. VST2 is not going to stop working due to obsolescence. However, plugins have always had that ability if the developer chose to implement it. The idea that VST3 is more efficient stems from its feature for shutting off a plugin when there is no data coming in. Developers maintain a common code base for both, with 99.9% of the internal code being identical. In all likelihood you will experience exactly the same performance with either VST2 or VST3.
0 kommentar(er)
