jamesyoyot


Autosave seems to have a mind of its own on my system. I have crashed several times when attempting to do something and then Autosave indiscriminately decides to start saving.

Yes it will do that when you have it set to "Auto Save Every 5 Min" then when 5 minutes comes around it autosaves like you told it to do. It doesn't care what you are doing. And I believe that's a lot of the reason some don't like autosave. It will try to save while you are recording a trk. It will save when the time comes.

However, if you have it set to "Auto Save every XX Changes", it won't do it while you are recording, it'll wait to save after your finished. That's what is good about that option.

 

Grem

jamesyoyot


Autosave seems to have a mind of its own on my system. I have crashed several times when attempting to do something and then Autosave indiscriminately decides to start saving.

Yes it will do that when you have it set to "Auto Save Every 5 Min" then when 5 minutes comes around it autosaves like you told it to do. It doesn't care what you are doing. And I believe that's a lot of the reason some don't like autosave. It will try to save while you are recording a trk. It will save when the time comes.

However, if you have it set to "Auto Save every XX Changes", it won't do it while you are recording, it'll wait to save after your finished. That's what is good about that option.

Ummm, yeah, except it will save whenever the hell it wants to, not following either of those parameters. It will save in such an unfathomable manner that never happened in earlier versions.

Yes it will do that when you have it set to "Auto Save Every 5 Min" then when 5 minutes comes around it autosaves like you told it to do

no, it doesn't. hence this thread. If it works for you great. But, that doesn't mean that those that it doesn't work for properly are imagining things. As James said, it has a mind of it's own.


That said, and as I said earlier, the worst part of autosave is the 'save' function which sometimes takes forever. 
 so, I submit that the save function is more broken than autosave.

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...

Another thumbs up for this post - It's so easy to make CTRL+S a part of your routine.  I'm often saving several times each minute as I'm working on edits.  It's just an easily ingrained habit.  I'd never let Sonar or any other program decide when it wants to save for me.

I was happy to see in the excellent Groove 3 video tutorials that everyone was raving about, that the advice given in one tute was not to use auto save, but to use CTRL+S instead.   Just start making CTRL+S part of your work habit - you'll be "auto saving" without even thinking about it in a very short time.

Randy B.

Amazingly stupid that Sonar will autosave immediately after you cntrl/save.

Yes & no, autosave saves to it's own file so sometimes I'll use it like a temporary versioning if I'm off on a tangent with a project. I also regularly use Ctrl-S under normal circumstances which as pointed out I also have control over.

I noticed you also said saving takes a long time, do you find that all the time? I've recently had that on a project where saving takes several seconds (5 or 6+) where normally my projects save in no more than couple of seconds regardless of size. I think that must have been some sort of quirk with that one project, it's the only one that has ever taken that long although others have mentioned Audiosnap can cause saving to take a while if it's applied to tracks even if not actually using it.

I also find size of a project has little to do with save time, as far as I understand it the save is saving pointers and layouut etc rather than actual audio which is saved as it's written. Having said that I use lots of external gear rather than virtual instruments so that may make a difference.

If my saves where taking several seconds I wouldn't be using autosave either. AFAIK autosave has never saved for me while recording or playing back either regardless of settings.

I've had CTRL+S built in since Windows 95.

You guys do know that cntrl/save has nothing to do with autosave not working correctly.
It is another workaround.
It's Like saying, I don't need audiosnap, I tap my foot.


I use cntrl/save. But, I also would like autosave to work like it's supposed to.

Grem


  I don't use "save every XX minutes" because I always forget that I have it set to that and There are certain things you don't want to be in the middle of and the time comes up it will save no matter what. But with "save every 10 changes" it won't save until your done with the thing your doing, then it saves right after.

and that's the wisest way to use it I believe. sometimes you are making some changes so fast and sometimes you just want to listen to the mix 20 times just to make sure. in the first scenario, sonar will autosave the project after X minutes (maybe 50-60 changes if you work fast, which means you are screwed if evil strikes), and in the second scenario you are just listening to the music and sonar overwrites the same project without any change.

I use cntrl/save. But, I also would like autosave to work like it's supposed to.

It does, doesn't it?

i believe it does!

this question was first adressed to Ross in the comedy series "Friends"!