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

I NEVER rely on auto save in ANY software.

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

Autosave does work but it could be made better. More Efficient. Cotrol S is good to save to the original file when your not in the heat of the creative process and making numerous changes and things are just falling into place. Oh Wait! stop the creative flow to control S-Ok now back to the process. Autosave should not make my system glitch every time it decides to do its thing. IT SHOULD BE SMOOTH!!!! HINT. Yes. Versioning would be nice. Like levels of undo. I could select an earlier autosave or a more recent one since it may be set to do it frequently. How ever many times it is set to, it should not cause the system to glitch. It should also be smart enough to not try to save in the middle of someone working but as soon as there is a break for X-milliseconds.. whatever number that may be to autosave Efficiently and smoothly. If i wanted to control S I would not be using autosave????? ok other people.

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 find I can't set it to something more minimal. Even when I have it set to 15 minutes and every 200 changes I see it auto saving way more than it should. Regardless I choose to leave it on especially for the versioning.

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

If your autosave saved when you inadvertently delete something. You go back to that point in project and control Z. I don't think that would be typical. Would it?

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.

What would be really nice, mind you, would be if it managed to save in a slightly more "background" way. I don't imagine this would be a small task, but it would be great for usability. Somehow get a snapshot of the project state and save that, and let you carry on working while it does.

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