| Author
|
Problem with "corrupted" track files in cubase
|
osker246
IsraTrance Junior Member
Started Topics :
16
Posts :
34
Posted : Jan 19, 2007 03:47
|
I don't know what the deal is. Every once an awhile I'll start a new track then the next day its "corrupted".
Like last night I was working on a new song and I saved it right before bed. I get on my computer to work on it this afternoon, and as soon as I load the file cubase crashes on me. I have no idea why it's doing this either. Its happened to me a couple times before also.
Does anybody here have an general idea why its doing this? And, how to avoid this from ever happening again? |
|
|
Boobytrip
IsraTrance Junior Member
Started Topics :
39
Posts :
988
Posted : Jan 19, 2007 14:19
|
|
Meta
Meta/Boomslang
Started Topics :
24
Posts :
1045
Posted : Jan 19, 2007 21:17
|
|
Yan
Started Topics :
1
Posts :
6
Posted : Jan 19, 2007 21:45
|
|
Use Ctrl+Alt+S |
|
|
|
shachar
Basic
Started Topics :
13
Posts :
402
Posted : Jan 20, 2007 17:10
|
could be:
bad crack version of cubase,
bad vst effects crushing cubase,
corrupt hard disk.
|
|
|
|
IRRATIONAL IMPULSE
Started Topics :
9
Posts :
50
Posted : Jan 20, 2007 17:47
|
I will agree with shachar...It should be a corrupt HD or a corrupt array on the disk...
 Vasilis Irrational |
|
|
|
xaBBu
xaBBu
Started Topics :
8
Posts :
161
Posted : Jan 20, 2007 18:10
|
there is an easy way to fix this : most of the time its caused by two things:
1 a vst effect which fails initializing the saved settings and thus blocking cubase to load the project.
2 a frozen vst instrument, in which case the freezing somehow messed up. I experienced this with a few combinations of plugins.
but the good part is: most of the time there is an easy way to fix this.
for 1:
Just take the bad vst out of your vst directory, load up the project and fix it. it will say it cant find the plugin, but in this case thats a good thing 
for 2:
go to your project directory and find a directory called "freezes". Look at the filesizes of the wav files. if you find a freeze file that has 1KB or 0KB size (except for frozen multichannel instruments, where only the used channels will have a bigger size), its damaged. delete these files and then load up your project. Cubase will say that it cant find the freezes and thus mark the vst plugin as unfrozen. Now fix your project.
I hope these tips help you. They did the trick for me.
|
|
|
|
osker246
IsraTrance Junior Member
Started Topics :
16
Posts :
34
Posted : Jan 21, 2007 06:23
|
Thanks for all the replies guys, I appreciate it.
Last night I tried reinstalling all my vst plug-ins to see if it would solve the solution, which of course it didn't. So I tried removing the Vst folder from the Steinberg directory seeing if it would make a difference. Which it did, the project would load completely but would show the missing plug-in menu.
I believe I know which plug-in are giving the problem. I recently installed z3ta+, toxic, and waveplus. Prior to that I've never really had this problem happen to me. Which is a damn shame too, these are great plug-ins. Plus it took me a long track down these plug-ins. 
So im gonna do a little more messing around seeing if I can find out which one is giving me the problems. Hopefully I can keep z3ta+, I love that synth now...
|
|
|
|
Boobytrip
IsraTrance Junior Member
Started Topics :
39
Posts :
988
Posted : Jan 21, 2007 20:07
|
|
In my case i think it was the Enigma plugin of the Waves bundle.
|
|
|
|
