Doesn’t seem to be the exact same result. Scopes shift a little.
Ignoring the 1.4 exposure compensation and the header-hack, I get a match between:
- Resolve (Rec.709/Linear to D-Gamut/D-Log (…to AWG3/LogC3) - via colorspace transform node)
- Resolve (Rec.709/Linear to D-Gamut/D-Log - via DJI’s 1D LUT)
- Baselight (CGI Linear / Rec.709 to AWG3/LogC3)
- Transkoder/OSD (auto debayers to AWG3/LogC3)
- Silverstack Lab (RAW set to "D-Gamut/D-Log)
Now… with the header trick, the actual “debayer to D-Gamut/D-Log” in Resolve is ever so slightly different, dare I say better?.. And no Color temp/Tint tweaking can get the Rec709/Lin to match this method.
What is Blackmagic doing? Did they profile the sensor themselves? How is it that no other software can replicate Resolve’s D-Gamut/D-Log debayer?
I’ve also tried the photo-based softwares (Lightroom, Affinity, RAWTherapee, etc.), and those are the furthest off (having no straightforward way to get a Log image),
I even compiled rawtoaces and that did not get me anywhere near the baseline.
Fascinating. Exhausting.