Thu Mar 31, 2022 11:55 pm
@berdinho10
Thank you for this. I'm recently updated to Davinci Resolve Studio 17.4.6 Build 4 and have been getting this error for a very long time.
This has been happing for me ever since the "auto-save" feature was implemented.
I finally found this workaround today.
I'll admit, I've been dealing with this for so long and the only way I could get it to save in the past was to close the program and lose all my progress. This frequently resulted in having to redo hours of work.
And I was checking to make sure it was saving along the way. It would stop and then when I reloaded it would revert HOURS back. So it was giving me false positives for saving (or it's reverting to some slower to save restore point, not sure which).
Either way, it was about to happen again, I finally found this workaround, did it, and it saved. I closed and reloaded the file to test and it was up to date.
Yay.
I really do hope Davinci Resolve fixes this soon. It's been well over a year of frustration for me on the Studio version.