I know remember what the issue was with the "disk full" message I had a few years ago.  It was when I was still 32 bit and was pushing the limit of the 2 GIG memory addressing limit in WIN 32 bit.  The project had many large sample libraries loaded in and the other symptom that was happening was the UAD2 plugin knobs were disappearing on the GUI.

However, in my case, a reboot was in order and I was able to re-load the project that I had saved earlier.  I did NOT have auto save turned on and my error happened when I tried to save once I saw the GUI knobs disappearing so I didn't lose much work.

Jim

I'm sorry you lost a great tracking session, it's a tough thing to accept.

One thing I didn't see mentioned is this: fill out a bug report (professionally - i.e. no swearing) and attach the corrupt project file for Cakewalk. They may or may not be able to recover it but it could lead them to understanding the problem. If they understand the problem they might be able to fix it and save some other poor soul the frustration you are experiencing.

Regards,

You didn't have autosave on? I keep tellin' people.... Autosave is not perfect, but its better than nothing.

After you cool off, start back on your project. I find the second time around, it comes out better than the first. 

I've become over-sensitive about things I believe might jam the system somehow and cause project corruption, even though I've never experienced "catastrophies" except for one HDD crash. I have autosave off, and I Ctrl+S frequently, I don't try to edit MIDI/audio or save on the fly (=during playback), I never leave pitch-shifters (=Melodyne) active in the project, I never advance from a task to another before I can see the previous one is executed, I always save before I launch VSTs that often halt the project (Vocal Strip, Perfect Space) etc.

There's been too many posts recently about lost projects, it is alarming. Having MIDI saved in a folder of its own would be a step forward in project safety, I agree.

I am sorry to hear about losing some of your work. Have you tried retrieving your audio files from the project audio folders? You might be able to get some of your work back.

I searched on this error and found the following suggestions: 

• Delete your picture cache.
• A bad WAV file that was imported
• It just means an (unidentified) error was raised while attempting to write to disk. It could be a failing disk drive, a loose cable, or simply a bad spot on the disk. Run a disk diagnostic that can map out bad spots.
• Export an audio track as a wave file and then try the save again
• In your aud.ini file, change DiskRecBufferSize to 512. 

"Export an audio track as a wave file and then try the save again"... that was my suggestion and every time I suggested it to someone with that problem, they replied that it worked.

daveny5


You didn't have autosave on? I keep tellin' people.... Autosave is not perfect, but its better than nothing.

After you cool off, start back on your project. I find the second time around, it comes out better than the first. 

In my case, it was an autosave that corrupted the project. Had the autosave not failed, I would have had the prior save and the project would never have been corrupted.

The problem seems to be that Sonar saves things in a piecemeal manner, and if the save doesn't complete 100% successfully, instead of not applying those changes (so I'd at least have things as of my prior save), Sonar will end up creating a corrupt project file. 

Most programs will create a .tmp file while you're working and for the duration of the save process as not to overwrite existing files. This way if the save fails, you don't loose your old data. Sonar doesn't appear to handle saving this way. Not cool.

The last time this happened to me, I tried exporting to a .wav.  I could export the mix or an individual track, but SONAR would still not allow me to save the project anywhere. 

I had to quit SONAR, and the autosave file of course was "truncated" at that point. 

So I agree with everyone who says they need to do a better job with exception handling in the code, and robustness during saves.  

SONAR  should have several schemes for trying to recover from a save error, up to and including asking the user to plug in a USB drive to save to if the main drive is having issues. 

It should save whatever is savable in some format that the program can read in and recover as much information as possible.

John

Funkybot

daveny5


You didn't have autosave on? I keep tellin' people.... Autosave is not perfect, but its better than nothing.

After you cool off, start back on your project. I find the second time around, it comes out better than the first. 

In my case, it was an autosave that corrupted the project. Had the autosave not failed, I would have had the prior save and the project would never have been corrupted.

The problem seems to be that Sonar saves things in a piecemeal manner, and if the save doesn't complete 100% successfully, instead of not applying those changes (so I'd at least have things as of my prior save), Sonar will end up creating a corrupt project file. 

Most programs will create a .tmp file while you're working and for the duration of the save process as not to overwrite existing files. This way if the save fails, you don't loose your old data. Sonar doesn't appear to handle saving this way. Not cool.

I don't know about that. Autosave saves to a different project file, not the one you're working on. I've had autosave cause problems though so I guess its possible.