Cubase 7.0.7 Side Panel No Longer Functional On Windows 10

[wagtunes]

Ok. then it is the Cubase 7_64 bit folder you need to put on the desktop to let Cubase rebuild.
rsp

Okay, I got rid of everything except the vst plugin info because otherwise Cubase would have to scan through my hundreds of plugins again and that would take all day and those files should have no effect on the side panels opening.

I started up Cubase after deleting everything else and it still doesn't work.

[zvenx]

I hope you moved not deleted.
For me unless there is a bug in the program, relocating the preference folder solves must of the sudden issues for me in cubendo.
Personally I would have tried it without the vst plugin info.
But your call.
rsp

[wagtunes]

I hope you moved not deleted.
For me unless there is a bug in the program, relocating the preference folder solves must of the sudden issues for me in cubendo.
Personally I would have tried it without the vst plugin info.
But your call.
rsp

I made a copy of everything in Cubase 7_64 and put it in a folder on my desktop. I then deleted all those files except for the vst info. So I still have my original preferences.

Removing the entire folder would not have fixed this. I've been using computers long enough to know that. So something else is wrong and for the life of me I can't figure out what.

[wagtunes]

Trying to get in through the mix console (F3) those controls don't open either. So it's not just the side panel.

[wagtunes]

Update:

I bit the bullet and moved the entire folder. I then restarted Cubase and it started going through all my VSTs. It got to Rayblaster2 and not only did Cubase blow up but it shut down my PC.

So, I removed Rayblaster from the VSTs folder and restarted. Cubase eventually started up and everything is back to normal.

Now, here's my question.

If I restore my original defaults folder back, will the problem come back or was it the bad VST that was causing it? I don't want to go through this again.

What do you suggest I do?

[chk071]

I doubt it had to do with Rayblaster. It's much more likely that it had to do with some borked settings. I wouldn't restore the original settings, as it's likely that there's something in there which caused the problem.

[wagtunes]

I doubt it had to do with Rayblaster. It's much more likely that it had to do with some borked settings. I wouldn't restore the original settings, as it's likely that there's something in there which caused the problem.

I restored the original defaults.xml and it still works fine. The problem was apparently in one of the vst files.

[zvenx]

.......

Removing the entire folder would not have fixed this. I've been using computers long enough to know that. So something else is wrong and for the life of me I can't figure out what.

....
rsp

[vurt]

has rb had an update?
odd its gonna mess up for no reason.
but then, computers are arseholes.


glad you got sorted

[wagtunes]

.......

Removing the entire folder would not have fixed this. I've been using computers long enough to know that. So something else is wrong and for the life of me I can't figure out what.

....
rsp

The problem still made no logical sense. The only files I didn't remove were the ones containing VST info. VST info should have no effect on whether or not the side panels open.

So as chk071 said, Rayblaster should not have caused this problem. Therefor, the only other explanation that makes any sense is that the actual Cubase7_064 folder itself got hosed. If that's the case, theoretically, I should be able to replace all the new defaults with my old files and everything should work fine.

Since Rayblaster did in fact blow up my whole PC, I'm not going to do that. But I'm pretty sure now, given what I've seen, that it was the actual Cubase7_64 folder that got whacked. I have never seen a folder get whacked but I guess anything is possible.

Anyway, thanks for walking me through this. I'll know what to do the next time this happens. And given how crappy Cubase is (this hasn't been my only problem) I'm sure it, or something like it, will happen again.

PS - The last Cubase problem I had was after I installed the Loom demo. Cubase was so badly hosed that I had to reinstall it. So yes, plugins can totally screw up your DAW.

[vurt]

The problem still made no logical sense.

as i said above, computers are arseholes.

[Passing Bye]

And given how crappy Cubase is (this hasn't been my only problem) I'm sure it, or something like it, will happen again.

Yeah, it will start happening more and more, I don't think many developers at this point are testing on Cubase 7 and Cubase 7 isn't made to work on latest Windows 10, so you will be SOL pretty soon.

[zvenx]

Ironically there is a sale on loom II and i just tried it and it took down Cubase ..... But I don't think it hosed anything. The later versions are much much less prone to be hosed.

Never the less, every day I back up my preferences elsewhere on mac (not to mention time machine is great for stuff like this) and on pc I back up it up daily to several locations, and at least once a month they are archived to four other locations.

Because after using Cubendo for 19 years and ............ for many years, I know shite happens.. I have seen vst's cause issues beyond what you would consider their scope of influence.

I always have at the very least the previous day backup of preferences to revert to.

I don't believe the folder itself was hosed or can get hosed, but if Cubase sees that folder does not exist it rebuilds or migrates everything. If the folder does exist,it only rebuilds/migrates some things.
Always better to move that folder elsewhere and have Cubendo restart/rebuild with older versions of Cubendo if you have issues.

rsp

[wagtunes]

And given how crappy Cubase is (this hasn't been my only problem) I'm sure it, or something like it, will happen again.

Yeah, it will start happening more and more, I don't think many developers at this point are testing on Cubase 7 and Cubase 7 isn't made to work on latest Windows 10, so you will be SOL pretty soon.

Believe me, I know. I just don't want to spend hundreds of dollars on an upgrade that I really don't need.

[wagtunes]

Well, this is obviously my day to have problems. Finally, after getting Cubase working, I loaded up Reaktor 6 (I have a full license) and tried loading a module but it came up saying it was created in a newer version. Fine, I went to Native Access and updated Reaktor. I then tried to load the ensemble and i get a message that my Reaktor 6 is now in demo mode even though I have a full license for a couple of years now.

Long story short, without doing anything other than starting Cubase up a few times, I finally got rid of the demo message. No logical reason why it was there or why it was gone but it is.

I sometimes hate computers.