I'd never trust any sort of autosave.

It's all too easy for it too kick in when you've just inadvertantly deleted something.

No, it's Ctrl + S all the way here.




As for versioning, that itself opens up a whole rats nest of misinformation & problems.


It's all too easy to fall into the trap of simply doing a "save as" and incrementing your project from e.g. "My Song 1.1" to My Song 1.2"

Then, one day, you decide to clear out your system a bit and you realise that there is no easy way to delete not just the .cwp of whatever song it is you want to clean up, but also all the audio tracks that go with it.

These will all mount up in the project audio folder and you won't have a clue which bit of audio goes with which particular version.

(A workaround is to do a 'save as' but to a totally different part of your filesystem, this ensures that Sonar COPIES all the audio files to the new location, provided you've got that option checked).

Now, you can do what you want with all the other, outdated versions, copy to Backup & delete being my choice.

I freed up 250Gb of disc space over the weekend, just from doing this on 15 or so projects.

Using the reliable, user-controlled CTRL+S isn't a "work-around," -it's how saving works in Windows.  Auto Save is there for people who for some reason prefer a computer to decide when to save, but I have no idea if it's working correctly in X1 or 8.5, or any version of Sonar, since I don't find it a useful concept and don't care to test it out. 

I'll go with the expert advice in the Groove 3 videos which suggests users stay with the solid, reliable CTRL+S.

Randy B.

Not sure what is causing your issue but Autosave doesn't save while the transport is running, that includes during recording.

Bristol_Jonesey


I'd never trust any sort of autosave.

It's all too easy for it too kick in when you've just inadvertantly deleted something.

No, it's Ctrl + S all the way here.

Same here.

Loptec

Bristol_Jonesey


I'd never trust any sort of autosave.

It's all too easy for it too kick in when you've just inadvertantly deleted something.

No, it's Ctrl + S all the way here.

Same here.

2 things, first - OLD THREAD ALERT!!!! This was originally posted in 2011

Second, I have now revised my thinking on Autosave and use it all the time in X2a

markyzno


Just use CTRL and S and dont rely on auto save....

I NEVER rely on auto save in ANY software.

FBB - Mythbusting mission (again) - I can see how the confusion arises, as autosave in a lot of software overwrites the current project or file. This does not happen in Sonar. It creates a second file called "Autosave copy of <your filename here>". Here's few myths exploded.....

• It makes no changes to your original file at all.
• It doesn't take away your ability to save when you want with Ctrl+S.
• It doesn't save while the transport is running, it will wait until it is stopped.
• It does give you a second copy of a project should the worst happen and may well save you a lot of heartache if a project ever gets corrupted.

The only reason I could possibly think of for not having it on is if you're working on a minimal powered system where a save takes time. Other than that autosave is a valuable safety net that you'll never realise is on, until the day disaster strikes and you'll either pat yourself on the back for having it on or curse and swear about how you've just lost minutes/hours/days/weeks/months* of work and wished you had turned it on.

*delete as applicable

HMusikk

BlixYZ
my autoosave works perfectly.

Mine too. I have it "built in" in to my fingers... almost evertime I do some changes my finger hit Ctrl+S "automatically... and this goes for all other Windows based program I use...

+1

I Still dont trust it, goes back to a few losses from 8.5...

Theres another tip I use which is every MAJOR change hit "save as"

FastBikerBoy

markyzno


Just use CTRL and S and dont rely on auto save....

I NEVER rely on auto save in ANY software.

FBB - Mythbusting mission (again) - I can see how the confusion arises, as autosave in a lot of software overwrites the current project or file. This does not happen in Sonar. It creates a second file called "Autosave copy of <your filename here>". Here's few myths exploded.....

• It makes no changes to your original file at all.
• It doesn't take away your ability to save when you want with Ctrl+S.
• It doesn't save while the transport is running, it will wait until it is stopped.
• It does give you a second copy of a project should the worst happen and may well save you a lot of heartache if a project ever gets corrupted.

The only reason I could possibly think of for not having it on is if you're working on a minimal powered system where a save takes time. Other than that autosave is a valuable safety net that you'll never realise is on, until the day disaster strikes and you'll either pat yourself on the back for having it on or curse and swear about how you've just lost minutes/hours/days/weeks/months* of work and wished you had turned it on.

*delete as applicable

I have the same problem as the OP. If I set it based on time, the frequency of saving seems to bear no relation whatsoever to the value set.

+1 john T. Now we're talking. Smart tool. ok smarter autosave. haha. Yeaaaaahhh!

I have set for every 10 minutes and 0 for changes. And it seems pretty damn random. It's not a big irritant to me. Or at least, having lost lots of work in my time, it's the much lesser of evils. So not one that massively bothers me, but wanted to confirm that the OP is not mistaken. Dunno whether it's a system config issue or what.

What I would like to know is whether it has a set minimum time period..mine seems all over the map.

Could very well be. 

Maybe I might do some checking about this a little later again.

John T


Yeah, it never initiates a save during playback. Ah, actually, I've just realised what it could be. If a save comes due during playback, it will save as soon as you stop the transport. However, maybe it doesn't reset the timer. So rather than an X minute wait til the next save, it sticks to the previous schedule, and so the next one feels "early". Bet it's something like that.

Yeah that'd make sense (as to why it works as it does).