Cubase 12

[Trancer]

It seems to me that it was Steinberg who announced the abandonment of support for vst 2 x86 with version 12 of Cubase.

Having a multitude of vst 2 in x86 and especially a multitude of Native Instruments products, Arturia to name a few, it is not interesting to switch to Cubase 12 Pro since 90% of my vst will no longer be usable.

So, we might as well continue with the competition which continues to support vst 2 x86.

[DMG68]

If you know what plugin you want just type the name in the search box at the top, that’s how I add all plugins, I don’t bother with navigating to or through folders.

[T-CM11]

It seems to me that it was Steinberg who announced the abandonment of support for vst 2 x86 with version 12 of Cubase.

Did they? What's your source? I must be imagining those VST2 plugins in my Windows version of Cubase 12.

[Googly Smythe]

It seems to me that it was Steinberg who announced the abandonment of support for vst 2 x86 with version 12 of Cubase.

Did they? What's your source? I must be imagining those VST2 plugins in my Windows version of Cubase 12.

X86 = 32 bit. Not supported since v11, I think.

[PAK]

X86 = 32 bit. Not supported since v11, I think.

Native (to Cubase) 32 bit support was dropped at version 9. Since then you've required a 3rd party bit-bridge to use 32-bit plugins.

[MegaPixel]

If you know what plugin you want just type the name in the search box at the top, that’s how I add all plugins, I don’t bother with navigating to or through folders.

Don't you ever have a little browse and think oooo that would work? Happens to me all the time.

Search is expected and without it things would be OMFG.

[MegaPixel]

It seems to me that it was Steinberg who announced the abandonment of support for vst 2 x86 with version 12 of Cubase.

Having a multitude of vst 2 in x86 and especially a multitude of Native Instruments products, Arturia to name a few, it is not interesting to switch to Cubase 12 Pro since 90% of my vst will no longer be usable.

So, we might as well continue with the competition which continues to support vst 2 x86.

I think you can use Unify to still load up VST 32 bit (x86) plugins in Cubase as it acts as plugin host.

But yes, pretty much nearly every other DAW still supports VST 2 - 32 Bit.

FYI It is possible to get VST 3 (32 Bit).

[EnGee]

In Mac M1, it even blacklisted MassiveX!! Of course all other NI are blacklisted as well. It might NI fault though as in S1 and Logic I can see NI synths (AU version), but I can't see the vst version in S1!

I believe that both Cubase and Logic sit in the extreme opposite end of each other, while most of other DAWs support both formats and also old versions. So, to be safe (at least for the near future), I think it's better to invest in DAWs like Studio One or Bitwig ..etc.

[Googly Smythe]

X86 = 32 bit. Not supported since v11, I think.

Native (to Cubase) 32 bit support was dropped at version 9. Since then you've required a 3rd party bit-bridge to use 32-bit plugins.

I was clarifying something for T-CM11. I switched to 64-bit about 9 years ago.

[chk071]

In Mac M1, it even blacklisted MassiveX!! Of course all other NI are blacklisted as well. It might NI fault though as in S1 and Logic I can see NI synths (AU version), but I can't see the vst version in S1!

I don't think so. Cubase's blacklist is just downright weird. It even blacklists their own plugins. Happened here once at least.

[Googly Smythe]

It seems to me that it was Steinberg who announced the abandonment of support for vst 2 x86 with version 12 of Cubase.

Having a multitude of vst 2 in x86 and especially a multitude of Native Instruments products, Arturia to name a few, it is not interesting to switch to Cubase 12 Pro since 90% of my vst will no longer be usable.

So, we might as well continue with the competition which continues to support vst 2 x86.

I didn't realise that any current developers were not producing 64-bit plugins. Certainly all the big boys do.
And Steinberg stopped support for the VST2 platform about 10 years ago, even though Cubendo stills loads them. I don't think Wavelab, for instance handles any VST2 plugins, just VST3.

[Googly Smythe]

In Mac M1, it even blacklisted MassiveX!! Of course all other NI are blacklisted as well. It might NI fault though as in S1 and Logic I can see NI synths (AU version), but I can't see the vst version in S1!

I don't think so. Cubase's blacklist is just downright weird. It even blacklists their own plugins. Happened here once at least.

GrooveAgent4 in my case.

[chk071]

Always knew there's something funky about it...

[EnGee]

In Mac M1, it even blacklisted MassiveX!! Of course all other NI are blacklisted as well. It might NI fault though as in S1 and Logic I can see NI synths (AU version), but I can't see the vst version in S1!

I don't think so. Cubase's blacklist is just downright weird. It even blacklists their own plugins. Happened here once at least.

I think you are right! I started Reaper and saw the best support for plugins. Pity I can't stand its workflow and shortcuts, otherwise it is the ideal DAW!

Screen Shot 2022-09-05 at 10.41.20 AM.png

vs

Screen Shot 2022-09-05 at 10.49.31 AM.png

[rollasoc]

It's Steinber, they are EVIL...

VST2 x86 aka VST 32 Bit has been dropped though.

That was dropped years ago and we were given ample notice that it was going to happen.