Hello, there is something weird happening with my cubase 14. I was the colors of the meter in the preferences, and as usually this often make cubase crash. This time it couldn’t load any of my vst3 anymore, it can’t even find them in the vst manager … !
found the bug, cubase know no longer look for vst3 in Common Files/VST3
instead, it looks in Progame Files/Steinberg/Cubase 14/VST3
weird… I need to manually copy each time the vst3
VST3 path is hard coded and shouldn’t change…how do you know it’s looking in the other path? Can you post screencap showing this?
because when I copied my vst3 content from the first location to the second, it just found everything again
I would imagine this is intended for Cubase native plugs only and not third party plugs…maybe some sort of permissions got broken so Cubase can’t see the correct path?
While it may be working there’s no guarantee it won’t cause issues in future. I would try to repair the Cubase install to get the proper path working rather than moving plugs to an incorrect location.
Proper VST3 path is stated clearly to be the original one in this support article.
1 Like
I might try reinstalling Cubase 14
I found the solution was some corrupt plug-ins in the VST3 folder. In my case they were old “WaveShell” plug-ins. I suggest going to this folder and temporarily removing various collections of plug-ins and see if that fixes it.
/Library/Audio/Plug-Ins/VST3/
The downside is I seem to have lost all my WAVES plug-ins, the upside is I don’t even care enough to figure out how to get them back.
My thoughts.
Cubase can have multiple search paths for plugins. Plugin manager allows you to specify additional paths beyond the standard location. These additional paths will be stored in one of the preference files not sure which. These preference files can become corrupted. If the preference file is deleted Cubase may rebuild but it may not be able to put back any manually entered plugin paths which have been stored in them so you just have to re enter the path to your plugins you use.
The paths do have different purposes so whilst your solution works it may give you other issue later such as if you add a new plugin which may not install where you’d expect so it would not be identified.