just jumped on Cubase 13 Pro for Windows 11 and the very first scanning of my VST was a disaster: a lot of plug-ins (from EastWes, NI, IK Multimedia, UVI, Arturia, just to name a few of them…) were not recognized
With DP10 and Cakewalk the same plug-ins are correctly seen and usable.
I am really surprised by this: I thought that the company inventing the VST format was pretty much robust with 3rd party VST recognition and usage…
Is there any know issue with Cubase 13 vs. plug-ins recognition ?
Any help is surely appreciated and welcomed.
If you use VST2 plug-ins, check the paths in the VST Plug-in Manager > VST 2 Plug-in Path Settings. Further information contains the Plug-in Report, which can be created also in the VST Plug-in Manager. And of course the Blocklist, as @cubic13 has mentioned already.
Yes, the block list is crazily populated with many plug-ins.
The most absurd thing is that Cubase 13 do not recognize UVI Falcon and Workstation, tagging them as not valid plug-ins!!
No need to say that instead they work perfectly fine both stand-alone and with other DAW (DP and Cakewalk).
So, the point is not that Cubase can’t find the plug-ins, but rather that it finds them but tag them as invalid…
I would try to reactivate them one by one (with a working test for each) from the Blocklist panel. I already did that for one or two VSTis that also ended in it, with success. If i remember well, you would have to select a given plug-in and there should be a Reactivate function available for this.
Can’t be more precise, as it was a while ago : maybe check the manual/online help on the subject.
No, unless you bridge them (32 → 64 bits) with a third party software like jBridge, without any assurance that it will work for all of them, this, with the risk of adding an overall instability of your whole setup…
Mmmh… so , no 32b VST is going to work with Cubase ?
I wonder why on other DAWs they do work…
Nevertheless, the fact that plug-ins like Opus, UVI Falcon, UVI Workstation, several Arturia plug-ins, etc. are not considered valid by Cubase is a huge problem.
It makes the whole SW useless for me
I contacted the technical support and if they can’t solve asap, I will ask for a reimbursement.
Because they still have a bundled bridge with them. In example, reaper has one.
I can just talk about Arturia ones, and this surprises me, as I have the VCollection with many of their VSTis and all have been recognized by Cubase and work as expected.
Cubase hasn’t had 32 bit support since version 8.5 which was around 2016:
I have used Jbridge on occasion and it works well for many but not all things – although I am now wanting to weed out out unstable plugins where I can. I can’t speak for much else but I have had no problem with any Arturia stuff on Cubase 13. Arturia constantly supplies updates for thier plugins through their Software Center application so you might want to check you’re up to date with that. If Arturia items still cause problems you may want to contact their support services for guidance.
I think step 1 is to look for a 64 bit version for each plugin. Most install them to separate 32 and 64 bit folders - read the docs for each to find out where they put them, then delete the 32 bit versions. Also look for VST3 versions.
Step 2 for the older plugins (that we all love :- ) and the slackers that haven’t given you a 64 bit version for current plugins - try bridging.
Steinberg seem to be less tolerant (zero) of 32 bit plug ins but, theoretically, this will make you work harder for a more stable system.
