Steinberg news: Stopping VST2 plugin support!

This is the end for CUBASE upgrade. CUBASE PRO 7 forever,
i use A LOT OF VST2.4 in my compositions, so BYE STEINBERG : NO MORE "upgrading".

Now we just need CLAP (clever audio plugin) to be adopted by the industry + a VST2 to VST3 convertor and we will be in the most technologically efficient era of music technology ever

the plugin manufacturers had more than 15 years (!!) to code their plugins in VST3!
It's absolutely time to replace the stone old VST2. VST3 is the future.
Most manufacturers already have vst3 others will follow suit.
Manufacturers can't maintain VST2 plugins that are more than 20 years old. That's just how computer technology works.

I still have VST instruments which are VST2, or my TriplePLay midi pickup which uses mainly my VST2i's, so I will keep my Cubase 11/12 in working condition in the future :-)

This shouldn't come as surprise to anyone. Steinberg announced it a while back and we all knew VST2 would eventually sunset. I began making the move to VST3 plugins early on because anyone that has been doing this for a while could see the transition coming. Like the moves from 16, 32 and 64bit, the end of Quicktime, etc - everything changes. If you're that pressed by this, then keep your current machine running for as long as you can. Just know that moment that you need a new one, there will be some obstacles to circumvent and compatibility with old sessions might be problematic. I make printing any midi or effects that "make the song" to audio (and archiving the midi) a standard practice for this reason alone. It's hard being an early adopter, but it makes moments like these easier to manage. And any company that doesn't get on the update bandwagon, as far as I'm concerned, it's time for me to re-evaluate giving them my business - as painful as that might be. I'm looking at you Native Instruments. You knew this was coming and only a handful are VST3 and nothing is M1 native. Well, Arturia is ready to go (VST3, M1 Native) and I find that I like their products better.

Well reasons 11 12 is screwed then.

as far as I know the novation automap works only with VST2 . It is discontinued but no other solution has been offered

When will halion sonic move to the new license system

Yes, it's time to say good bye. I remember 16bit and the change to 32bit and than the new 64bit... omg omg omg we all die, the world ends tomorrow because we have no more 16bit.

Ahm, NO ;-) We still here and produce music beter than ever before.

Hi, many companies announce their vst3 support...but for some of them we discover that they do not support all the features they had in their vst2 version, this concerns especially the support of midi PC (program change) which has to be handled in a totally different way. Question is why had they not discovered it before, are they bad testers ???
Another situation concerning these vst3 midi PC not supported is the curious case of Korg which provided 2 new plugins this year (Opsix Native and Wavestate Native) directly in vst3 (no vst2 version)... but the midi PC features announced in their user guide, the ability to change preset with a PC, was not running Ok ????
Strange case of poor concern of customers...it is evident they have not even tested this feature, even when written in the product user guide.
So strange, such a giant company...

Thank you. But your headline is misleading. Steinbeg's support for VST2 vill stop in 24 months.

Improvements aside, the cost of moving to Cubase 12 is expensive with all the vst plug-ins updates. My drum software is about $319 (US). For the meantime I am staying with 11. If this effects 11, That 319 bucks may be spent on a more customer focused daw. I have never liked cubase for many reasons. This is man other example of why I coulD not ever recommend Steinberg to anyone.