KVR Audio

Pouckypluysch · Post by **Pouckypluysch** » Sun Aug 06, 2006 9:54 am

Since yesterday I can't start up Cubase SX3 anymore. The loading process starts after I double click the Cubase-icon. The start screen tells me its initializing VSTi's and such, but everytime it reaches the point of initializing DirectX plugins, the loading process stops.

I tried to re-install Cubase, but that doesn't seem to help. (Uninstalling doesn't even work; I get a pop-up saying that the INSTALLER.LOG-file can't be opened...)

Between this state and the state in which everything was still running smoothly, starting up Cubase showed some problems. Sometimes I was asked to insert the B4 cd-rom, and some plugins were unloadable.

I don't know whant might have caused this. The trouble started after I installed the latest Windows udate, but undoing that didn't help.

I ran a virus scan by AVG, and it did find one somewhere in a Java directory. I removed it, and AVG doesn't find anything anymore. I also ran Spybot and Adware, and though some things were found and removed, it still doesn't help.

I fear I have to reinstall Windows and all my music software, but that would take a lot of time, so I hope I can fix it some faster way. Anyone got a clue?

DevonB · Post by **DevonB** » Sun Aug 06, 2006 10:43 am

I had a very similar problem with Cubase SX 2.2. It got ALL the way to the end of loading all the plugs, and poof, back to desktop with the audio driver now locked. My only fix was to upgrade to SX 3. Considering it took me days to load this system, it was a total bullet dodging effort for me. Looks like you're stuck in the boat I was though. Good luck. Wish I had better words of wisdom for ya. You could try contacting Steinberg support?

Devon

johnnytluxury · Post by **johnnytluxury** » Sun Aug 06, 2006 10:56 am

Did you install a new VST? I had that happen before when I installed an old VST, I had to uninstall and then erase the cubase folder. Uninmstall, reboot, then check to see if cubase left any remannts (including your VST folder, youll have to re-install your VSTs as well) and erase anything related to Steinberg (cubase that is). You can do this or delete the offending VST, if you can track it down. If you cannot uninstall then go brute force and erase the Steiny folder outright, then try to reinstall, and then reinstall your plugs. good luck. Oh and try to find your offending plugin, be it vst, Dx or whatever.

morelia · Post by **morelia** » Sun Aug 06, 2006 11:09 am

I have had a similar thing with scanning on first load with Wavelab. What I did was create a new directory, copy everything from the plugins folder to there, and start wavelab, over and over incrementally adding more plugins until they are all back there.

Pouckypluysch · Post by **Pouckypluysch** » Sun Aug 06, 2006 4:50 pm

Thanks for the replies.
I upgraded some NI stuff, but that was actually after things started to get messy. It didn't get any messier since, I reckon.

I will try to reinstall vst's and Cubase again, but as I get thrown out at the point of initialising DirectX plugins, I fear that it's not the vst's that cause the troubles. And I don't run any DirectX plugs, so there's nothing to uninstall there.

Bugger.

Foxglove · Post by **Foxglove** » Sun Aug 06, 2006 5:04 pm

You probably have a corrupted .xml file in Cubase's Data folder. Here's your fix;

1. Go to C:\Documents and Settings\Foxglove\Application Data\Steinberg\Cubase SX 3

2. Delete the file VST Plugins.xml

3. Run Cubase again.

If that doesn't work, try deleting all the .xml files. They will all be made again once Cubase starts up, but you will loose all your window layouts, preferences, etc.

Lord Snarebottom · Post by **Lord Snarebottom** » Sun Aug 06, 2006 5:04 pm

Pouckypluysch wrote:I don't know what might have caused this. The trouble started after I installed the latest Windows udate

You mean you don't have a drive image or system restore on your system drive?

Q: If your setup was working fine (and you weren't prudent enough to have the steps listed in the previous sentence in place), why oh why do a Windows update?

Chump. I guess you'll mend your ways now. I use Acronis True Image for imaging, it works great and restoring from external drives is a snap. Turn on system restore for your system drive, as well.

Highvoltage · Post by **Highvoltage** » Sun Aug 06, 2006 5:08 pm

morelia wrote:I have had a similar thing with scanning on first load with Wavelab. What I did was create a new directory, copy everything from the plugins folder to there, and start wavelab, over and over incrementally adding more plugins until they are all back there.

i did this exactly quite a few times, and it works for me too.
just to find which plugin causes the problem.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Sun Aug 06, 2006 5:43 pm

[DELETED]

Foxglove · Post by **Foxglove** » Sun Aug 06, 2006 6:08 pm

morelia wrote:I have had a similar thing with scanning on first load with Wavelab. What I did was create a new directory, copy everything from the plugins folder to there, and start wavelab, over and over incrementally adding more plugins until they are all back there.

Doing this gives the exact same results to which I explained earlier, because it forces Cubase to create a new .xml file. Probably easier to just delete that one file, then to have to move all your plugins to a new folder.

alienmachine · Post by **alienmachine** » Sun Aug 06, 2006 7:06 pm

I ALWAYS had this problem when working with plugins. From my experience:
1) Move all your plugins out of the vstplugins folder.
2) Start Cubase. If it works it means that a plugin is to blame.
3) Start moving the plugins back to the original folder (in groups of 3, 4 or whatever) and run Cubase everytime until it fails.
4) Then you can isolate what plugin is to blame.

I tried that process hundreds of times.
Stupid Cubase, when it finds a unrecoverable error it just disappear without any trace of what happened. Sometimes, even in Cubase.log there is nothing.

ObsoleteAcc99 · Post by **ObsoleteAcc99** » Sun Aug 06, 2006 7:12 pm

[DELETED]

Pouckypluysch · Post by **Pouckypluysch** » Sun Aug 06, 2006 7:24 pm

Lord Snarebottom wrote:

You mean you don't have a drive image or system restore on your system drive?

I actually do have system restore on my system drive. But unfortunately it didn't restore my system...

Q: If your setup was working fine (and you weren't prudent enough to have the steps listed in the previous sentence in place), why oh why do a Windows update?

Well, if there's room for improvement, I'll go for it. I use the pc to browse the internet as well, so I feel comfortable to have the security leaks corrected, when Microsoft finds any.

But meanwhile, I have made some progression. I replaced my plugins folder, and Cubase started up with no problems.

I tend to think Foxglove's suggestion about the corrupted xml-file is right; it would explain the strange behaviour before the start up troubles.

It's just that I can't find the 'VST plugins.xml' anywhere on my system (might that be the problem?). There even isn't a Steinberg or Cubase SX folder in my application data.

Could it have another name as well, or is there another xml-file I could look for?

Muzik 4 Machines · Post by **Muzik 4 Machines** » Sun Aug 06, 2006 7:38 pm

maybe its a hidden file
be sure you can see them
and show extensions
and if you do a search,check find system files

Roman Empire · Post by **Roman Empire** » Sun Aug 06, 2006 8:20 pm

Just for the future:

Moving all plugins can take alot of time if the new dir is not on the same drive.

The easiest way to go is to simply rename the vstplugins folder, like adding a ! in front of its name.
That's alot easier, and will have the same effect.

Help needed: SX3 won't start up anymore!