I had some crashes becasue of auto save in the past that corrupted my project a few times-

That may not happen much now, but I went to control s and save as for backup sometimes-

I never looked back-

Save as backup and then I save as the original again so the backup is a print in time until I do it again-

Lance

Hi, Bub - I'm currently at a disadvantage in replying - apparently Firefox 6 screwed up some things. All I know is that I can't quote from messages anymore when I'm replying here on the Forum. The basic thing for me is that I'm not against Auto Save - it's just that the routine I've had for years now works perfectly well for me. CTRL+S is so an automatic, built-in response for me, I know I sometimes do it many times during the course of a minute. I certainly do it after every small chunk of editing. And when I know I've made enough changes to warrant a new save, Save As is easy to do. I like having control over my saves - that's all. It's a sense of control thing when it gets down to it. And in my project folder, I have a neat little list of versions - usually a fairly short list, and they all share the audio folder, it's so simple to go back to a previous edit if I want, delete the extra versions if I want - Basically the same thing I could do with auto saves (though I'd have a lot more to weed out with that method)- but IIIII did it, not some robot telling me when I should do it. Auto Save - the first thing I turn off in any software I use, not just Sonar. RB

Hi Randy. Thanks for the reply!

I'm very forgetful and see the Auto Save as a God send. I can't tell you how many times I would crash and lose everything and be so furious at myself for not saving. Especially back when I first built my DAW and I didn't realize I had a bad stick of RAM for several months! DOH! It was crash-fest 2009. But the one thing I noticed that now leaves me scratching my head as to why, knowing I did in fact have bad RAM, is, the crashes almost completley stopped when I enabled Auto Save. I don't know if it dumps things from memory, free up the page file, or what it does, but it helped tremendously.

Now I have the page file turned off and everything goes in to RAM. I wonder if that's why I don't see any stuttering when auto save kicks in?

And by the way, Firefox 6 is causing serious problems on the forum here. There's been a few unhappy threads about it. :)

I'm still on FF3.6 and working fine.

Autosave's purpose is to prevent data loss when the machine stops responding, app hangs, electricity loss, hardware failure, cat on the keyboard, spouse requiring attention,...

Yea sure, doesn't happen often.  That's also good reason to not purchase insurance.

I enable the autosave function on all programs I use, and my client's use.

The main problem with Sonar is, my observation, the autosave does not happen when the transport is transporting.

There are times when I will loop a long section and add a bunch of tracks. This can be many, many minutes.   During these happy moments I do not want to be tending to the app. But Sonar requires this attention. 

Yea, most of the data will have been written to disk. But having to import and align a bunch of clips after the saddness of a blue screen is annoying at best. 

Word, excel,... do it without interrupting my rolling along.

j

Lanceindastudio


I had some crashes becasue of auto save in the past that corrupted my project a few times-

 
This makes no sense. Unless you had opened the Autosave file and did not save-as to a new name.
 
Autosave creates an AUTO SAVED file. And replaces it when next auto saving. The orginal project file is not affected, unless it was named AUTO SAVE.
 
I never use SAVE.  Only SAVE-AS, to a slightly different name so files are less likely to become corrupted. And to not lose ideas and work that was altered, and will be lost using SAVE.
 
j
 

hehe---The debate/conversation continues. All I know is I haven't lost work in Years - capital Years, and I am my own captain at saving my projects. I usually just CTRL+S, do Save As when I've done a major change - no need to have my folder fill up with a million Save As versions, since after years, I've never lost anything. As wrapped up as I might get while playing back a project, it is simple pie to stop for a second, spend a split second to do a manual CTL+S, and then continue - it's all done within the space of a measure. No messy re-construction to do as was described in post #34. Folks- the point is there is no Right Way to save our projects. Use Auto Save if that floats your boat, do it yourself if that does. As long as you do Something to save your work and never lose your sessions. RB

--oooh no--- now I see that I can't even do paragraphs--formatting is totally for kaka--supposedly due to Firefox 6? arrrrgh. RB

Bub

rbowser

... more than a few of us have made the choice to save manually because we Do understand Autosave, and we prefer to do the saving ourselves.

Hi Randy,

I don't understand why some people have an aversion to Auto Save and I'd like to understand better in case there's a better way for me to use it or not use it. :)

The way I always understood Auto Save is, it is a separate file that has nothing to do with the .cwp file or it's associated audio files and if you don't manually save, all the changes you made to your Project.cwp file are lost.

If you record a new track and it Auto Saves, but you don't save your Project.cwp file, you will lose the changes in the Project.cwp file, but the Audio data will still be there for the AutoSave.cwp. So in that regard there is the potential to have a larger than necessary Audio folder when all is said and done but that's really the only draw back I see to it.

It appears that some people are very dead set against it but I sincerely don't understand why?

Bub

For once we seem to agree on something Bub.

Not that I think for one minute that everyone should use autosave. I guess I'm just pedantic when it comes to factual things so if someone says "I don't use autosave 'cos I don't want to / don't like it / don't trust it" or whatever that's fine. Each to their own. It's the factually incorrect statements that I question.

@randy - I wasn't referring to you specifically, rather just general incorrect comments I see on here all the time about autosave. When people make comments like "I don't want multiple copies of files on my system / it overwriting my files / to be in control of when I save / saving when I'm playing back or recording, etc" I just assume they don't understand how it works. The version of autosave I have is fully controlled by me as to when it saves, I can still Ctrl-S when I want, doesn't overwrite anything other than it's own file, only creates one file which even on huge projects amounts to no more than a few thousand kb, and most certainly doesn't save while recording or playing back, or on my under powered system stutter or stop playback. It just does it's thing without me knowing it's there.

Can't say I've needed it lately but it's nice to know it's there if I do ever get a project corrupts.

I'M with FBB on this on as well.  Saved my bacon the other night,  I got called to the phone in other room with the project running. It must have completed and auto saved after it stopped and then the power went out.  I fired up the auto save version and never lost a single edit. 

Bub - it saves everything that your normal save function does,  midi, envelopes, everything.  You have the entire project where you left it at the point of the autosave. 

I have never found it to be intrusive, sometimes a slight delay if I just hit the transport, but it has never bothered me but I have used it to retrieve files many times.

Who uses Auto save with SONAR?

Not me but my friend does...