Cubase 12 and VST2 support?

Is support for VST2 going to be scrapped?

not as far as I can see… it affects the M1 Macs only


That’s correct. Only on native Apple silicon system VST 2 plug-ins won’t be supported.

1 Like

Is there something specific in the Apple “silicon” technology that prevents the use of VST2.4 plug-ins ? Beside this, I’ll quote yourself from the Cubase 12 is coming in 2022 thread :

I smell the beginning of a process, and the feeling isn’t good. First, I’m wondering how eventual Cubase users with an M1 based setup will deal with a VSTis set such as mine…

I feel for them and am rather worried about what is planned beyond Cubase 12 for the other ‘categories’ of users : will what is left of the VST 2.4 compatibility remains ? I consider each of my VSTi as an INSTRUMENT, used since several years, have invested a lot of time/money/skills and continue to use each them as regularly as before. Beside this, and for nearly all of them, there are no equivalent available (I’m especially thinking of Alchemy, Emulator X3 and TruePianos, which are no longer maintained but still prefectly working).

Actually, this is much more important for me than any digression about the forthcoming license management changes. So, more precisions about what is planned in the years to come about the VST 2.4 support would be welcomed…

1 Like

Well, actually we are already deep in the process for years.

Looking at the list in your plug-in manager there is not really much left. Arturia fully supports VST3 with the V-Collection. Lennart Digital has already announced VST 3 support. Camel audio and FXpansion don’t exist any more. I don’t think that you can blame us for not supporting products of companies that are not maintained any more.

1 Like

I’m not talking about ‘supporting products of companies that are not maintained any more’. I’m talking about supporting a standard (VST 2.4) that Steinberg has promoted during several years as a company.

I’ll take the Microsoft example (never thought that I would need to do so, but well…) : they have, more or less, managed to assured us a backwards compatibility since countless years. So yes, I can blame you for not assuring us the same thing : a part of your credibility is in play, on the subject.

At the end, and despite your reaction, if I have to make a choice, I’m sorry to say that I’ll choose my VSTis over Cubase, as again, they are INSTRUMENTS, as well as the Stratocaster that I have since 30 years. I still have a Reaper valid licence that I carefully kept up to date, just in case : so, one customer lost for you. It won’t make an earthquake in Hamburg, I reckon, but still…


the standard is a very old one,
Steinberg promotes the transformation to VST3 since years, already

Are you sure that you have read all my post and, especially, what is related to the the backwards compatibility ?

are you sure that you understand what @Matthias_Quellmann was saying?
VST2.4 is outdated since years and Steinberg supports the vendors since years with the transformation to VST3.
and by now, only the M1 Mac’s are affected from VST2 incompatibility.


I perfectly understood what Matthias said and actually, you don’t answer my inquiry about the backwards compatibility. FYI, the VST 2.4 (2006) has been released AT THE SAME TIME as the VST 3.0 one :

… this, to assure the needed management with what was already existing. I’m not going to endless debates : what I see from Matthias answer is that Steinberg is ready to ditch the VST 2.4 support (it has already starting with the Apple M1 based configurations). Point taken : again, I’ll prioritize my instruments over Cubase. As simple as that…


Just for a better understanding: which instruments exactly are you talking about?

As I said previously (and seeable in my previous screenshot) :

  • Emulator X3
  • Camel Audio Alchemy v 1.55
  • 4Front True pianos v 1.95
  • BFD3 v
  • GSi VB3 v 1.4.1
  • Sylenth 1 v 2.21
  • Loomer Stings 2.5.4

Are you planning to buy a M1 Mac?


Surely not. What is this question for ?

Than you are not affected from unsupported VST2 plugins in the near future…
and you can still use older Cubase versions for compatibility…



Thanks, but I have already the first post of @Matthias_Quellmann. What I’m wondering about is what will happen beyond Cubase 12. Is that so difficult to grasp ?

Your list looks like an old rusty car.
For VB3,4Front, BFD are alternatives on the market, Google is your friend.
The lost of Camel Audio is annoying but it’s a fact. you can use Alchemy in Logic, which can load your Alchemy extensions. Another alternative is Omnisphere, which is in excellent condition incl. maintenance.

this will be pure speculation…
and I guess @Matthias_Quellmann will not answer this question at the moment…

Yep, old and gold rusty car still going ahead…
FWIW, I’m under Windows : no Logic workaround possible. Beside this, none (including Ominsphere) will give me the same sounds (mainly, Alchemy ones) I am used to and retrievable from past projects. And, beside this, Google is certainly not my friend…

I also guessed it. I’ll see what is coming from Steinberg headquarters. Simply, and all my previous posts were about it, as soon as Steinberg ditches the VST 2.4 support, I’ll stop supporting Cubase : as simple as that…


In my opinion we should be more mad at all those plugin vendors, that, since years until this day didn’t care enough about their customers and adapt to the next generation protocol to give us all the benefits that come with VST3.

I was waiting forever for eg. Native Instruments which is a big player to finally go the VST3 route. Same for some other big companies… Though, there are still new or upgraded plugins released that are VST2.x exlcusive.

This irritates me more and it’s good something is finally happening on this side.

1 Like