My auto-save works perfectly ... set for every 50 changes (which isn't that much considering if I am just testing presets in a synth, they count that as a change)

Dunno what could be going on ..

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

I forgot about this. It isn't "auto", But I have done this over the past three or four years now. When I make big changes, get a good take, things like that, I don't care if it just autosaved, I still hit "the combo"!

Chregg


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

+ 100000000000000000000000

Ditto, I tried using auto save on a session once until it started saving right in the middle of precise edit which ended up in errors.
Been using the "built in" version ever since.

Usually autosave seems to work fine for me.  Where I start running into problems is when I have projects that have a lot of samples loaded into RAM.  The last few projects I've done used a lot of the EW Symphonic Orchestra.  I had several instances loaded & about 8 gig of RAM loaded. Every time I made a change it would autosave... and with a project like that the autosaves takes 10 seconds or so, which is a real flow killer.  I ended up turning it off & putting a big note on the side of my monitor that said AUTOSAVE IS OFF!!! to remind me to save more often.
 
'Hope it gets fixed in X1b!

I never use Autosave. It drives me crazy having the computer set to "Smarter than me" so I leave it off. It has burned me a couple times not having it on but I save with out even noticing it using Ctrl-S. I sit there, play back something, hear a small "fart" in the audio wondering what it is, then realizing it was me hitting Ctrl-S

It's Auto enough for me

Having said that, I tested it a few versions back and it seemed to work great. Unless something has changed I'd imagine that it would be pretty much the same still.

Auto-save has always worked fine for me from the original Cakewalk to X1. But CTRL+S is a much safer and better way to keep your project saved. Autosave, like so much else on your system, runs without your bidding, and therefore interrupts your program to do its thing. I'd rather do the manual save frequently, knowing that auto won't push me over into a dropout.
 
Good luck!

Wouldn't it be nice to have an auto-save with a "save-as option" (or a save-as shortcut) that would automatically number a save sequentially?

The auto-save does have versioning, or at least it did in 7. As far as the "save as" thing, that would be pretty easy to affect on your own. Now if they could keep it from crashing, that would be a good thing... <SMILE>

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

I noticed that some use the 'x amount of changes' vs. time. These seem to be the folks that are happy with autosave. Maybe something there and maybe the argument is about the timed autosave. For me, I have it set to like 20 minutes. But, it will autosave whenever it feels like it. Using the 'x amount of changes' is sort of ridiculous as any you could dittle with an eq for 3 minutes and eat up 30 changes.

All that said, to me, the big problem is just the amount of time it takes (sometimes) to save or autosave.
I mean, not much has changed in the last 20 minutes with the data, but, still save or autosave can take up to 45 seconds. that's ridiculous and a huge inspiration killer.

Hey Bob Cain. Yea, been here for 20 years or so:) Thanks for the kudos on the CD. Glad you like it. I'm sure autosave was used during the creation (just staying in the thread:)  Nice to see you (we've done this before BTW:) LOL..

timidi


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

I noticed that some use the 'x amount of changes' vs. time. These seem to be the folks that are happy with autosave. Maybe something there and maybe the argument is about the timed autosave. For me, I have it set to like 20 minutes. But, it will autosave whenever it feels like it. Using the 'x amount of changes' is sort of ridiculous as any you could dittle with an eq for 3 minutes and eat up 30 changes.

All that said, to me, the big problem is just the amount of time it takes (sometimes) to save or autosave.
I mean, not much has changed in the last 20 minutes with the data, but, still save or autosave can take up to 45 seconds. that's ridiculous and a huge inspiration killer.

Hey Bob Cain. Yea, been here for 20 years or so:) Thanks for the kudos on the CD. Glad you like it. I'm sure autosave was used during the creation (just staying in the thread:)  Nice to see you (we've done this before BTW:) LOL..

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.