After update to Cubase 13 plugins do not show

Hi everyone,
I just upgraded from Cubase 12 to 13 and now have troubles with some of my plugins that are not showing. I am specifically talking about Kush plugins, FabFilter Pro Q3 and Universal Audio plugins. Other plugins are showing and working just fine.

I am using a Macbook Pro M1 and have the plugins installed, as always in their default VTS/VST3 folders. When I start Cubase 12 again, all plugins are showing and can be used. I’ve tried re-installing FabFilter but still that plugin doesn’t show in the VST plugin-manager. Also a rescan of complete restart of the MacBook or Cubase doesn’t fix the issue.

Anyone any thoughts or same experience?

Thanks in advance for your help.
Sander

1 Like

Hi,

Did you use Cubase 12 in the Rosetta mode? Do you use also Cubase 13 in the Rosetta mode?

Yes, that is correct. I am running in Rosetta mode. I do see a couple of Kush plug-ins in the “blocked” Tab in the plug-in manager. I will upload some images. You see that for instance Fabfilter is installed in VST and VST3 library, but still can’t been selected of round in the plugin manager. Also rescanning doesn’t add this to the selectable plugins. Strange that Cubase 12 doesn’t have this issue and Cubase 13 does…



Hi,

Do you run Cubase 13 in the Rosetta mode too, please?

Hey Martin, thanks for the heads up on Rosetta. Had to select “Open with Rosetta” (Right click in finder—>apps—> Cubase 13) and after that no problems with loading and using the plugins. Problem solved!

1 Like

I have the same but worse. All my Steinberg VST3 instruments such as Halion Sonic, and many of my effects, are not available, and appear on the blocked list. alonf with the VST2 instruments and effects. They are all fine on version 12 I am using Windows 10

Hi,

This is most probably the known Windows issue discussed a lot here on the forum.

I have Sonoma version 14.0 installed on my Mac. Lots of my great Plugins are blacklisted. Please help.

Hi and welcome to the forum,

First of all, macOS Sonoma is not officially supported, yet.

There was a known issue on Apple’s side in the 14.0 version. It has been fixed in 14.1, please, update your system.

If lots of plug-ins are blocklisted, that means, the plug-ins are not Apple Silicon (Native) compatible. Try to update all plug-ins. Some of them may be compatible with the last update.

If it’s still not the case, start Cubase in the Rosetta 2 mode (al Intel emulation). To do so, right-click the Cubase icon in the Applications folder and choose Get Info. In the given window, enable the Use Rosetta mode. Start Cubase.

1 Like

Hello,

I have the same problem. I am running cubase artist 10,5 and 13 both on Mac OS Sonoma (14.2.1 / most recent version) and within 10,5 I have access to all my VSTs but not in 13. When using the VST Manager to show Cubase the location path, it is not willing to include them.

In my case it concerns the following plug ins: LoopMash, Mystic, Prologue, Spector, Hybrid3, MiniGrand, MPC Beats, Velvet, Xpand!2.

Is there someone who can help me on that? Many thanks!

Best regards,

Jona

First Sonoma, update to latest version 14.2.1, then:

Move the Cubase preferences folder to the desktop (including the Cubase 12 folder that C13 imported), maybe keep some templates you may have made.

Ensure all of your 3rd party plugs & VIs are up to date and indeed that they support Sonoma.

Re-boot C13 and let it rebuild everthing. Mine was a pig until I went through this. Even so, it may still blacklist some things, very oddly (like some of my latest versions of Native Instruments for example). Still, I did find that some these could be manually re-enabled without any noticeable downsides.

Import your control room & routing prefs from one of your working templates or recent project.

Open the media bay at point it at the libraries you want to use & let it build that … also set all the Cubase prefs to your liking, audio, midi, metering break points etc.

It may be of use to quit often & between each of these learning stages, if for some reason it locks up en route, you will lose all the chages to date. Quitting it saves the prefs in stages.

So far, C13 is now much improved from what I stared with but still has a few issues, like unexpectedly hanging with some earlier projects, or crashing when changing the sample rate etc.

Hello Profdraper,

Thanks for your answer which I do appreciate. However I am not so technical so I do not understand it really.

No worries. The VSTs are visible and usable in 10.5 but not in 13 using the same OS version (latest Sonoma) - I bought the upgrade from 10.5 to 13.

I will check with Steinberg/Cubase and hope they have a simple answer.

Best regards and happy new year!

1 Like

Where is the Cubase 13 preferences folder? (On Windows 11 here) Thanks. Yes i have the same problem where Cubase is ignoring my custom VST folders for UAD plugins. They show up just fine in Ableton - but Cubase they are hidden. I was going to do a full rescan but nobody seems to know how to do it! the ‘rescan all’ button in Cubase 13 doesn’t actually rebuild the database. it just checks for new plugins. 2 entirely different things.

Open Cubase, open plugin manager and insert your custom folder. I can’t remember exactly (not in front of computer right now) but there is an option there to include any folder you need.

Hi,

Cubase Preferences folders are:
Mac: ~/Library/Preferences/Cubase X
Win: %appData% \Steinberg\Cubase X_64

Where the X is the Cubase version (for example 13).