Blimey, I can't believe the level of interest in autosave! That said, I'll add my tuppenorth... I definitely need a reliable, regular save (cos, crashes) that is as invisible as possible. I very rarely need to go into autosave vault. Current behaviour is actually pretty acceptable (though I would like control of 'inactivity' period with a 'force at X mins' override - see 5. below) 1. Seems like this isn't 'background save' as I'd understand it, or it wouldn't wait for a break in editing. It's just hidden the progress bar. Which is fine. 2. Presumably 'waiting for a break' is current behaviour too - which explains why I see much longer gaps in autosaves than the 2 mins I have it set to. 3. Please make 'autosave saves current project' the default. Especially in productions. With this set (which matches behaviour in Avid) the *only* two reasons to need to go to autosave vault is a. corrupt project file (rare) or b. to revert to a previous edit (also rare with sequence versioning) 4. The copy of the current project in the autosave vault is then pretty much redundant + a waste of cpu/storage io. Last modified version in vault should be the one *before* current save. 5. Avid offers granularity in the 'break in editing' wait. So you can set autosave to 3 mins, with 'inactivity' set to 15 secs, but 'force' autosave at 10 mins. 6. Could the 'vault' versioning be set to keep, say, last 5 autosaves, then hourly + 24 hourly autosaves. (Maybe done on file size rather than strictly on time + would therefore better reflect big changes).
... View more