This is very annoying as projects from Cubase 13 won’t open with everything in place.
Is there any workaround? Surely we should have the option to locate plugins and VSTis as we do audio files.
If I understand what you’re saying, yes, you can create custom collections of effects, VSTi’s, etc in the VST Plug-in Manager.
Select the category of plugin from appropriate tab, and they you can create new collections (either empty or from others) and copy whatever plugins you want into however many folders you want. You can even have “duplicate” references of one plug-in in multiple folders. Sorry if I misunderstood and you’re referring to something else.
If you are referring to plugins that do not open/load at all than it might be the case that these are VST2s which have to be explicetly enabled in C14:
Studio/Plugin Manager > check the little box down below
1 Like
Ooooh. My train was on the wrong track, yo.
Who knows, let’s see 
The topic Title and the first post are about different things.
And someone who has been a member of this forum for 15 years should have their plugins sussed.
I have my plugins sussed.
I’ll give you an example: in Cubase 13 SSD5 (Steven Slate Drums) is placed in category “Other”
whereas in C.14 it is placed in"Synth".
Hence when I load a C.13 song using this VSTi into C.14 the VSTi isn’t found.
Clear?
I apologise for offending you.
If you’re talking about the Plugin Manager, where plugins are categorised, then however they are categorised has no affect on whether Cubase will load/open/find them.
If we are talking about the Plugin Manager, I use my own collections, which get carried over with each upgrade, and with each new machine I copy the old Settings folder to the new.
And again, it reads as though we’re dealing with two different things. In the first paragraph, it seems to be about collections in the Plugin Manager. The second paragraph seems to be about locations of plugins on the hard drive.
We don’t even know if we’re talking about VST2 or VST3, which Cubase handles differently.
There are some people here who want to help (or want to show off their knowledge - maybe I’m one of them) but cannot do so without some details.
So, that’s a No from me.
As @Googly_Smythe has already pointed out, the behavior you’re describing isn’t attributed to category placement. In my screenshot of the VST Plug-in Manager, you see a category (i.e. “Fx|Reverb”) which the 3rd-party vendor should be using as part of the VST standard. If they don’t, Cubase most likely puts it in “Other” (just based on cursory observation).
So no, it’s really not clear at all what you’re describing. Based on what you’re saying, it sounds like @Reco29’s reply is what you’re looking for. That or you’re using a different version of the plugin in C14 which has a different VST GUID registered.
I think cubase will also put VST2 plugins per default into Other, as I am not aware that categories were a thing in VST2 land…
This would add to the suspicion that this is again a problem where the developer didn’t provide VST2 session compatibility for the VST3 plugin.
To the OP: make sure the VST2 version is also installed, and then activate VST2 plugins as instructed by @Reco29 , this will most likely solve your problem. It has nothing to do with categories, nor is it a Cubase problem, it is a problem of the plugin.
1 Like