rapapar wrote:Highlight Stretch is the main cause of trouble here
What is Highlight Stretch?
For years and years and years, we've done three things to work out the
rare case of corrupted projects:
1) be prepared to export the project from the project manager, then import the exported project and see if that new project copy has "uncorrupted" itself
2) keep the system you're working on as simple, un-modified, and powerful as you possibly can, and don't run anything else in the background (except really light-duty stuff like notepad). Whatever you do, don't run anything that tries to use the video drivers. And don't touch the system during renders.
3) have a second system (if you can afford it) and be prepared to use the second system to examine or fix the original bad project. This goes back decades to Avid, Final Cut, all that stuff: sometimes one person's log-in allows the session to open, but the original owner's does not.
I have had cases where Resolve choked because of a bad plug-in, but they do at least give you the ability to turn off plug-ins while you're in Project Manager (and not opening up a project per se). Our solution was: kill the bad plug-in, delete it, and Resolve should then run OK.
And add to this the constant reminder to backup every single day. I think I've only had it happen 3 or 4 times in 13 years, but once in awhile, you need to restore a backup to recover from a crash or a drastic mistake (like deleting a timeline or shifting several hundred clips by mistake, or unintentionally doing a Global Ripple).