save it with a different name.

hmm hope you figure it out, at worst case scenario, take tons of screen captures.

Thanks for the reply guys!

Mad for Brad: Already tried that. The problem remains..

MSZ: Good point.. That'll be my last resort!

___________________
David Laine / Castra / Semantica
Magic Island / Armada / Perceptive
Website | | Soundcloud

Save it with a different name, try to render as much of the VST to audio as you can, export the MIDI files, write down the presets and instruments if u have to. quit Cubase, restart ur machine.

Then try and see if u can actually start a new project with the same exported MIDI and audio, presets etc.

___________________


http://soundcloud.com/subtara

be careful with your hard-drive, this could be a sign of it starting to fail in sectors(if indeed not a software issue).

Can you open more than one project file at the same time and copy the stuff to another file to save?

___________________
Soundcloud

quote:

Originally posted by alanzo It's like sifting through cat shit to find a penny. In the end, it wasn't worth the effort.

quote:

Originally posted by music2dance2 Can you open more than one project file at the same time and copy the stuff to another file to save?

Yes you can actually.

___________________


http://soundcloud.com/subtara

I reckon that would be the way to go. Those situations with corrupt files that cant be saved usually end one way, they dont save. That and make multiple screen shots and notes export midi, audio etc if needed

___________________
Soundcloud

quote:

Originally posted by alanzo It's like sifting through cat shit to find a penny. In the end, it wasn't worth the effort.

There's no way around it - it happened to me once in Cubase SX2 and the only option is rebuild the project from the files.

You're actually way better off anyway as you don't want a corrupted file as your project, even if you were able to save as.

Just get a new project open (simultaneously) and copy the tracks over. Go through each one and check your settings. Each time you copy a full tracks worth of data in to the new rebuild project, do a save as and create a new version to copy the next tarck data in to.

It may mean a lot of project files but at least this way, if it's a weird corrupt bit of data or a strange conflict causing the problem, you can pinpoint which one and rebuild the project without it.

You can also save your effects chains for each channel as presets and load them up in a new project.