Cubase 7.0.7 Side Panel No Longer Functional On Windows 10

[chk071]

Not to unsettle you, but... I would do a full virus scan on your system. Sometimes malware can cause oddities like that.

[wagtunes]

Not to unsettle you, but... I would do a full virus scan on your system. Sometimes malware can cause oddities like that.

I do a scan everyday. It's automatic. So unless my antivirus is missing something, my system is clean.

The only sites I go to on this PC, which is for work only, are 2 forums (this and Gearslutz) Youtube and the vendor sites where I get my VSTs. I do not go to any dodgy sites on this PC and I do not open any emails from people I don't know.

This PC is as clean as a whistle. Unfortunately, Windows 10 has a number of issues that many people have, such as the reboot loop. So I never reboot my PC anymore. I close it down and start it back up no matter what I have to do.

Windows 10 sucks. That's the only problem.

[chk071]

Windows 10 sucks. That's the only problem.

Naaah. Never had anything remotely like you described (I use Reaktor 6 as well). I actually would have said it's the combination of a old DAW (Cubase 7), and a modern OS. After all, Steinberg doesn't support the DAW anymore, and they surely didn't support Windows 10 for it either.

Just a speculation, of course, but, I don't think it's surprising that stuff doesn't work in such a old version.

[wagtunes]

Windows 10 sucks. That's the only problem.

Naaah. Never had anything remotely like you described (I use Reaktor 6 as well). I actually would have said it's the combination of a old DAW (Cubase 7), and a modern OS. After all, Steinberg doesn't support the DAW anymore, and they surely didn't support Windows 10 for it either.

Just a speculation, of course, but, I don't think it's surprising that stuff doesn't work in such a old version.

And of course that's most likely the problem. So Windows 10 sucks for me. Forced to use it unless I wanted to forgo updates and security. And yeah, I get that software doesn't work forever if you upgrade your OS and there's a perfectly viable version of Cubase that will work fine on Windows 10. I just don't feel like shelling out $300 if I don't have to.

[wagtunes]

And there are Windows 10 issues. Look up the Windows 10 reboot problem. I'm not the only one who has it. You not having these issues doesn't mean they don't exist. They do.

[jancivil]

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.

Or so you'd think, but it doesn't have to be true. The delete preferences thing was a thing back to SX1.06 to my experience. Todays Cubase throws a dialog if you've crashed or force quit after a hang to 1) keep the preferences; 2) disable them, ie., temporarily; or 3) delete them.

I never heard anyone try to make a logical case for this or describe any reasoning behind it. I tend to doubt there's anyone who actually understands cause and effect here. The dialog window now suggests more of, not less of a mystery as it has happened more than once that disabling them then quitting and relaunching Cubase solved the issue. IE: with the same preferences now it's all good. So just think of it as magic.

[wagtunes]

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.

Or so you'd think, but it doesn't have to be true. The delete preferences thing was a thing back to SX1.06 to my experience. Todays Cubase throws a dialog if you've crashed or force quit after a hang to 1) keep the preferences; 2) disable them, ie., temporarily; or 3) delete them.

I never heard anyone try to make a logical case for this or describe any reasoning behind it. I tend to doubt there's anyone who actually understands cause and effect here. The dialog window now suggests more of, not less of a mystery as it has happened more than once that disabling them then quitting and relaunching Cubase solved the issue. IE: with the same preferences now it's all good. So just think of it as magic.

Well knowing something about computers, I ran into another problem that made no sense.

After getting everything working, I went to bring up Guitar Rig 5 for one of my tracks and it was gone.

Long story short, I checked the list of blacklisted vsts and Guitar Rig 5 was suddenly on it.

The solution from NI was to delete all the vst files again and let Cubase rescan.

I said f**k this. I went into the XML file, deleted the block of code with Guitar Rig 5, relaunched Cubase and it's fine now.

Throwing out the baby with the bath water is stupid if it doesn't have to be done.

[jancivil]

Cubase 10.5 has developed a dislike of Guitar Rig 5 recently here. It scans a while and then tells me it may have a problem, that I should check the plugin to see... which is completely idiotic. How do I check the plugin while the host has yet to load? VE Pro does not have a problem with it at all, so there is no check the plugin to see, another host is another host period. Eventually it finishes the scan.

Don't get too used to things making sense, that one does (and I think I'll try it for one thing it has blacklisted just for shits and giggles) but...

[wagtunes]

Well, it's happened again. So I went through the whole process that I did the last time when I got it to work. I backed up the Cubase 7_64 folder onto my desktop and then removed the whole thing from the roaming folder. I then started up Cubase and it rebuilt the VST list (took about 20 minutes) and finally started up. I then pulled up a VST and tried to open the side panel and nothing. It still won't work. No VSTs blew up my PC like the last time. I even shut down my computer cold and then did a cold restart. Nothing.

