VST3 vs VST installs - removing vst2 plugin query

[MFXxx]

Hi all

I've got so accustomed to installing both -- I'm realising nowadays only need vst3 (unless of course the original plugin is vst2 only).

So question - aside from the vt2/vst3 difference and to satisfy my insecurity

I can happily delete/uninstall all vst2 plugins from my plugin folder if my daws/software supports vst 3? Or am I missing something.
I've still got compatibility issues in my mind from years yonder re posts about vst2 over vst3 ie u-he and others, but I'm getting the feeling vst2 is a habit I should now break and save hard drive space?

Looking for peoples thoughts and opinions please.
Of course IM going to back up the plugin folder prior to deletion so a thought simply delete or am i better using the unsintall?

Cubase - Maschine - Reason - Wavelab

Thanks

[jamcat]

Generally, yes, but with a caveat:
While fairly rare, there are some plugins that use only a VST3 shell that actually calls the VST2 plugin and wraps it. If the VST2 plugin is missing, the VST3 plugin will show up blank, in those cases.

I think the KORG Legacy collection is (was?) like that. Same for some Tone2 plugins (again, may no longer apply?)

I would suggest removing the VST2 plugins, but keeping the installers on hand at least until you verify they're real VST3 plugins. It's not really a big deal to reinstall the VST2 version in the unlikely event that the VST3 version stops working. You'll know which, if any, are affected.

Or you could just cull the plugins from your list if they're fake VST3.

[elassi]

Though you don't use Ableton Live I'll share my experience: Live doesn't replace 'old' VST2 by the VST3-versions in a former project.

I've deleted some VST2 due to the reason you named (had them installed in VST3 also) but learned that Live reports a missing plugin instead of using the other/newer format.

[kidslow]

I only install one format and prefer VST3, if available, but over time I have slowly discovered the various VST3 plugins that are not as functional as their VST2 counterparts. Some Plugin Alliance are wonky about presets with VST3. Some HoRNet plugins are better installed as VST. I think Largo is another one.

[Saffran]

I install both formats. Today with very large HD/SSD it doesn't matter as long as your daw can handle it.
It gives an advantage because if i drag in a vst3 instrument to a track and it misbehaves i just delete it and drag in the vst2 instead. That always fix it.
..
Of course there's a checkbox in preferences to hide vst2 if vst3 is present, if you need it.

[sjm]

viewtopic.php?p=8917347

[syntonica]

I use VST2 over VST3 because... reasons... VST3 is an utter mess, it often just wraps the VST2. I only use 3 of there's no 2 available (basically, any newer plugins).

If there's CLAP available, bye bye VST! Much prefer it for open standards goodness.

[maanga]

Some VST 3 plugins will not work if VST 2 version is not installed, even though you do not use VST 2 in the project.
They refer to some details from the VST 2 installation.
Beware.

[CapnLockheed]

I use VST2 over VST3 because... reasons... VST3 is an utter mess, it often just wraps the VST2. I only use 3 of there's no 2 available (basically, any newer plugins).

Straight up. I've spent years setting up my VST folders/subfolders to suit my workflow.
I found out the hard way that, in some DAWS, if both VST2&3 versions are installed, the VST2 version does not show in the proper folder. And, IMHO, trying to organize VST3 plugins to my way of liking is like herding cats. So yeah, I only use VST3 plugins that have NO VST2 versions.

[jamcat]

Straight up. I've spent years setting up my VST folders/subfolders to suit my workflow.

Sunk costs aren’t really a valid reason for sticking with VST2 past its expiration date.

[MrJubbly]

Though you don't use Ableton Live I'll share my experience: Live doesn't replace 'old' VST2 by the VST3-versions in a former project.

I've deleted some VST2 due to the reason you named (had them installed in VST3 also) but learned that Live reports a missing plugin instead of using the other/newer format.

FL Studio is also the same in that regard. As its (currently supported) method for automatic migration is unable to migrate the majority of developers' VST plugins to their VST3 equivalents, even when it's plugin manager is aware the formats are available. The DAW can only migrate a limited number of developers' plugins, who managed to implement correctly matching plugin IDs for both VST/VST3 formats.

I use VST2 over VST3 because... reasons... VST3 is an utter mess, it often just wraps the VST2. I only use 3 of there's no 2 available (basically, any newer plugins).

Straight up. I've spent years setting up my VST folders/subfolders to suit my workflow.
I found out the hard way that, in some DAWS, if both VST2&3 versions are installed, the VST2 version does not show in the proper folder. And, IMHO, trying to organize VST3 plugins to my way of liking is like herding cats. So yeah, I only use VST3 plugins that have NO VST2 versions.

What about when Steinberg inevitably decides that it is time to discontinue the VST3 format, just like it previously did with VST? Are all DAW users expected to go through all of this whole unnecessarily convoluted migration nonsense yet again? No thanks, Steinberg.

If there's CLAP available, bye bye VST! Much prefer it for open standards goodness.

I wholeheartedly agree.

Already, a good +30-40% of my plugins are using the CLAP format only within my new projects (all FabFilter's & many of u-he's plugins). And that percentage will only increase further in the future, as and when updated/newer plugins become available in the CLAP format.