The manufacturer should implement this, but this is a significant change compared to VST 2.4. Hierarchical plugin and classification of automation parameters.

Then in May 2018, Steinberg announced that, starting in October, a subset would be eliminated.

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.

They are at least as good as VST 2.4 versions and may even offer some advantages.

So how important is migration to VST3 Lets start by breaking down a few myths.

MYTH 1: VST3 Plugins Are More Effective VST is an interface specification of how the plugin interacts with the host, so performance depends on the code, not the specification.

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.

MYTH 2: VST3 plugins are not more effective Plugins no, but they can be disabled when the data is not processed.

This is not unique to VST3; Developers were able to implement this using old technologies.

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).

MYTH 3: VST3 is buggy, so its best to stick with VST 2.4 now The VST3 specification has been around for 10 years, and implementation has been relatively slow since the early release was stable.

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.

Remember, the problem is not in the specification itself, but in its implementation.

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).

MYTH 4: Now that there is VST3, VST 2.4 plugins are deprecated Any host can freely support VST 2.4 and or VST3 (Fig.

If the program supports your VST 2.4 plugins, it will continue to do so unless the manufacturer specifically removes this support.

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 manufacturers website are displayed in the information bar at the bottom.

In the end, developers can stop releasing VST2.4 as soon as VST3 captures most of the music market.

See also: best plugins and programs for cleaning sound from noise MYTH 5: Ableton Live Cannot Use VST3 Plugins Although there is no built-in support for VST3, the Metaplugin DDMF plugin will help to install them.

You can put it as a plug-in in Ableton Live, and then put VST3 in it.

Actually, this may be good, because when you create a system disk image, you back up your plugins as well.

But you can usually install them wherever you want (in Windows, directory connections can point to the standard VST3 folder on any drive).

Several hosts and plugins have implemented side binding with VST 2.4 over the years.

MYTH 8: VST3 has many interesting new features that are not available in versions of VST 2.4 Potentially yes.

If a product was developed exclusively for VST3, it is likely to take advantage of at least some improvements.

However, during the transition, many developers created VST3 plug-ins with the same basic features as their version of VST 2.4.

MYTH 9: VST3 is no different from VST 2.4.

It is just a hoax; there are no real improvements VST3 is a remake of VST 2.4 and, in fact, is a new platform.

See also: 6 best plug-ins for fixing phase problems Consider some of the benefits: A sample of precise automation.

The manufacturer should implement this, but this is a significant change compared to VST 2.4.

Hierarchical plugin and classification of automation parameters.

Vst 2 Vs Vst 3