Several hosts and plugins have implemented side binding with VST 2.4 over the years. MYTH 7: You must have VST3 side chain plugins
But you can usually install them wherever you want (in Windows, directory connections can point to the standard VST3 folder on any drive). Actually, this may be good, because when you create a system disk image, you back up your plugins as well. This is a preference, not necessarily an iron rule. MYTH 6: You must install the VST3 plugins in a specific location on the system drive You can put it as a plug-in in Ableton Live, and then put VST3 in it. See also: best plugins and programs for cleaning sound from noise - MYTH 5: Ableton Live Cannot Use VST3 PluginsĪlthough there is no built-in support for VST3, the Metaplugin DDMF plugin will help to install them. In the end, developers can stop releasing VST2.4 as soon as VST3 captures most of the music market. Please note that the lower part of the graphic icon is different for the two types, and if you click the plugin, the supplier, type and category, as well as a link to the manufacturer’s website are displayed in the information bar at the bottom. If the program supports your VST 2.4 plugins, it will continue to do so unless the manufacturer specifically removes this support. MYTH 4: Now that there is VST3, VST 2.4 plugins are deprecatedĪny host can freely support VST 2.4 and / or VST3 (Fig. But also note that many companies are more actively developing and debugging their versions of VST3, while earlier versions are updated with delays. You can set both types if you want, because plugins themselves usually do not take up much space (their libraries and samples take the place of tools). Remember, the problem is not in the specification itself, but in its implementation.
But during these 10 years, manufacturers improved their code and, in general, fixed any possible errors, so VST3 plugins are as reliable as v2.4.
The VST3 specification has been around for 10 years, and implementation has been relatively slow since the early release was stable. MYTH 3: VST3 is buggy, so it’s best to stick with VST 2.4 now However, VST3 is a standardized method that works as long as it is implemented by both the host (see Figure 1) and the plug-in manufacturer (like MIDI, manufacturers can choose what to support in the VST3 specification – for example, just because the keyboard supports MIDI does not mean that it implements a polyphonic subsequent touch). This is not unique to VST3 Developers were able to implement this using old technologies. Plugins – no, but they can be disabled when the data is not processed. MYTH 2: VST3 plugins are not more effective Plugins VST2.4 and VST3.0 have a common code base, and almost all internal code is identical, therefore, this does not affect the processing of audio material. VST is an interface specification of how the plugin interacts with the host, so performance depends on the code, not the specification. So how important is migration to VST3? Let’s start by breaking down a few myths. They are at least as good as VST 2.4 versions and may even offer some advantages.
Most hosts are more than happy with VST3 versions. If you are impatient and just want to summarize this article, here they are: VST 2.4 plugins will work great for a very long time. Then in May 2018, Steinberg announced that, starting in October, a subset would be eliminated.
In 2013, Steinberg announced that they would no longer support the software development kit (SDK) for the VST2 plug-in format, but the SDK itself would still be available as a subset of the VST3 SDK.