Some grades not saved on Resolve 16.2.7

I'm having a major issue on Resolve 16.2.7 (Windows), with some of my grades not being saved. This issue crept up on me a few weeks ago. After closing my project and reopening it, I realized that some of my work was gone. At first I thought I might have screwed up, so I redid the work. But lo and behold, after closing and reopening the project, the work was gone again. Only some clips are affected. Any operations on those clips on the color page will not be saved. Every other operation is saved even if performed after the stuff that does not get saved. I can reliably replicate the problem so it is not user error:

1) give a nasty magenta bias to clip#1
2) same to clip#2
3) same to clip#3
4) do some stuff on the edit page.
5) save, close project and reopen

Everything is as expected except clip#2, which does not have the magenta bias. It's not that the grade on the clip got completely reset, just the stuff that I did in that session.

- I'm using ACEScct
- local grades
- my clips are organized it groups but the issue occurs that the clip level
- the problematic clips are drone shots (H.265, the rest of the media is Prores or XF AVC)

I tried everything I could think of (rebooting, exporting and reimporting project, removing all peripherals, etc.). Then I moved the problematic clips to a new group, which did nothing to help me. Then I put them in a new group again, and the problem just disappeared. No idea why that worked.

Two weeks later, I'm on a new episode (same series) and it's happening again. I'm in a different suite, on a different PC, but the database from the other one has been restored here (it's a local disk database). This time, some of my drone shots (H.265) and some archive shots (H.264) are affected, but not all of them. The other thing is that all affected clips are a different resolution from the timeline (which is HD), but I can't see why that would matter. I tried generating optimized media for the problem clips, but it did not help...

Any ideas?

I've put the project here in case it might help:
https://www.dropbox.com/s/tg19m42kwrc3u ... 2.drp?dl=0

The problematic clips are in the "Drones" and "Archives" group. Clips with a cyan flag are problematic, clips with a green flag are ok.

=======
OS Name Microsoft Windows 10 Pro
Version 10.0.18363 Build 18363
Processor Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz, 3000 Mhz, 18 Core(s), 36 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 2002, 2019-10-03
BaseBoard Product WS X299 SAGE/10G
Installed Physical Memory (RAM) 128 GB

GPU: Dual NVIDIA GeForce RTX 2080 Ti (Driver 456.71)

Mini panel in one suite, advanced panel in the other.

I'm guessing you can't duplicate this on a simple test project?

But if you can, then post that here and others can test it.

I just had a play in V17, doing what you described, but it always saved fine for me, which is what I expected. If the problem was that fundamental lots of people would be complaining.

This sounds like a similar problem, but no solution:

https://www.dropbox.com/s/tg19m42kwrc3u ... 2.drp?dl=0


This one is on Linux (I'm on Windows):

viewtopic.php?f=21&t=108144

User Sulo Kokki says:

We encountered similar behaviour with DR14 on Linux (CentOS & others). Case-in-point, when Resolve was used specifically with the US keyboard, things were good. But, if you used anything else, your grades were only good for that session.

What happened if you had, like, English (UK) keyboard layout was - apparently - that the decimal pointer went awry (from . to , or vice versa). This caused the project file to be saved / exported in the wrong format. In other words, bye-bye grades. Better luck next time.

Another user states that he's had the same issue when using a French keyboard layout. That's interesting because I am also using an non-US English keyboard layout (Canadian French), though I switch to US English layout within Resolve.

I'm guessing you can't duplicate this on a simple test project?

But if you can, then post that here and others can test it.

I just had a play in V17, doing what you described, but it always saved fine for me, which is what I expected. If the problem was that fundamental lots of people would be complaining.

I haven't seen this issue before, so I understand that it must not be common. I just tried a new project with some of those clips, but it's working fine.

Initially I suspected something was corrupted in my project. That could explain why some grades were not saved properly, if that part of the project in the database was corrupted. But the fact that it just happened on another brand-new project worries me.

I just loaded your project and saw that only the last grade showed the offset.

I made a similar offset in the first node on the second to last clip, saved the file and quit Resolve. Restarted and the save had worked. This is in 17.1, which is what I have on the laptop I'm on at the moment.

That's going to make it difficult to track down.

I just loaded your project and saw that only the last grade showed the offset.

I made a similar offset in the first node on the second to last clip, saved the file and quit Resolve. Restarted and the save had worked. This is in 17.1, which is what I have on the laptop I'm on at the moment.

That's going to make it difficult to track down.

Thanks for trying. I also tried the project at home and it seems to work. I've re-exported the DRP from my home PC and will try that in the suite next time I am scheduled.

Thanks for trying. I also tried the project at home and it seems to work. I've re-exported the DRP from my home PC and will try that in the suite next time I am scheduled.

I just imported the project exported from home into the color suite at the facility and the problem has vanished for now. Hopefully it’s the last time I encounter this bug.

EDIT:
Nope, it was only fixed for a moment. And I learned that another colorist encountered the same bug in the same suite.

FWIW the 16.3 betas are no longer listed on the support page, so I guess if you have any more problems then you'll have to look to 17 for a fix.

FWIW the 16.3 betas are no longer listed on the support page, so I guess if you have any more problems then you'll have to look to 17 for a fix.

That was a typo, I am not on a beta version. The correct version is 16.2.7.008.

Nope, it was only fixed for a moment. And I learned that another colorist encountered the same bug in the same suite.

New attempt at a fix:
Starting with the assumption that the problem lies with the instance of the media pool clip in the database, I imported another version of one of the problem clips, re-conformed it in the timeline (which retained all settings including the previous grade). The bug remains: so I conclude that the bug is related to the instance of the clip in the timeline, not to the instance in the media pool.

Then I did a match frame of the problem clip and overwrote it in the timeline. This should create a new instance of the clip in the timeline, unrelated to the previous buggy one. That seems to have fixed it for now. I repeated the operation for all of the buggy clips and tested whether new grading operations are saved. It seems to work.

Glad you found a fix. I’ve never experienced it.

As a rule, before closing a project, I always create and time/date a stills bin and then choose “Grab all stills from first frame “, Save, and export the .drp to the cloud. (Save Stills with project is also checked under preferences) This way if anything happens, dead drive, lightning strike, asteroid, I’m covered. Just a suggestion.


HPz840 - 2x 14 Core 2.6GHz - 64GB RAM
Windows 10 Pro 20H2
2x RTX 2080Ti (SD 460.89)
Resolve Studio 16.2.7
Decklink 4K Extreme (11.6)
FSI CM250
Panasonic FZ1000
Mini Panel

As a rule, before closing a project, I always create and time/date a stills bin and then choose “Grab all stills from first frame “, Save, and export the .drp to the cloud. (Save Stills with project is also checked under preferences) This way if anything happens, dead drive, lightning strike, asteroid, I’m covered. Just a suggestion.

Good tip. I always export a DRP (multiple times a day in fact). But I don't systematically save all stills. I should do this from now on.