Cubase 12

[zvenx]

not shown where? can you send a screen shot please?
I have reported it but a screen shot of the vst plugin manager would help.
thanks
rsp

[Grumbleweed]

I just checked in Cubase AI 12, and, you're right... it doesn't even show the VST3's in the plugin browser, if the VST2 and VST3 share the same plugin ID. Can only load the VST2 version. I checked with Largo and V-Station.

WTH Steinberg?

Thank you

[chk071]

@zvenx: Here is a screenshot of a project with Z3TA 2, V-Station and Largo loaded. You can see in the plugin browser that there is only one version of the plugins shown (the VST2 version), and, in the plugin manager, you see that the VST2.4 version of the plugins is instantiated (although both are installed and show up in the plugin manager, thus aren't blacklisted either).

Cubase_AI_12_VST2.png

I don't want to claim something wrong, but, I was pretty sure that it was the other way around in former Cubase versions.

Edit: Just tried the update to 12.0.10 (still was one 12.0.0), but, that didn't do it either. Still the same behavior.

[Googly Smythe]

Non-sequiter follows:
The few vst2 plugins I have are all PA (or don't have vst3 versions) - I use them in VEGAS. In Cubase 12.0.10 the vst2s that also have vst3 installed are all black-listed.

[Trensharo]

There are a few DAWs that will skip scanning VST2 plug-ins if a VST3 is available (Cubase, Studio One, etc.), and some that have options to automatically upgrade VST2 instances in projects to VST3 (Cakewalk by BandLab/SONAR).

That's fairly normal.

I generally disable the VST2 plug-ins when a VST3 is available. I will only enable the VST2 if the VST3 is buggy and causes issues, but I have yet to run into an issue with that on a DAW that wasn't developed by MAGIX or MOTU (both of which are worthless when it comes to non-problematic VST plug-in/VI support).

I run into less issues with plug-ins due to consolidation. Instead of cherry picking pieces from all corners of the internet, I tend to bias towards plug-in bundles (Komplete Ultimate, Arturia FX Collection, iZotope MPS, etc.) so I get fairly "even" and predictable support across VST-compatible applicaitons.

I only keep VST2 around because MPC, Maschine and Komplete Kontrol don't have VST3 support.

[zvenx]

@zvenx: Here is a screenshot of a project with Z3TA 2, V-Station and Largo loaded. You can see in the plugin browser that there is only one version of the plugins shown (the VST2 version), and, in the plugin manager, you see that the VST2.4 version of the plugins is instantiated (although both are installed and show up in the plugin manager, thus aren't blacklisted either).

Cubase_AI_12_VST2.png

I don't want to claim something wrong, but, I was pretty sure that it was the other way around in former Cubase versions.

Edit: Just tried the update to 12.0.10 (still was one 12.0.0), but, that didn't do it either. Still the same behavior.

Thanks
Isn't "Standard" a vst collection that you created?
There is usually one called Default created by '... default..lol.. are both vst2 and vst3 shown in that Default list instead of standard?

or is there no Default collection in AI?

rsp

[zvenx]

Non-sequiter follows:
The few vst2 plugins I have are all PA (or don't have vst3 versions) - I use them in VEGAS. In Cubase 12.0.10 the vst2s that also have vst3 installed are all black-listed.

Hmmm
Afaik all PA plugins have vst3 versions.
but yes the vst2 being blacklisted happened in their last update. I emailed them over a month ago and they said it was a known issue they were working on...... all now....
rsp

[zvenx]

@zvenx: Here is a screenshot of a project with Z3TA 2, V-Station and Largo loaded. You can see in the plugin browser that there is only one version of the plugins shown (the VST2 version), and, in the plugin manager, you see that the VST2.4 version of the plugins is instantiated (although both are installed and show up in the plugin manager, thus aren't blacklisted either).

Cubase_AI_12_VST2.png

I don't want to claim something wrong, but, I was pretty sure that it was the other way around in former Cubase versions.

Edit: Just tried the update to 12.0.10 (still was one 12.0.0), but, that didn't do it either. Still the same behavior.

Thanks
Isn't standard a vst list that you created?
There is usually one called default created by '... default..lol.. are both shown in that default list instead of standard?

rsp

Put another way... (does AI work differently) the only Collection Cubase Pro comes with is Default which shows all your vst's installed (except of course those blacklisted)...the others you see there, Beta, Favourites, Essentials and Essential Backups are the ones that I created to only show some, like Essentials are my first call ones.. so they are many plugins that would appear in the left columns and would also appear in Default but not in Essentials because I didn't put them there... and for instance those plugins that do vst3 the 'wrong' way, I f their vst2 version is in the Essentials Collections, I have to remove them and substitute them with the vst3 versions.

Screen Shot 2022-04-22 at 4.23.20 PM.jpg

Hope that makes sense.

Also if I choose Essentials from the plugin Manager it automatically uses that collection when I am choosing a vst in the usual fashion, either by right clicking in the project window or the right pane as you have.. I can of course manually change them there to whatever collections I want.



Does AI work differently?


rsp

[zvenx]

@zvenx: Here is a screenshot of a project with Z3TA 2, V-Station and Largo loaded. You can see in the plugin browser that there is only one version of the plugins shown (the VST2 version), and, in the plugin manager, you see that the VST2.4 version of the plugins is instantiated (although both are installed and show up in the plugin manager, thus aren't blacklisted either).

Cubase_AI_12_VST2.png

I don't want to claim something wrong, but, I was pretty sure that it was the other way around in former Cubase versions.

Edit: Just tried the update to 12.0.10 (still was one 12.0.0), but, that didn't do it either. Still the same behavior.

What happens when you click there? what does it show?
rsp

[chk071]

Stupid me, I totally forgot that you can set up custom plugin lists in Cubase...

This is what it looks like for me:

Cubase_AI_12_plugin_manager_standard_collection.png

The reason why it says "standard" here and "default" for you will be that I use the German language version of Cubase. They're probably both the default plugin lists Cubase creates when you initially scan for your plugins. I didn't create any custom plugin list here for Cubase AI 12 (I did in former versions, but forgot that you can do that when I tried Cubase AI 12).

So, what Cubase obviously does is put in the VST2 versions of the plugins in that default list, when you don't create a custom one. Why that is the default behavior (putting the VST2 versions instead of the VST3 ones in there), I don't know.

[zvenx]

Ahhh.. got ya.. so it doesn't put ALL in the list, just the vst2 ones?
odd.
anyway let me add that to the report.
rsp

[chk071]

Ahhh.. got ya.. so it doesn't put ALL in the list, just the vst2 ones?

Yeah, it looks like it. Unless I miss something. It only seems to add both the VST2 and VST3 versions for plugins which don't share the same plugin ID on the VST2 and VST3.

anyway let me add that to the report.

Thanks, I really appreciate it.

[zvenx]

Ooh but that is how the pro version works. If shows both of they have different vst ids, and if they have the same only shows the vst3 one. You are saying the difference in AI is in the latter case it shows the vst2 one only? The one without the 3 bars next to it in the list right.

Rsp

[Googly Smythe]

Non-sequiter follows:
The few vst2 plugins I have are all PA (or don't have vst3 versions) - I use them in VEGAS. In Cubase 12.0.10 the vst2s that also have vst3 installed are all black-listed.

Hmmm
Afaik all PA plugins have vst3 versions.
but yes the vst2 being blacklisted happened in their last update. I emailed them over a month ago and they said it was a known issue they were working on...... all now....
rsp

Par for the PA course, then. Fortunately, for me, it's not a problem. Others may feel differently.

[Grumbleweed]

See next post!