Cubase Can't Find Instruments After New HD?

[Domlun]

So... I've been fighting with Cubase for TWO MONTHS now.

I upgraded my hard drive. I've learned the hard way that one SHOULD NEVER EVER EVER EVER do this with Cubase, unless you're into torturing yourself. Load Cubase, work on Cubase and NEVER change anything in your system. Hopefully you can finish all your projects before your PC dies.

I reinstalled WIndows, I reinstalled ALL of my plugins.

When I call up a project, the instruments load, but the sounds/samples are missing. ALL OF THE LIBRARIES ARE EXACTLY WHERE THEY WERE on the old hard drive with exactly the same name on each folder. The names are the same, the paths are the same, yet Cubase can't find or locate anything. Can't find ANY of the Native Instruments stuff, can't find the Toontrack stuff, nothing.

All installs were done by the same default configurations.

I now spend 95% of my time attending to problems like this and only about 5% doing anything creative. This has become my norm. I'm about to give up on all of it, and throw it all in the trash.

I've spent the better half of TWO MONTHS just trying to get Cubase to reassemble ONE SONG project. I thought telling Cubase where everything was on that song would remedy things system wide.

Nope.

Looks like it's going to torture me FOR EACH AND EVERY SINGLE PROJECT!

Not a day goes by anymore without Cubase giving me some MONUMENTAL problem. Not letting me work on, or even call up projects I've spent MONTHS ON! This is far from the only problem I'm having with Cubase, just the one I'm having TODAY. I'm sure it'll be some other major problem tomorrow, as that's how it's been going.

Any suggestions?

[lfm]

...sad story.

I would try a new project and manually create a track and load the same instruments one by one.
- so each instrument can say it does not find it's content and similar
- references in registry or something is probably missing

A daw project has it's way of saving each plugins parameters as are in that project.
- a good host would give user a dialog to look for content when something does not load

I had a similar thing with new computer and Spitfire Audio library though.
- plugins loaded but no sounds

Solved it like this
- starting Spitfire manager as elevated admin the two first of three show installed
- then on last with samples I chose reset and full library
- it had a good working 10 minutes or so and then that red button went away too

So encryption for license or something that is based on that hdd need to be remade, is my assumption.
- check install manager for your plugins

This would make sense only if you run Spitfire manager.

For XLN Audio Addictive Drums 2, it went smoother as I just logged in and pointed to same folder for samples, and their manager just swapped the computer id in my account.

Similar thing with Magix Independence Pro Suite libraries. It did some work on existing samples and done.

It's too long since doing Toontrack stuff, but that was a separate sample installer from the actual plugins if I remember right.

As a last resort if nothing helps, I would run installers for plugins as elevated admin again.
- some installers do not raise themselves to be able to write in registry as needed

[Domlun]

I'm trying a new video card that has NO NVIDIA chips. That was hard to find, but I went and spent MORE MONEY in another attempt to fix my GIANT GRAB BAG OF HORRIBLE ISSUES with Cubase, as I found people online claiming that Cubase conflicts with NVIDIA chips and drivers.

Just got my computer back up and running about 45 minutes ago. Waiting to see if my projects open correctly. I say waiting because we're going on THIRTY MINUTES to open a project and the Cubase loading windows are still going. THIRTY MINUTES TO ONE HOUR is now the average norm for Cubase to open ANY PROJECT for me, sometimes up to TWO HOURS to open a project.

Still loading.

In the last two months I've...
Installed a new hard drive
I've reinstalled Windows
I've reinstalled ALL software, vst's, plugins, libraries, etc. TO THE SAME PATHS WITH THE SAME NAMES
I've replaced ALL of my ram with a different make, incase my original ram was defective

So far...NONE OF THIS has made Cubase work "better". NOPE. It's ONLY made things worse.

I've now replaced my graphics card, and video card drivers (removing and trashing the one I had that was $700)

Fingers crossed that the video card change out will solve my problems, but the going on 45 minutes to open a project still doesn't give me much hope.

Unfortunately NO ONE has any answers. Don't even get me started on the HORRIBLE support I've gotten, or should I say haven't gotten from Steinberg, who REFUSE to talk to me or give me ANY support because my last paid upgrade was Cubase 11, and that's "too old". Doesn't matter that I've been upgrading for years. So... needless to say... that attitude makes me never want to buy ANYTHING from them EVER, no matter how fantastic.

[Domlun]

Project FINALLY opened after about 45 minutes. Project opened up correctly, but now...

Cubase won't make any sound because it can't find my SSL interface.

Never had this problem before. Everything else is accessing my audio interface.

Everything else is working... EVERY OTHER DAW I've opened, has automatically selected my interface.

Just not... Cubase. As... per... usual.

Guess I'll be up all night for HOURS of internet searching to find out how to remedy this latest Cubase problem now. The same way I've spent pretty much EVERY NIGHT of the last two months.

[BertKoor]

What happened two months ago then?

[digging in post history...]

You still use that same "upgrade" harddrive? Was it perhaps a cheap deal? Did you try any utility to asses disk health and measure performance?

Is reinstalling the old one an option? I mean, if that eases the pain instantly...

[dellboy]

Cubase won't make any sound because it can't find my SSL interface.

I am sure you already know this, but anyway, .... select your audio interface in - Studio\ Studio Setup.

I posted here recently about the problems I had with Cubase - slow loading,freezing,crashing. In the end, after much googling, it turned out that Cubase does not like IK Multimedia iRig keyboards. The cure was as simple as disconnecting that keyboard before booting Cubase, since then I have had no problems. I too have had the same frustration of trying to get Cubase to find its sounds.The solution was to go to the drive that the sounds were installed on - in my case,E:\Cubase,WIN64, locate the missing instrument and double click on the sample, and then Cubase does the rest.

[Domlun]

What happened two months ago then?

[digging in post history...]

You still use that same "upgrade" harddrive? Was it perhaps a cheap deal? Did you try any utility to asses disk health and measure performance?

Is reinstalling the old one an option? I mean, if that eases the pain instantly...

No. It was brand new Crucial NVMe drive. I've already resorted back to the old drive. The problem is Cuabase on the old drive was so horrible that I went through the expense and headache of installing a new drive. Everyone said a fresh install of Windows and apps would make a big difference. It didn't. It made everything worse by far.

I'm now back on the old hard drive and it does load my projects correctly. The big problem is when or if. I tried opening up about four different projects last night and each one "opened up" with status windows etc. for OVER AN HOUR before I couldn't take it anymore and force closed them. Before a went to bed, I opened another one. Woke up this morning, over TEN HOURS LATER, to find that it's STILL in the process of opening the project.

Since the new video card made no difference yesterday, I'll be returning that.

I've now replaced the HD, the ram, all of the programs and the video card and Cubase has only gone from terrible to super duper terrible. I don't know what to do at this point. I don't know if I can open ANY of my projects ever again.

I should note that EVERY OTHER application works flawlessly on this machine. Premiere Pro, Photoshop, FL Studio, Ableton, Studio One, Reason, Reaper, all of my standalone vst's. I was NEVER having general computer problems. ONLY problems as it relates to Cubase.

It's Cubase AND ONLY CUBASE that acts like unusable garbage... no matter what I do.

[BertKoor]

The only thing still original is the mobo + cpu.

Better start digging in Windows Performance Monitor:
https://www.windowscentral.com/how-use- ... windows-10