According to Cubase (10) I havn’t done anything important from 12.12 to 12:47.
Again from 12:47 till now (12:57) all I did was crap and didn’t deserved being autosaved.
Truth is - that for testing I just drev some midi parts, changed some presets and loaded some other presets.
If Cubase were to crash now all those changes would be lost.
From what I can tell, and I just tested it, autosave is somehow linked to playback. It seems if playback is not running, Cubase isn’t saving. It it also not saving WHILE running but it will save once stopped again.
Steinberg please explain how the autosave function works and fix it so Cubase autosaves when changing stuff.
Just think about all the stuff that can go wrong???
My thoughts on this (no testing, just my years of observation and the disappointment of loosing some edits)…
The autosave function seems to not save anything during recording or playback. That might be a good thing to prevent artifacts during those functions. But, the autosave clock seems to start over again after you record or playback anything. So during certain editing sessions (like when you do a few edits and do quick short playbacks to hear what what you just edited) this seems to cause huge amounts of time between auto saves. It would be better if the autosave clock would continue as set in preferences and, if past the set time in preferences, activate immediately after stopping the record or playback function.
Yes this is indeed a problem. Autosave in C10 is also bizarrely unpredictable - I have mine set to intervals of 3 minutes, so technically my project folder should be full of .bak files - but after working on a film score for several hours, the external I was running the session off got disconnected accidentally rendering the project file corrupted, and when I went to look for .bak files there wasn’t a single one there. Cubase, for whatever reason, simply didn’t create a single backup file in all those hours of work. Had to do everything from scratch over again.
I just lost 5 hours of vocal editing due to the same problem so hoping for a fix really soon. I remember this happened a few times in earlier versions as well.
+1
I made a part of my workflow ctrl+alt+S. Every change i make, i hit this combination. I cannot rely on the auto save feature and risk many hours of my work.
I end up a project with over 200 saves.
Just an FYI… the “Autosave” function has not worked properly for many years now. So going back to 9.5 won’t help as it relates to it.
Of course if you are having other issues with V10 then, yes… working in CB 9.5 would help while you were figuring out why V10 is crashing on you. Many (including myself) think that V10 is the most stable yet. Maybe you want to start a new topic to see if someone can help you with your V10 crashing.
It works as it’s designed, whether that equals “properly” is a mater of opinion, I suppose. But let’s be clear about what the issue is that people don’t like. That autosave doesn’t save while the transport is running.
That’s my view as well. It would be nice to some built-in advanced options for saving, but external methods like autohotkey, keyboard maestro , or human left thumb and index finger tapping work…
It might work as designed but, it does not work like it is described in the manual. Meaning… no where in the operation manual does it list that autosave doesn’t save while the transport is running which may increase the autosave interval by a who knows what amount of time.
So technically that makes it most likely a bug… or an error in the OM. Either way… we are discussing it’s shortfalls here in the forum feature request section. Same section where it has been discussed for years and apparently where the concern has fallen on the deaf ears of those who can improve (fix) it.
Logic Pro X has true background auto save. There is no need to set a save interval. It also doesn’t interrupt the user workflow during auto save or manual save.
No, you’re right. The OM should at least have some “Notes” about usage of auto-save. As far as I can determine, I have not had any problems as a result of Auto Save, per se. I have it set to the 15 minute interval which I think is the default.
All I can say is – as we all know – save early, save often.
I’m quoting myself from another AutoSave related thread here: “Logic indeed has a “save at crash” function that does work like a charm. I suspect they do something similar to what Adobe does with some of its titles. My guess is that like InDesign, (for example) Logic is constantly updating a duplicate of the project data in a recovery cache that’s memory protected from the host program. If a crash occurs, it dumps the cache into a recovery routine when the program is restarted.”
When restarted, Logic will immediately present a choice of launching from the backup cache or the last manually saved version. The Adobe products do the same thing. Nice touch.
And as Logic’s AutoSave function works in the same non-invasive and invisible fashion as the Adobe title’s autosave functionality, it stands to reason that the methodology is cross platform and not restricted to being an “Apple OSX only thing”.
