time for vst3?

[Tj Shredder]

What is more interesting is the question which developers actually implement the features VST2 does not have? It seems its only Steinberg.
I would love to get the expressions in all VST3 instruments I have, but they are mostly missing.
As new developers are forced to VST3 the situation might change. The lack of Midi support in the early VST3 versions is solved, and slowly DAWs adapt as well.
Unfortunately we will need both for quite a time. If VST3 would function always as intended, I‘d ignore VST2 if possible...
Lets see how it developes the next years...

[sjm]

I've taken to installing both and prioritising the VST3 in my DAW. The reason I install both is that there are some VST3 plugins that don't play nice for whatever reason, seemingly related to preset management. So there's a handful that don't support instant recall when loading projects in FL Studio (Kuassa in particular come to mind). Instead they revert to the default patch when reloading projects. That's a dealbreaker for me.

For the most part, it's fine using VST3. But I install the VST2 just in case so I don't need to reinstall. I can always just delete the .dll if I really want to.

[metaside]

Same here.

Yes, and for different DAWs you have the identical vst-trees. You can build up
you own categories easily. And they are identic for ALL DAWs!

According to the topic: I use VST2 and VST3 in peaceful coexistence,
in the same category-tree. Works wonderful!

Hm, last time I checked it didn't work as expected - either the name prefixes or the folders didn't show up IIRC, but maybe I didn't look in the right place. Guess I have to try it again at some point, thanks!