I just installed a new NVME drive in my machine, as an upgrade to my old 3.5" drive. Windows had gotten real... slow and buggy on my old drive, so I figured this would be a good chance to get a new drive with a fresh install of everything.
Well... this has turned out to be a raging nightmare with Cubase.
I've spent the last several DAYS downloading and installing the latest updates of all my software, vsts', plugins, etc.
I thought I had everything back in place and up and running.
When I open up Cubase 11, it seems fine and it loads ALL of my plugin instruments correctly for the most part.
However, when I try to open up ANY of my existing Cubase projects that I've been working on, Cubase unloads the instrument on certain instrument tracks.
Initially, I thought it was just XLN products, like Addictive Drums and Addictive Keys. Then, upon further exploration of more projects I find that it's certain Kontakt tracks too, BUT NOT ALL Kontakt tracks. Certain IK Multimedia instruments on tracks, but not all. It doesn't make any kind of sense. It's not just the samples it's not loading, it's the whole instrument. Toontrack stuff, and Spectrasonics stuff and other companies instruments load up just as they're supposed to in the projects.
I simply installed everything to the defaults, like I always do, so there was nothing put in different exotic paths or anything like that.
What's odd is that these instruments that won't load WILL LOAD in these projects, BUT ONLY as a new instance. Cubase just can't seem to call them up and load them where they are in existing, tracks.
I've tried everything that I know to do to fix this but nothing works.
Any ideas.
Cubase Not Opening Projects Correctly After New HD Install?
-
mountainmaster mountainmaster https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=153531
- KVRian
- 621 posts since 10 Jun, 2007 from Netherlands
Just a few things I can think of...
If you had very old plugin versions installed on the previous drive which are now updated to the latest versions Cubase may not recognize them anymore.
Or did you have any VST2 instruments installed on your old drive which are now replaced with their VST3 equivalent?
If you had very old plugin versions installed on the previous drive which are now updated to the latest versions Cubase may not recognize them anymore.
Or did you have any VST2 instruments installed on your old drive which are now replaced with their VST3 equivalent?
- KVRAF
- 16806 posts since 8 Mar, 2005 from Utrecht, Holland
Kontakt? You're then missing a specific library.
Still got the old drive? Then not all is lost...
Still got the old drive? Then not all is lost...
We are the KVR collective. Resistance is futile. You will be assimilated. 
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRian
- 978 posts since 10 Feb, 2017 from By the Slot Machines
From what I've seen, Cubase should be upgraded to the newer version to sidestep these kinds of issues. So, maybe upgrading to 13 would work? IDK maybe something to consider.