RRRRegis wrote:I spent the whole day working on a Resolve (18.5) Project. After I tried to render the last piece (5 renders total) it crashed. When that happens (not very usual, fortunately) Resolve saves most of the advances on my project, and on top of that I got the good habit of always CMD+S every amount of minutes. But this time that wasn't the case, Resolve re-opened a 6-hour earlier version of the project. How is this possible? I can understand it didn't save the last couple of minutes (I got the live save feature "on" btw) but losing ALL 6 hours of work because of a crash when I saved multiple times throughout the day? Doesn't make sense at all.
I've been using Resolve for more than 13 years, and it's rare that it happens... but I've seen it happen twice (out of thousands and thousands of sessions).
Some possible fixes:
1) on the Edit page, copy the entire timeline (all clips) to the clipboard.
2) with Dynamic Project Switching turned on in the Project Manager, start a new project
3) create an empty timeline and paste all the clips over from the bad project. You now should be able to continue working. (You will of course have to recreate your bins and setup and so on.)
Method #2:
just create a new empty timeline in the bad project. Sometimes, this gives Resolve's save mechanism a kick, and it suddenly starts saving again. (But no guarantees.)
Method #3:
Highlight the timeline name in the bin on the Edit page, then right-click and try to export a DRT of just the timeline. In a different project, import that DRT in a new project and that should work (if it lets you do the export).
I know these problems are frustrating, but they are incredibly rare. In general, Resolve is fairly rock-solid and rarely crashes -- at least for me.