I'm experiencing silent database corruption when moving bins (I'm using 18.0.1 Studio, but I have no reason to believe it's unique to this version). I'm in the process of reorganizing my footage, so I'm consolidating bins into other bins.
When I do this, everything appears to work correctly ... until I leave Resolve. The next time I open the project, the bins show up as "invisible" folders, without names, and the bins are completely empty, with all clips and timelines missing from the project (this can be partially confirmed by looking at the "timeline" count in the project manager — corrupt projects show fewer total timelines). This screenshot shows what that looks like:
The only way to recover is to restore from backup.
I've spent the better part of a day trying to diagnose exactly what conditions cause this to happen, but it seems fairly inconsistent. Sometimes the corruption happens on the first bin move, other times I can move a few things around without a problem. Once the problem strikes, it seems to affect every bin move after that.
Right now I'm managing the problem by backing up the project before I move a bin, but the cycle of backing up and restoring projects is quite time-consuming, not to mention it doesn't give me confidence that my project is safe.
If anyone can help me track down the reason this is happening so Blackmagic can fix it, I'd be grateful.
When I do this, everything appears to work correctly ... until I leave Resolve. The next time I open the project, the bins show up as "invisible" folders, without names, and the bins are completely empty, with all clips and timelines missing from the project (this can be partially confirmed by looking at the "timeline" count in the project manager — corrupt projects show fewer total timelines). This screenshot shows what that looks like:
- Screenshot of what corruption looks like.
- Screenshot from 2022-08-11 12-08-03.png (82.91 KiB) Viewed 749 times
The only way to recover is to restore from backup.
I've spent the better part of a day trying to diagnose exactly what conditions cause this to happen, but it seems fairly inconsistent. Sometimes the corruption happens on the first bin move, other times I can move a few things around without a problem. Once the problem strikes, it seems to affect every bin move after that.
Right now I'm managing the problem by backing up the project before I move a bin, but the cycle of backing up and restoring projects is quite time-consuming, not to mention it doesn't give me confidence that my project is safe.
If anyone can help me track down the reason this is happening so Blackmagic can fix it, I'd be grateful.
Devon Cooke
The Hands that Feed Us
www.thehandsthatfeedus.ca
Resolve Studio 18.6.4
The Hands that Feed Us
www.thehandsthatfeedus.ca
Resolve Studio 18.6.4