KVR Audio

cptgone · Post by **cptgone** » Thu Nov 17, 2005 7:46 pm

(I posted this at the Steinberg forum first, then figured I'd have a better chance for replies here )

I have a project that keeps giving me the "A serious error has occurred, save your song under a new name and restart" dialog.
Every time I need to reboot or my ASIO drivers won't work (and then my PC hangs)
On top of that, one of the VSTi in the project won't make any sound since my last save... WTF?

- Is there a way to restore a corrupt SX2 project file?

- What does this dialog mean exactly? If I save the song after getting this message, is the resulting project file to be trusted at all?

steffensen · Post by **steffensen** » Thu Nov 17, 2005 8:01 pm

ive heard using waves plugins, with the waves vst wrapper, saved in the specific track can cause this. but i dunno..?

musicmaster · Post by **musicmaster** » Thu Nov 17, 2005 8:32 pm

It can be almost anything!
Often it is a bad plugin. Have you installed any new plugins recently? Don´t install more plugins than you use, stick to a few good ones instead of a hundred bad ones. Try to uninstall one by one and restart the project.
Cracked software can often be the reason of this kind of problems.

Musicmaster

cptgone · Post by **cptgone** » Thu Nov 17, 2005 8:33 pm

thanks... I do have lots of plugs installed, I'll give it a go

musicmaster · Post by **musicmaster** » Thu Nov 17, 2005 8:50 pm

Try to clean your registry with some kind of registry cleaner software after you have uninstalled the plugs and defragment your drive. Try to be structured when you install the plugs.

Musicmaster

Musicmaster

musicmaster · Post by **musicmaster** » Thu Nov 17, 2005 8:52 pm

Do you have the latest update for Cubase. Try to upgrade to SX3 if you can afford it it´s much more stable.

Musicmaster

steffensen · Post by **steffensen** » Thu Nov 17, 2005 9:14 pm

im actually considering cubase 3 myself. (switching ships from Logic.) trying out nuendo 3 in my mates studio right now, and with some configuring and adjusting, i kinda like it more and more. the external instr/fx thingys are GREAT! (as well as offline processing, wehoo!

) finally i have a good alternative to handle my HW stuff.

but i havent decided yet.. testing Live as well, but it really leans into the cubase 3 department. to many great features in there to be able to live without.

cptgone · Post by **cptgone** » Thu Nov 17, 2005 9:34 pm

musicmaster wrote:Try to clean your registry with some kind of registry cleaner software after you have uninstalled the plugs

Good point, I'll do that

musicmaster wrote:defragment your drive.

Check

musicmaster wrote:Try to be structured when you install the plugs.

The more i try, the less I succeed. I always seem to bump into e.g. plugs that work only partly when installed in a subfolder etc. etc.
Good point though.

cptgone · Post by **cptgone** » Thu Nov 17, 2005 9:38 pm

musicmaster wrote:Do you have the latest update for Cubase.

Yep.

musicmaster wrote:Try to upgrade to SX3 if you can afford it it´s much more stable.

I'm waiting for SX4, and may even switch to whatever appeals most to me regarding functionality, workflow, and copy protection. The final versions of SX1 and SX2 were quite stable to me already, apart from occasional trouble with particular plugs. Thanks for the tip though.

steffensen · Post by **steffensen** » Thu Nov 17, 2005 9:41 pm

try renaming you vst plugins folder, or move it temporarily. and then open yer song, and see if the same error occurs. that way u at least can save the tune somewhat..

cptgone · Post by **cptgone** » Thu Nov 17, 2005 9:42 pm

I think I have it solved now: I think it's a 'bad' plug. Should have known from before

Step by step fix

steffensen · Post by **steffensen** » Thu Nov 17, 2005 9:54 pm

goodie.

Sequent · Post by **Sequent** » Thu Nov 17, 2005 10:02 pm

I get that message too once in a while and I was told that it's related to graphics. Usually what happens once I get it is that the graphics go haywire even though the audio still sometimes continues to work. Then I have to do a complete reboot to get back to ground zero.

You should always save a safety copy of your file in addition to your regular file in case your main project file gets corrupted.

A lesson I was well taught by Mr. Quark XPress.

cptgone · Post by **cptgone** » Thu Nov 17, 2005 11:00 pm

Liondream wrote:You should always save a safety copy of your file in addition to your regular file in case your main project file gets corrupted.

Yeah, I regularly "save as" to a new title ("titleYYMMDD")
That way I have a "history" of all MIDI tracks and settings.

kritikon · Post by **kritikon** » Fri Nov 18, 2005 12:38 am

Good to see you have it fixed?

It almost certainly will be a plugin. For example I used to get that message regularly whenever I tried to automate any of the lesser parameters on Wusikstation (still on v1). Even patch changing could do it. Blockfish used to crash SX too. It took me a while to figure out which ones were the culprits, as they didn't do it all the time (which I find very weird...). Blockfish would work up to a point on my original SX2.0, but crash it with that error message when I got to 3 instances. When I went to SX2.2.whatever, it doesn't work at all, and I had to go through every single plugin I used in a couple of older projects to find out which plugins were the culprit. It's not always immediately obvious. It doesn't necessarily have to be older plugins either - although they have more chance.

I used to worry about saving a .cpr when that message popped up - I too assumed that the whole .cpr would then be saved corrupted. But it doesn't mean that at all. In fact that is why it took me so bloody long to find out it was almost always plugins - because I'd save, reboot and reload, and the saved .cpr would work fine. Go figure?

It seems to be just an error message to tell you SX has been given a brainstorm by something, not that SX has faulted, more that something has fed it duff information or something. Call it indigestion? It's a Cubase barf

Cubase SX2 problem: "A serious error has occurred"