I just upgraded to Cubase 14 from Cubase 12 and now, I can’t see any of my UAD Plug-ins. Could it be because Cubase 12 is still installed on the computer?
No, Cubase 12 can run fine all by itself and won’t interfere with C14 at all, other than when C12 is present, C14 will attempt to import preferences.
If your current install of UAD is only VST2, you’ll have to enable VST2 in Plug-in manager. I wouldn’t actually do that - rather, reinstall the VST3 versions of UAD. Your OS will determine further troubleshooting.
1 Like
That’s an odd one. Did you manually delete the VST3s or are you using the UAD hardware??
I can’t live without my UAD native stuff now, but from what I can see, UA Connect doesn’t let you decide what to install. It should be installing both VST versions, the AU and the AAX version automatically, so everything SHOULD technically be there. Don’t own any of the hardware so no clue if the installers for those let you choose what to install or not.
Are you on Windows? Maybe they were moved somewhere Cubase isn’t scanning (you can’t move them on a Mac)?
That reminds me, gotta go delete the VST2s and the AAX files from the last time I updated everything.. 
Indeed, and much to my chagrin. I find it particularly irritating that they insist upon creating a “Pro Tools” folder in the user’s Documents folder on MacOS while then setting permissions on the folder to prevent us from deleting it, requiring sudo to remove. Not only should that never be done in a user folder, but they should let us decide what plug-in format we want (at a minimum).
2 Likes
Its one of the reason I no longer have my Arturia collection installed as well. Besides just never using them, the things a total hog as far as resources already, can you NOT install every plugin format I will never use?
Hi,
it’s not clear if you are talking about native UAD plugins or hardware-based plugins. In any case, please get the latest update of your UAD software first. If I am not mistaken, some users reported issues with older UAD versions and C14 which were resolved by the latest update.
1 Like
100%. I’m actually going to skip Arturia altogether when The Beast (Studio M3 Ultra) arrives. In fact, I’m probably going to nix Kilohearts, and even my NI libraries too. I’ll keep them on my MBP (for now) but I’ve been paying explicit attention to what my actual NEEDS are, and I’m going to severely limit what plug-ins I install, and force myself to use the default Cubendo/WL/SL tools which I’m finding are not merely “good enough” but top-notch. @Norbury_Brook made an outstanding point about working within limitations here:
It really resonated with me, as well as discussions with @Reco29 about acquiring gear and plug-ins.
I’ll keep Spectrasoncis, SSL, Audio Modeling, and UAD… but NI, iZotope (as much as I like Iris2), Softube, Slate, EW, UVI, VEP, Vital, Serum, etc are all going bye bye on the new rig.
2 Likes
I thnk the only reason to keep all your plugins is for backwards compatability. I don’t know how much of a thing that is for you , I used to be very concerned about it for clients mix recals etc but over the years, plugins have gone by the way side so despite my best efforts I now don’t worry that much. If a client want’s a recal from 10 years ago they’re genreally wanting to do something different anyway so it’s not actuall been an issue.
Usuall a new machine will illicit plugin housekeeping for me, unfortunately due to AMD’s forwrad thiking of keeping the same socket for 3 CPU revisions I’ve had the same instal now for quite a few years.
A new machine is always a good opportunity to asess where you’re at with plugins/workflow.
M
Indeed, and that’s why I’m keeping the MBP as it is, as well as a current archive of a time-machine backup 
I also stared exporting stems and archiving them as a matter of practice a few years back, just in case
Good advice, thanks!
I am all in when it comes to reducing the number of plugins and optimizing the workflow in general.
What I did: Over the years, I bought many plugins and to be honest, some of them I barely used, others were neglected from the start and others I didn’t bother to test what they can do for me.
Firstly, I tested each and every plugin which I didn’t know well enough and checked what it’s really good for. Actually, as time-consuming as that was - it was worth it. There were quite a few surprises. On the one side, I got rid of many plugins and on the other side, I found about some really cool plugin and features unknown to me up to that point.
Secondly, I categorized the remaining plugins using the Plugin Manager and created streamlined Plugin Collections for different purposes (composing, backwards compatability, bread n butter, out of the box and so on).
Now that I got rid of all this fancy distractions constantly lingering above my head I am no longer at risk to loose myself in too much details but rather focus on the things right in front of me.
Of course, that’s just one way to do it and a personal decision. Although I have been using personalized Plugin Collections from the start - they have never been more streamlined than now.
Sorry @the1soundman : we kind of hijacked your thread… Please let us know if you are any closer to a solution after testing the above suggestions 
2 Likes
Things got back to normal after some updates.
1 Like
Good for you 