I have mistakenly ordered Nuendo to quit without saving, only to find out that all the autosaves since last saving were deleted, along with all the audio files that had been created.
WTF? This should not happen in anyway. Autosaves are there for a reason, it can’t be one click away from deleting everything.
If I click to quit without saving, all the backups and audio files created should remain where they are. Or at the very least there should be a dialog stating what will happen, and asking me if I’m sure, just like it happens when the project has never been saved at all.
Please fix this as soon as you can!
Thank you very much, as always.
I didn’t tell Nuendo to “not save anything”. I told it, by mistake, to not save a specific project file before closing.
What I expect is autosaves are preserved, as they should be.
Also what I expect is that Nuendo NEVER deletes any audio without my express decision.
Furthermore, what I expect is that it does what it is told, not extras on the side. It didn’t ask me if I wanted to delete all my autosaves, and it didn’t ask me if I wanted to delete audio files. (by the way this is directly contrary to the behaviour in a similar situation, where it tells there is new audio, and if you want to preserve it.)
And finally, I expect it to be on my side and help me when I make mistakes instead of leaving all these irrevocable actions be behind one single click.
If you generate data in a project, like recording audio, the files will still be present in the pool.
But if you once answered the question if recorded material should get saved with no, and ticked the checkbox “don’t ask again”, indeed Nuendo will delete the files if you don’t save the project.
Dude what are you? The Advocate for Bad Implementations?
Haven’t you read the post?
The dialog you mentioned doesn’t even have a “don’t ask again” option.
Please, unless you have positive contributions to make, refrain from further interaction in this thread.
IMO your expectations are perfectly valid and the autosaves should have been preserved.
However, if you choose ‘Don’t Save’ you should get a second warning pop-up which asks if you want to delete the audio files created since the last save.
AFAIK autosaved backup files should never be deleted - it sounds odd that they were deleted in your case.
Yeah, that was the most strange to me. So after you said it I went to investigate further and I found the problem:
When you use “make extension permanent”, you are not creating a new audio file strictly speaking, so if you choose “no” to the “Save Before Closing” dialog, you get no warning and lose all and any work on extensions even after “making permanent”.
Also, DOP “make permanent”, which are said to “be not able to be undone”, are undone if you close without saving.
And unfortunately, my test confirms the worst: if you close the project without saving, willingly, autosaves ARE DELETED!
If it crashes, which I simulated with an “end process” in task manager, it does keep the autosave, at least.
But bottom line is we are, in some cases, one click away from losing hours of work.
Please fix this, Devs! Autosaves need to be kept in all situations! Extensions and DOP “make permanents” should prompt a dialog to confirm deletion.
Sometimes by the end of a long day we are tired and we click on the wrong stuff, and we also forget to save. Please don’t punish us for it.
Can someone acknowledge this issue here, please?
Thanks!
How frequently does your system autosave (every 15 minutes, every hour, once a day)? Could it be possible that autosave was not triggered during that session even though it was switched on?
My autosave is set at 5 minutes interval, and I lost a couple of hours of work, so there should be plenty of .bak files.
But to be sure I tested it in a controlled manner and it does delete the autosaves if you willingly quit without saving. It keeps them only if the program crashes or is force quit.
Furthermore, it seems that Nuendo doesn’t consider “made permanent” DOP and Extensions to be “new audio files”, so in the case of quitting without saving it won’t ask you if you want to keep them. It’s one click and POOF, everything is gone.
If you look at this another way round you could argue that if you quit without saving then you want the project to be put back to the state it was in before you made any of the edits - and this would mean undoing any of the DOP and Extensions operations you may have done (designated permanent or not). My take on this detail is that steinberg have got it right. If you changed this it would mean that ‘quit without saving’ would no longer mean ‘without saving’ which, in my opinion, would risk being even more confusing.
No time to properly test right now but I’m guessing this may be as designed and that there are cases where this is logically correct.
Well ok, maybe they are by design and it makes sense for some cases. But my argument that we shouldn’t be one click away from deleting hours of work still stands, IMO.
We need at least a confirmation prompt, stating everything that will be deleted, so we can back off in case of a misclick.
Keep it all as it is and add an “are you sure or just half asleep???” dialog and I’m happy.
