WDI


Curious if you guys having this problem have NTFS or FAT32 formatted hard drives?

NTFS in my case.

when you get that error first thing you want to do is launch windows explorer and copy your project directory to a new one.  dont ever close sonar first...its eaten my audio data before and even 4 drive recovery programs found no trace of them. that one sucked big time.

Funkybot

chuckebaby

s h

just keep in mind if your work is so important(I know you don't want to hear it) but back it up man.  :) 

Question: how do I backup a project I just started working on? How does one backup work they're in the middle of doing?


1. Create a new project
2. Get a good flow happening
3. Stop & Save
4. Burn DVD's
5. Launch my online backup, upload the file
6. Now, what was I doing? Oh yeah, I was working on a song at some point. 
7. Make a change
8. Repeat steps 3-7?

Backups will happen after I'm done working, not during.

And sorry, saving should NEVER corrupt files. I've never had it happen in any other software. I've had saves fail in other software for various reasons, but only Sonar has corrupted files during failed saves. 

I like Cakewalk too, but I refuse to apologize for their critical bugs nor do I try and pin the blame on the end-users.

is it really that hard ?
at days end, I copy the working folder on my external HD.
at the end of the month, I burn all those copy's to disk.
 
now how do you take 8 steps to do this process ? ..lol
 
you don't blame the user for losing 6 months worth of work?
because that's exactly what you just wrote.
go ahead and read your comment again.
"I like Cakewalk too, but I refuse to apologize for their critical bugs nor do I try and pin the blame on the end-users. "

 
8 steps to save a project ? im sorry..lol
even my buddy next to me is laughing.
upload ? where are you uploading ?
burn dvd's?  in between saves ?
even if you copy the project file to a different part of your hard drive you have a simple back up.
 
you should only need to back up your work to dvd between once a week to once a month.
 
either you just want something to complain about or your working backwards man.
 

no professional software should corrupt files on save with any kind of regularity. Photoshop, Word, Excel (and I spend probably 20x the amount of time in these programs just do to the nature of my fulltime work) don't corrupt files.

 
I'm not from Boston, but I certainly don't have this problem with SONAR, and never have.   Knock on wood.   However, I have had Excel 2007 files go bad a few times over the years on my work system.  Same goes for CAD files such as DWG and DGN (which I've also seen first-hand).  Fortunately I've never lost much anything, but it can and does happen outside of SONAR.
 

I also do not use auto-save.

After any significant effort in a project, whether it's a bunch of drum beats entered manually or a superb guitar/keyboard track, I will save.

I just had a knee replaced, and I am just getting to where I can sit at the computer for a while, but I have to frequently move my leg around to keep comfortable.  One of the places I put my left is on top of the computer tower, which sits under the table that my primary display is on.  It's mighty comfortable, but there is a reset button on the top of the computer, and I frequently cause my computer to reboot.  DOH!

Anyways, I also normally save off a project to a 2nd physical drive prior to beginning any substantial editing of a project, to further protect myself in the event of a drive failure.  That also protects me in the event of any kind of project file corruption, so I recommend doing that as well.  It takes maybe 30 seconds to a minute at most to do.

Bob Bone

This is the worst of all Sonar bugs.

Assuming the post just above from THambrecht is correct, is it possible that those who suffer from this do not have their hard drives always powered on? If you still had the default power saving scheme from Windows and the hard drive was not ready, would it cause this?

I believe FunkyBot is right that none of the audio should ever be lost. Much like Adobe Lightroom treats photos, Cakewalk shouldn't do anything at all to the original audio. It's non-destructive. The audio isn't touched, only read. Then, when you mix/export it produces a treated resulting copy of the audio with all the work Sonar does to it, but you should be able to cut your clips (slice and dice), save the project, close it, re-open it, and still be able to adjust the ends of clips (unless you bounce them to clips, which should only create copies of original audio, I believe). 

So, think of everything Sonar does is merely an overlay to your original audio. I think Cakewalk support should be able to walk the OP through this and at least minimize the issue. 

Then let's get on a good backup regimen. I've had issues with Auto-Save as well, so I've discontinued its use until I hear of improvements, but I manually save my work every 5-10 minutes or x-number of changes. Ctrl+S is very easy to make a habit. Archive your session daily, but not the audio. The audio shouldn't change, only session, unless you bounce (I believe).  

brconflict : "I believe FunkyBot is right that none of the audio should ever be lost."

Things are already this way for audio and in the case of this thread audio was not lost.

This doesn't hold for midi but it would be nice if it did.

Midi was lost in the case in question.

I've had this a few times. What worked each time for me (don't ask why) select all tracks and delete them in one go. Then undo the delete. Project comes back up , but with no error message.
 
Let me know if it works for anyone else.
 
Hope helps

Funkybot

chuckebaby

Funkybot

chuckebaby

s h

just keep in mind if your work is so important(I know you don't want to hear it) but back it up man.  :) 

Question: how do I backup a project I just started working on? How does one backup work they're in the middle of doing?


1. Create a new project
2. Get a good flow happening
3. Stop & Save
4. Burn DVD's
5. Launch my online backup, upload the file
6. Now, what was I doing? Oh yeah, I was working on a song at some point. 
7. Make a change
8. Repeat steps 3-7?

Backups will happen after I'm done working, not during.

And sorry, saving should NEVER corrupt files. I've never had it happen in any other software. I've had saves fail in other software for various reasons, but only Sonar has corrupted files during failed saves. 

I like Cakewalk too, but I refuse to apologize for their critical bugs nor do I try and pin the blame on the end-users.

is it really that hard ?
at days end, I copy the working folder on my external HD.
at the end of the month, I burn all those copy's to disk.

now how do you take 8 steps to do this process ? ..lol

you don't blame the user for losing 6 months worth of work?
because that's exactly what you just wrote.
go ahead and read your comment again.
"I like Cakewalk too, but I refuse to apologize for their critical bugs nor do I try and pin the blame on the end-users. "


8 steps to save a project ? im sorry..lol
even my buddy next to me is laughing.
upload ? where are you uploading ?
burn dvd's?  in between saves ?
even if you copy the project file to a different part of your hard drive you have a simple back up.

you should only need to back up your work to dvd between once a week to once a month.

either you just want something to complain about or your working backwards man.

Again, you missed the point. Yes, at some point in the last 6 months the OP should have backed up. However, when saving/autosaving will corrupt a project is impossible to predict. And it doesn't matter if it's 6 months worth of work that was lost, or 6 hours. Barring a catastrophic hardware failure, one should never loose work during a save.


Now, as I've already said, I had it happen in a brand new project. This means 1) I never even had the chance to backup, and 2) there was no other version of the project for me to revert to. Luckily, it was early enough in and everything was fresh enough in my mind that I was able to recreate my work fairly quickly.
That said, I should NEVER EVER EVER have experienced that. No other software I've ever used corrupts files on saves. Sonar does.

Now post back and tell me how it's my fault for not having named my project, and how had I done that, autosave would have created a second file and how I'd have at least some prior version of the project I could have gone back to. You'd be right. Except, and this is a big EXCEPT: no professional software should corrupt files on save with any kind of regularity. Photoshop, Word, Excel (and I spend probably 20x the amount of time in these programs just do to the nature of my fulltime work) don't corrupt files. Sonar does often enough that these posts crop on the forum frequently. In fact, it seems like a lot of people in this thread have had this happen to them. Well, it's unacceptable.

And I don't want something to complain about...I just want a DAW that can save projects without corrupting files. I don't know why you think it's ok that this happens. Is it a "Cakewalk's from Boston and I am too" thing? Heck, maybe you even work for them in some capacity. Otherwise, I don't get it. 

I don't think its okay this happens and im sorry for your loss (of your project)
this is never happen to me, so I cant agree with you. I wish I could so I could relate, im not saying it doesn't happen because...well look here at this thread,
I just don't see it every day, every week, maybe once every month ?
maybe ?
so out of 1000's of users, a corrupt sonar file ?
this could be anything, it may very well not even be sonar corrupting the file ? hmmm?
possible.
 
I don't use autosave, that might be another one.
I don't even use autosave on any software I use, not word, anything.
 
its not a boston thing, its a ..I made a comment and you quoted it, then mocked me about it.
so after this, you then turn around and say, its a boston thing ? 
no,it isn't.
 
some people do indeed enjoy complaining, they like it.
I save my complaints for serious inquiries, because I have found that if you complain all the time, then when you have a real complaint, its over looked,
people are just: "o he complains all the time"
so I save my complaints for real issues, which I have a few.
I only mention this because your posts usually end up going down this road and at the end there is this.. "well cakewalk should";
 
ive had corrupt files in other apps before so im sure it will happen to me sooner or later.
but I don't think cakewalk should stop, drop and roll looking for he corrupt project file problem like you want them to.
every software sooner or later is going to do a few things you don't like.
my theory on this is, we have become so spoiled with software that we expect it to do every little thing we want it to.
only problem is every application has different environments (different apps running in the background, exc) so its bound to follow the laws of error.
it was only 10 years ago when you could only do half the things you could do now on a daw and if someone would have presented the idea
of doing these hi-technical things with a few flaws back then, you would have certainly jumped at the offer to use these hi tech functions.
so at what point to we start biting the hand that feeds us these great pieces of work ?
I guess now..lol
 
there are those who have trouble understanding this theory. probably like yourself, it sounds it anyway.
I don't see the forum blowing up with this issue, sorry not buying it.
 
by the way, my corrupt files in other apps that I mentioned earlier,
they were do to a failing hard drive.
not saying this is the case for everyone but in my case it has been.
 
good luck
 

I tell ALL of the computer techs in this field that if they EVER lose data due to not having a backup they should look for another line of work...tough love but it is what it is.

 
In three distinct formats/locations, correct?   
 

Autosave would have saved your ass! Well...  if not your ass, most of your project....  I've had that truncation issue before and the Autosave file ALWAYS works.  Then of course of you have versioning turned on, you have more choices to recover from

It is important to understand that when SONAR saves, the data may not be written to disk immediately. If write caching is enabled for the hard disk (which it seems to be by default), Windows will complete the write some time later when it's not busy or the cache is full. If there is any glitch or crash before the cache is committed to disk, the file will be corrupted or lost. There is nothing that SONAR can do about this.

How to turn off caching:

http://www.speed-up-pc.or...ware/write_caching.php

stxx


However, ypou will likely have some version that is useable that was successfully written prior to the disk issue.   Also, there is some GREAT SW out there that lets you recover a good portion of a blown HD.   I've used it and it totally saved me. It is called "Diskinternals Partition Recovery" and it works!   I also have a kit that allows me to hook up any type of hard disk via USB including notebook style so between those 2 things, if your disk crashes and you don't have a good backup, there is a very good chance you will be able to recover most if not all of your data. using those tools

But, we always have a good backup...RIGHT!