Bristol_Jonesey

sharke


I don't like the idea of autosave but I've taken to hitting CTRL-S after every successful action I make. I do it subconsciously now. There is nothing worse than spending half an hour on some tedious non-fun editing task only to have to do it all again after a crash. Save save save. 

I've only started using autosave recently and I am SO GLAD I did!


It never overwrites your current project, it creates a new version for you

+many. There are loads of myths circulating about autosave. Here's what it doesn't do............

It doesn't interfere with,  change, or touch your original project in any way whatsoever. It creates a separate completely independent copy of the project.
It doesn't take loads of hard drive space. It's just a cwp file which are usually no more than a few thousand bytes.
It doesn't autosave during playback or recording. If a save becomes due while the transport is running it will wait until the transport stops and then complete the save.
It doesn't stop you pressing Ctrl+S and saving as you normally would.

I see many users de-crying autosave some claiming they want to decide when a save is made. The point is you can still decide, autosave just takes an extra copy for you. I just can't see one downside but there are lots of upsides. Not least of which is you end up with an extra copy of the project that may or may not be more recent than your original if the system does crash. Whether it is more recent or not depends on how you have autosave set up and when you last saved the original.

FastBikerBoy

Bristol_Jonesey

sharke


I don't like the idea of autosave but I've taken to hitting CTRL-S after every successful action I make. I do it subconsciously now. There is nothing worse than spending half an hour on some tedious non-fun editing task only to have to do it all again after a crash. Save save save. 

I've only started using autosave recently and I am SO GLAD I did!


It never overwrites your current project, it creates a new version for you

+many. There are loads of myths circulating about autosave. Here's what it doesn't do............

It doesn't interfere with,  change, or touch your original project in any way whatsoever. It creates a separate completely independent copy of the project.
It doesn't take loads of hard drive space. It's just a cwp file which are usually no more than a few thousand bytes.
It doesn't autosave during playback or recording. If a save becomes due while the transport is running it will wait until the transport stops and then complete the save.
It doesn't stop you pressing Ctrl+S and saving as you normally would.

I see many users de-crying autosave some claiming they want to decide when a save is made. The point is you can still decide, autosave just takes an extra copy for you. I just can't see one downside but there are lots of upsides. Not least of which is you end up with an extra copy of the project that may or may not be more recent than your original if the system does crash. Whether it is more recent or not depends on how you have autosave set up and when you last saved the original.

I don't use autosave. I make a second file that I call "xxxx backup" that I save to sometimes as extra backup. 
Sometimes autosave can start saving during critical tasks that can cause dropouts and sometimes even crashes. That is why I never use it on any DAW or program. CTRL S works for me and then I'm in control "when" and "what" is being saved.

Hi Freddie

I would suggest that you may have system issues if a save is causing dropouts and crashes. I've never had a dropout or crash from a save, auto or manual. Might be worth investigating given that you are having other issues as well, they may be related.

I use auto save and like it. If I have a crash I need to recover from I head to the project folder and make copies of the project files (very small files) and find the most recent one and try it. This has saved me a lot of headaches. Original Poster (OP), I see you are using Windows 8. Windows 8 has a built in scanner (see Security Settings). I have set it to bypass my Cakewalk folders. When the scanner is set to scan the Cakewalk EXE and the Cakewalk Folder it will burn your processor at load time making sure your wave files are safe. haha. No need for that. Just add your folders to the bypass list. BTW, if you don't add them, it will scan the cakewalk exe when you are bouncing tracks or even recording just to make sure everything is going as it should. This is just part of the setup of a new PC for a DAW. It isn't isolated to Sonar. BTW, Sonar is very stable on 8 for me. Actually, I would venture to say I have so far had my best experiences on 8. This may be b/c I'm getting better at it, but I believe the OS is a + in the equation.

FastBikerBoy


Hi Freddie

I would suggest that you may have system issues if a save is causing dropouts and crashes. I've never had a dropout or crash from a save, auto or manual. Might be worth investigating given that you are having other issues as well, they may be related.

Thanks Karl but I'm sure it works without any glitch with my setup. I just doesn't prefer to use it as a security measure.
I know by my own experience working with friends in other studios how it works. Autosave are available in all common DAWs.
 
 
Hypothetical example of Autosave bad behavior.
1. You editing a plugin suddenly the mouse freeze... what? It autosave the project...
2. 10min later... you hit play...then suddenly the locater freeze???? its autosave-time again...?
 
 
No thanks I think I skip that!

After having Sonar corrupt my correct project several times due to a bad bitbridged plugin versioning is the only thing that gives me piece of mind, at least you can go back to a later version, just saving over the same version would have killed that project for me.

Load the bad plugin, everything seems fine, work a bit... hit save, Sonar goes unresponsive and crashes, start Sonar again, load project and it's now "truncated"

I think that was the old version of leCab, the yellow one that caused this, I can make Sonar corrupt the current project consistantly just loading that plug.

I prefer the "tilde" for save (never have got used to control+s, don't miss the save icon anymore, use it in all programs that allow keyboard shortcuts)

control+tilde for save as

T

my recommendations... go win 7. Sonar x2 does not have win 8 drivers. Turn autosave in x2 every 10-20 changes. Turn off ram and processor power saving in the bios menu. do all the usual pc optimizations in windows for pro audio. If that dont work, yer buggered tbh.

Swiller


my recommendations... go win 7. Sonar x2 does not have win 8 drivers. Turn autosave in x2 every 10-20 changes. Turn off ram and processor power saving in the bios menu. do all the usual pc optimizations in windows for pro audio. If that dont work, yer buggered tbh.

"Sonar X2 does not have win 8 drivers"? Funny Sonar X2 is running fine on my Windows 8. BTW X2 doesn't come with drivers. 

Before sonar, I used cubase sx, got real lazy at saving as it never crashed until the day I lost 6 hours work. In a way, sonars tendency to crash for me at randomly frequent intervals has made me an advocate of saving after every change and as such, crashes never bother me now as I know I can restart from where I left off. I wouldn't trade sonar for the world now, think its the best daw by a mile, both for functionality and bang for buck.