SONAR X1D definitely not my favourite progran at the moment.

I'm venting at the moment but I have to say that in all the years of using this software I've never had hassles like this before. Never mind that I've just lost a project that I have to deliver to a client in two days.
 
The project consisted of about 24 tracks with 10 drum tracks and the rest gtrs, keys and bass. Session drummer, bass player, etc did their parts and the whole process seemed to work well.
 
Everything went fine, Sonar behaved (or so I thought) and I kept saving the project to two different hard drives (just in case).
 
During the final mix, I started getting a message that the disc is full and Sonar could not save the project. Both drives have about 450 Gb free so that was utter rubbish.
 
Anyway, I closed Sonar and reopened the project to find out that the project cannot open as it is truncated. This is caused by the program exiting prematurely whilst saving?????????? Nothing of the sort happened and the program certainly did not exit prematurely. I closed the program because it refused to save.
 
I went to the backup project files and I got the same message.
 
This is the first time that this has happened and quite frankly it has to be the last. Getting session players into the studio to redo stuff that the DAW has destroyed is not very cost effective.
 
At the moment I'm furious that this has happened. I'm gonna miss a deadline for the first time in my life and there is absolutely nothing I can do about it.
 
I would like to hear from anyone else if they've had this happen and is it really the end of the project or can it be rescued?
 
Thanks,
 
Peter.

Yes, I have tried holding shift and opening but all I get is a completely empty project.

I will do a search.

Thanks

Did you try dragging the old .cwp file into a new project?

"During the final mix, I started getting a message that the disc is full and Sonar could not save the project. Both drives have about 450 Gb free so that was utter rubbish. "......... I have seen this in the 64 bit x1 on a number of occasions. Never seen it on 32, but I do use 64 a lot more than 32. I hate it when it happens because I loose my recent edits. Granted its only the recent edits but it really detracts from the art.

I did try dragging the project file into a new project but still get the same message.

I did use the "save as" but also got the "disc is full" error. It copied the audio tracks but not the project file.

Yes, it looks like I'm gonna have to start saving differently but still doesn;t get me out of this fix.

Thanks for the suggestions.

How about the old "Picture Cashe" folder?  Have you emptied that lately?  I hate to sound like a broken record on the forum, but empting the "Picture Cashe" folder seems to correct many of these issues for me.

Your audio waves files could still be intact and you could rebuild the project by importing them into a new session.

 
+1
The audio files are likely fine...

Yes, I had to do this a long time ago. It took me two days to reconstruct the project with all the plugins and synths. The tracks were all fine. Time alignment was a bear. I developed a backup strategy after that experience.

 PJH, I have also learned the hard way with the "save" giving you the white screen of death and having to close X1 becasue it is not responding.

When this happens, the file you are saving is ALWAYS corrupt and NEVER opens again.

It is essential in my opinion to do a "save as" every time you do a meaningful save after a change you are pretty sure you want to keep and keep working on from.

It is a pain in the ass, but this way, the only loss you can make is changes between your "save as" and usually it is quite easy to redo (providing you save as often)

Im sorry to hear your problem. it is such a blow when this happens and you never get back to what you exactly had,when you redo the stuff.

I would also suggest the following:

Close plugins open windows when you save. I can't say for sure this is part of the problem, but I think it may be one of the issues during saves that casues this.. well, that's just something I noticed anyway.

All the best with your project.

A normal save as is what I do all the time. I only use save if I know I want those changes in the file I'm working on. But I always have at least the first version as a backup.

I have some projects that I had to move to another disk because I had too many versions of it. That way I could start fresh. But I always have all the versions on tap if I want them.

Remember that a cwp file is just the project without the audio and is a small file.

Yes, use save as. 

Yeah, I think John may have confused what I was trying to ask (which is understandable because I'm still having a hard time with the lingo). So essentially the batch file Save As thing won't make any difference really and I should just stick to regular project files (so I don't waste disk space for nothing). If I REALLY wanted to be paranoid (which I do in some cases) if I felt it was important enough I'd save the batch file to another drive completely. And yes I do mean above and beyond regular back ups. Just... "okay, this part is done. I might want to roll back to it. Save As to drive C and Drive E (or D... or Q or whatever) so if something explodes I can snag EVERYTHING from that point and I'm good to go. Well I guess I may have answered my own stupid question there didn't I?

@John... Oh yeah... I know I've been a derper as far as X1 but I know about that kind of general stuff. I've been manhandling computers for a while now for work and play. I was more trying to figure out the save CWB vs. save CWP to avoid OPs problem.

Here's what I've eked out in my little monkey brain.

Internally I have HDD C and HDD E.

C is where Sonar and all it's components live and E is where I intend to record to.

In this set up I would...

1) Use Save (just regular Save... not Save As) every 15 minutes or so as I worked just out of habit...

2) When I reached some kind of completion, like a track has been EQd to my liking or I wanted something to rollback to so I can compare the initial setting to an experiment or I was just done for the day I'd "Save As" into whatever folder I had created for the project on the E drive.

3) If I hit an extremely crucial point in the process and everything is just the way I want it (for example an initial mix without effects, a finished drum buss, all tracks with effects... anything that is solid and would REALLY suck to lose) then I would "Save As" to both the E and C drives so I have two copies.

4) I would also do regular file backups with CWB to an external drive or optical discs or the Cloud or whatever the hell in case aliens mistook my computer for food or it spontaneously combusted or it shot a man in Reno just to watch him die so now it's in prison contemplating about the sound of passing trains or whatever other weird ass full on catastrophe might befall me and my little endeavor. I still need to buy another drive for external back up but I have DVDs for now and I'm not recording anything important yet so whatever. It'll be cool

Sound about right?

I use AutoSave every 10 minutes (It doesn't interrupt crucial disc writes etc as some folks would have us believe) and Versioning.

I set versioning to 'on', I allow 99 versions and SONAR writes a new .cwp file at every save. that way if there's ever a crash I not only have the audio but a project file that is at the very worst 10 minutes old. At the end of the session I just delete the additional versions that were there just as a precaution. It's not using a lot of disc space as its only the cwp file and it saves in the background so it doesn't interrrupt your work flow or disc IO operations.

I've been doing it this way ever since these features have been available in SONAR and they've worked well for me.

When you then add precaustions like using 'Save As' at crucial times in your project you then have even more redundancy and anyone who's ever lost a project will wish they'd had all the redundancy they could.

I'm one of the few that doesn't use auto save. But I have no objection for it being used by others.

I once used it but was a little put off it by it creating so many saved projects.

I like to decide when to save myself. But auto save can be great for saving oneself. LOL