In SawStudio there is a very useful save copy as feature.
In SAW a job .edl is termed a “session”. So, the dev created a “save session copy as” file menu item and what this does is create a copy of the session without opening said saved copy. It saves A LOT of back and forth when versioning.
It could be very handy in SL
Incremental ”Save” like in Cubase/Nuendo would have been nice.
There’s an autosave function that works quite well, after a (standalone) SL crash when opening SL again it will almost always ask if I want to open an autosaved version. And when I do I will mostly get to the point where it crashed.
After SL crashes; the re-open SL>
the Restore dialog pop-up does not make sense to me
when I have chosen “Reset”, then I’m OK and go back to where I was at or near the point of crash
choose anything else and I find my jobs hosed…as if the “old” back up was my first ever save
but, really, I don’t know what the buttons are supposed to do on the Restore dialog…sure, I can assume…but I do not “know” what each selection determines
It’s been awhile now since I’ve had a crash so I don’t remember exactly what the dialog pop-up looks like, but when it does pop up it says something like there’s being an older project file on the hard drive, and it asks if I want to open that or not.
So that’s what I do; then I can often see the last autosaved project as one of the tabs above the Overview bar, if not the only Project tab.
It might perhaps be a bit of trial and error what the different buttons in the pop-up will lead to, although I think they’re quite self explanatory. Don’t be shy to try out the different choices when starting SL after a crash, nothing bad could happen.
I find though that SL is more stable now and the crashes happen very seldomly to me, as compared to like in June.
On the contrary, I just lost about 10 days’ worth of work. I’m now saving safety copies as I work. I had to start over. This is terrible advice from you. I’ve had similar problems before on less important projects…test projects, for example, hence why I haven’t said anything about it before.
The Dialog says something like this:
Title bar: “Restore Project?”
EDIT: It’s not “Restore”; it is “Recover”
Dialog text: “Old Project Back-ups found, would you like to restore previous project?”
? icon
button1: Reset
button2: Yes
button3: No
every time I have clicked “Yes” I have had a problem, because of that I usually choose “reset”
Like my other thread says, (like you) I can assume I know what each selection does, but in reality (possibly unlike you) I do not actually know
Are you sure this happened because clicking the ”wrong” button? Couldn’t it rather be because the file actually was corrupt? I’d think that would be more plausible.
I have quite a few slp files…no, I’m not sure
BUT, the layers disappeared after my actions of the Restore Project dialog
EDIT: again, my syntax is incorrect! The Dialog box syntax is “Recover”
And I do not think you can know if the Restore Project corrupted my job or not
EDIT: again wrong, I mean “Reset”; “Restore” does not exist on the “Recover Session” dialog pop-up
As far as my job corrupting, the sources were 2 comps (wav files) that were not altered after putting them into SL…nor were those sources moved. All my work was in standalone and so far has all been in standalone.
your contention that:
is a guess on your part that may well not be very good advice at all. If you have deeper knowledge, then be so kind as to validate it?
if anyone is working on any slp, I would encourage a
back up/ safety strategy; that is what I will do going forward
again, I do not blame SL or Steinberg or Robin for my lost work…that lost work is on me 
obviously there was an issue with my install as per my screen shot of win explorer
I regret that you lost your file and I understand that you feel bitter about it. We have all been there, one way or another.
Of course I can’t know anything about your files, if they where corrupt or not but I feel quite confident that choosing a function that is aimed at restoring a lost job should be safe, so I have no problem with recommending that.
Like you say, it is always good practice to backup one’s work. Autosave helps with that and an incremental save function would be great in addition as a sort of belt and braces.
I don’t feel bitter about this situation. Stuff happens, dust yerself off and get back to work.
Logging procedures helps other potential users, it’s the only reason I contribute here is to learn and help others if they are looking for help here.
I’m not looking for sympathy, just purely pointing out I do not understand the Restore Project choices and what they are pointing to…Shadow copies? I don’t know…I haven’t found any info on how it works.
Frankly, my POV is of production and arriving at an effective workflow…emotion is not my intention
again, that is your assumption…as it was mine…yet was not my personal experience…
It is my experience.
But you do not know how it works as you have previously said
of course you have had a certain experience, but which you said was the dialog pop-up options are “self-explanatory”
further:
The dialog does not have this syntax.
I do not see a list of previous saves.
I typically have only one slp or wav open as a separate job in SL.
Seriously, my intention is not to tussle with you, I’d just like to KNOW what the various options are actually built to do, cuz I’ve lost a bunch of work after choosing “Yes” and I find no explanation in the Owners Manual.
And I’m supposing only @Robin_Lobel will know
Apparently we’re not talking about the same dialog window.
I have all the time been talking about the dialog window that pops up when starting SL after a crash. I thought I was clear about that in my 1st & 2nd post.
yes, we are talking about the same dialog pop-up when re-launching SL after a crash!
I’ll figure out a force crash and post the images…not that I have time for that…but to clarify when it comes up…I can’t do it right now
Ok, well I don’t think I have anything to add that can help so I’m out of the discussion.
Here is the dialog pop-up for SL11 upon re-launching SL after a crash thanks to @Sunnyman :
oh boy, what did I start?!? now we both using the term “restore”…in your case, here, seems a perfectly fine use of the term…where I totally screwed up earlier
