.

.

I tried it for a while and didn't like it.  I save ever few edits manually.

mike_mccue


 Here's what I do:  I "save" after making edits and I "save as" after making significant edits.

auto save has 2 options: save every X minutes, or save every number of changes you made
plus you have "enable versioning of projects cwp" which all basically do automatically what 
you are doing right now manually. I like that cwp versioning he best.
  
All those setting are in edit->preferences->file->advanced

I'm not a big fan of auto saving (in any application). I save whenever I think I've added something worthwhile to a song and I'll save a version at logical (to me) milestones in the songs development. I also backup every weekend to an external storage medium.

Regards,

rbowser


(footnote - the Forum's text scripting is off this morning, on my machine anyway - I couldn't pull out the quote I wanted, and formatting tools like bold, italic, aren't available. ---?)

FireFox 6???? 

I also suggest saving to the cloud.

rbowser


"...Here's what I do: I "save" after making edits and I "save as" after making significant edits..." Word for word out of my own book, Mike. That routine works for me. I haven't lost work in years. My project folders aren't over-flowing with multiple versions, just a reasonable number of them. And it feels good that I'M under control of saving. No problem - auto save is a fine option, I'm sure, but I so don't need it. RB (footnote - the Forum's text scripting is off this morning, on my machine anyway - I couldn't pull out the quote I wanted, and formatting tools like bold, italic, aren't available. ---?)

snap

I use Auto Save and have it set to save every 60 seconds. The reason I do that is I seem to have fewer crash related problems with plug-in's, bitbridge, drivers ... etc. I've never had it cause stuttering like I've seen a few folks report, but I'm not saying I don't believe them ... I imagine it depends on buffer size and the size of your project/.cwp file.

I never save the actual project .cwp until I'm 100% certain I like the changes I've made. Having it set to 60 seconds pretty much ensures that 99% of the changes I've made are safely stored. You don't have to set it by time ... you can set it to save after so many changes. I prefer to do it by time because it just seemed to make my system more stable when it saved on a regular basis.

The reason I went to 60 second intervals is, I used to have it set for 5 minute intervals but had some crashes that corrupted my regular project file and then I had to go back and make too many changes, so I set it for 60. I seem to have much fewer problems with crashes with it enabled and I have a project open for a long period of time.

I did stop using Auto Save though in X1 because there is a bug that causes the Tool Bar to lose all it's icon's and turn gray on some systems with it enabled, unfortunately mine is one of them.

"Bristol_Jonesey"
Nope, never use any sort of Auto save on ANY program, including Sonar.

It's either ctrl + s or I'll do a save as if what I've just been doing is important or radical enough to warrant an incremental name change

Ditto. Word for word. 

John T


Regarding the "under control of saving" thing, I'm guessing that at least some people don't know exactly how it works; it's actually quite nifty, and deals with that issue rather well.

If you open a file and start working on it, the auto-saves are not saved to that file. They go to a seperate copy called "Auto save of xxxxxxxx". You can work all day and not change your original file at all. It's only when you do a user-invoked Save that the original is replaced. If you don't do a user invoked Save at any point, you'll still be able to get to the auto-saved version as well as the original.

That's interesting JT,
I guess I'm in the "don't know how it works" camp as I don't use it.
Didn't like how it was implemented in the past, but I may have to try it again.
Then again, I haven't lost any projects with corrupt files or crashes for I don't know how long, so I guess it ain't broke...

...never use any sort of Auto save on ANY program, including Sonar.

Ditto here. I want to be in complete control of when and how I backup. I'll often experiment with synths and effects and mix techniques only to decide that the result isn't what I was after, at which time I simply close the project and re-open it to get back to where I started. With auto-save enabled I'd have accumulated multiple copies that would be of no use, taken up disk space and only add confusion if I ever really wanted to back-rev.

CTL-S is a reflex action. It's how I express "ooh, I like that take!"

John T

I think a great enhancement would be to get the Sonar open file process to handle all this for you. So rather than having to go messing about in the Windows file system digging up your version file and auto saves and so on, you'd just go to your usual file, but with some selectable options like "choose from version history" and whatnot. More a change in presentation than in how it actually works. I think more people would get more use out of it.

That's a great idea.

I do it just like bitflipper!

"...Ah good old Autosave. IMHO the single most mis-understood function in Sonar, an opinion backed up by some of the comments so far..." Well, FBB, I'm sure 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. Just because someone doesn't use it doesn't mean they don't understand it. It's really a pretty trivial topic, the discussion is fun enough though. It doesn't matter what someone does to protect their project files, as long as they do something which is effective for them. Randy B.

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