So I have no idea what to do now. I have no way of knowing for certain that if I do get Cubase 10 or 11 or whatever version they're on now that it's going to work.

Any ideas because I'm out of them.

[carlosigls]

You can try Cubase 11 for 30 days if you want to try it to see if it solves your problems. The update are 159 euros.

[flugel45]

... What happened? Worked fine yesterday. No Windows updates since it last functioned correctly.
I have no idea what to do.

And this is exactly why Backup Imaging software exists. I have never been more than a 15-minute restore from a working system, no matter what software glitch screwed up my system. That has been the case for almost twenty years now (since I started making backup images with Norton Ghost).

I'm currently using the FREE version of Macrium to make backup images, because it does everything I need (backup and restore using rescue media). All I have to do is backup once a month and before every major software update and I'm golden.

It's mind-boggling to me how many computer "power users" forego using this utility when this essential safety net is literally free!

[wagtunes]

You can try Cubase 11 for 30 days if you want to try it to see if it solves your problems. The update are 159 euros.

I downloaded the Cubase 11 demo and while there are a few things that aren't where they were in Cubase 7 and while it's a bit more cluttered, I am getting used to it and, so far, it's working fairly well. A couple of little annoyances (recording MIDI sometimes glitches in the middle and record stops) but other than that, seems pretty solid. Will be finishing my first song using it today.

[wagtunes]

... What happened? Worked fine yesterday. No Windows updates since it last functioned correctly.
I have no idea what to do.

And this is exactly why Backup Imaging software exists. I have never been more than a 15-minute restore from a working system, no matter what software glitch screwed up my system. That has been the case for almost twenty years now (since I started making backup images with Norton Ghost).

I'm currently using the FREE version of Macrium to make backup images, because it does everything I need (backup and restore using rescue media). All I have to do is backup once a month and before every major software update and I'm golden.

It's mind-boggling to me how many computer "power users" forego using this utility when this essential safety net is literally free!

I've done imaging. In fact, that's how I went to my SSD drive. The problem with imaging is that every time you make a significant change (like installing a program) you have to reimage, otherwise the last image won't have that program. Now, put this off for the installation of 20 programs and then you have a real pain on your hands having to reinstall all those programs.

Why is this not a great solution? Because creating an image, depending on how much stuff is on your computer, takes hours. Sometimes a whole day. This is not something I want to constantly be doing, especially since I am constantly adding things to my computer.

Case in point, on Dec 24, 2010, this computer and Cubase were working fine. 1 week later, it's not. What if my last image was in July? I mean how often are you supposed to keep creating images of your system?

[flugel45]

Because creating an image, depending on how much stuff is on your computer, takes hours. Sometimes a whole day.

Why in the world would it take hours? You don't need to image your sample drives -- just the C: partition. How big is your C: drive? I keep my C: drive data within a manageable 30-60GB and like I said, it never takes more than 15-20 min tops to image or restore. Frankly if your system partition is in the terabytes, then you're doing it wrong.

In 20 years of personal and corporate IT imaging, I don't recall any system backup job taking more than 45 minutes - and that was on a HUGE server system drive.

If you're experiencing a weird issue with software, the vast majority of the time it will be a recent change to your system drive. The rest of the time, it will be easy to pinpoint to a problem on a data/sample drive and you can make the necessary adjustments.

Bottom line, for a safety net, you only need to regularly back up your C: partition. The other drives can be done much less often (and usually aren't the culprit when stuff suddenly doesn't work).

[wagtunes]

Because creating an image, depending on how much stuff is on your computer, takes hours. Sometimes a whole day.

Why in the world would it take hours? You don't need to image your sample drives -- just the C: partition. How big is your C: drive? I keep my C: drive data within a manageable 30-60GB and like I said, it never takes more than 15-20 min tops to image or restore. Frankly if your system partition is in the terabytes, then you're doing it wrong.

In 20 years of personal and corporate IT imaging, I don't recall any system backup job taking more than 45 minutes - and that was on a HUGE server system drive.

If you're experiencing a weird issue with software, the vast majority of the time it will be a recent change to your system drive. The rest of the time, it will be easy to pinpoint to a problem on a data/sample drive and you can make the necessary adjustments.

Bottom line, for a safety net, you only need to regularly back up your C: partition. The other drives can be done much less often (and usually aren't the culprit when stuff suddenly doesn't work).

Okay, here's the deal. My C drive is 1.35 TB full. 560 GIG of that is in my documents folder. So tell me, what am I supposed to do with all that stuff?