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

WDI


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

NTFS in my case.

I was trying to copy a 8GB video file to an external hard drive formatted with Fat32. I kept getting the disk full message despite having plenty of space. After spending lots of time trouble shooting I remembered Fat32 files can not exceed 4GB.

Anyways, saw this thread and thought I'd bring that up. Windows must use that generic message "disk full" even though that is not the problem. That would be my guess. Obviously you guys have free space. Hope you guys or Cake get to the bottom of this issue. 

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.

daveny5

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. 

When it happened to me, it was a brand new untitled project so there was no other version unfortunately.

Again, I was able to manually recreate everything I did (manually imported in the audio tracks and recreated the MIDI parts manually), but I was still really peeved.

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.
 

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. 

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.
 

It takes 10 seconds to do a "save as" to my back up drive. 
I do that when I'm feeling insecure randomly but at least once a day. usually 4 x. 
Just remember to do a second "save as" on next save to re direct to your main drive again. I have never used auto save, I'm a control freak. 
I save after every good take, or ten??? minutes of editing. 

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