bug: temperature in hdr tool

when i change the temperature slider on a node at clip-level ever so slightly (both warmer or colder), for a subtle adjustment, it looks like the tint also changes a tiny little bit towards magenta. not the actual tint value, which stays at zero, but it's visible in the image. it's very subtle, but needs to be corrected by changing the actual tint a little. The footage for what i just tested is Slog, and has a conversion to 709 with a CST on post-group level.

this happened for me the last few versions, and the current (18.6) if i'm working with the HDR tools, with the timeline color space set to DWG/intermediate, output to rec709 2.2 and 2.4, color science davinci YRGB.

Hi, did you ever find a solution to this? I'm having the same issue. It's driving me mad. I'm using a mini panel. Whenever I touch either the temp or tint in HDR there's an immediate jump towards magenta. You can see the shift on the scopes, but it doesn't show anything on the tint control itself.

If you're actually trying to change color temp, I think a better way to do it is with the OFX Chromatic Adaptation plug-in, which actually has readouts for color temp in degrees Kelvin. Much more precise way to do it.

when i change the temperature slider on a node at clip-level ever so slightly (both warmer or colder), for a subtle adjustment, it looks like the tint also changes a tiny little bit towards magenta. not the actual tint value, which stays at zero, but it's visible in the image. it's very subtle, but needs to be corrected by changing the actual tint a little. The footage for what i just tested is Slog, and has a conversion to 709 with a CST on post-group level.

this happened for me the last few versions, and the current (18.6) if i'm working with the HDR tools, with the timeline color space set to DWG/intermediate, output to rec709 2.2 and 2.4, color science davinci YRGB.

How the tuneline color space is setup?

Hi - hopefully this demonstrates what I mean -

Just touching the Temp wheel, and pushing it in either the magenta or green direction pushes the image markedly in the magenta direction - you can see the jump on the scope. So even if you push to green, it initially jumps to magenta. Any ideas?

NOTE - Timeline colour space is Davinci YRGB Rec 709 Gamma 2.2.

This does seem to only be an issue with Temp and Tint in the HDR panel when using a control panel:

This video shows what happens when I touch the Tint wheel - no matter which way I push it, it initially pushes the image to magenta:



In the video I then adjust the Tint wheel using the mouse and there is no jump, it behaves normally.

Is this a bug with the control panel working with the HDR? As I understand it, it's only since Resolve 19 that the Temp and Tint in the HDR panel actually affect the HDR controls?

NOTE - this only happens when using Temp and Tint in the HDR panel using a control panel. It does not happen using Temp and Tint in the Primaries Panel.

I'm seeing this as well in Studio 19.1.1 for Windows.

Are you working with color management or you manage your color manually?

I tested with RCM.

Rick... if you are not color space managed, the timeline color space setting (Davinci intermediate) will be used for the math in that HDR tools, and that is not coherent with the shot you are trying to color (you stated Slog)

while a bug could be present, you should (in the HDR tool) correctly declare the color space a Slog.

I tested this with both footage shot in just 709 and no colour management, and footage shot in Clog3 colour managed to transform to Davinci WG with a CST and back to 709. The same thing happens in all cases - whether using colour management or not - as soon as I just touch either HDR TEMP or HDR TINT on my mini panel there is a big shift to magenta (as shown in my videos above)

I tested this with both footage shot in just 709 and no colour management, and footage shot in Clog3 colour managed to transform to Davinci WG with a CST and back to 709. The same thing happens in all cases - whether using colour management or not - as soon as I just touch either HDR TEMP or HDR TINT on my mini panel there is a big shift to magenta (as shown in my videos above)

Can you test it by disabling the mini panel and use the mouse? It looks like a legit bug…

OK, I've unplugged the control panel, and just tried adjusting TEMP and TINT using the mouse, and actually it has the same issue.

So this issue with HDR TEMP and HDR TINT does seem to happen whether using a control panel or not.

I am using Windows 11 - Resolve 19.1

If you're actually trying to change color temp, I think a better way to do it is with the OFX Chromatic Adaptation plug-in, which actually has readouts for color temp in degrees Kelvin. Much more precise way to do it.

+1

Compared to the HDR global control, Chromatic Adapation uses a different calculation that is generally closer to the result when the temp/tint is adjusted in camera (or in the Raw tab control). If making small changes to temp/tint, the difference isn't so stark and may not matter. But for making big shifts in temp/tint to balance out a camera operator error or wonky lighting, in those cases I nearly always get the best result from Chromatic Adaptation.

Same problem here on MacOS Sonoma 14.7.2, Davinci Resolve Studio 19.1.1

It only happens in HDR panel using Temp and/or Tint, with or without mini panel.
Minimum adjustment and all colors are shifted towards magenta, magenta seems to be the only color untouched.
Have tested in managed and non managed workflows, and different timelines color spaces. It always happen, no matter what is selected, even in Aces workflow.

Image below from non managed workflow with DWGI timeline color space

hdr temp tint.png (818.59 KiB) Viewed 4659 times

it happens in rec709 timeline color space too, but not so obvious as in bigger color spaces.

So it looks like a bug

I'm grateful to others who are posting to say they're seeing the same as me. I'm not sure how to properly report this to Blackmagic - I did go to the support site and sent an email a few days ago, but not had a reply to that. Is there a better way to report bugs so they get looked at with some urgency?

I'm not sure how to properly report this to Blackmagic

This thread.

confirmed on W10 19.1.1, no color management, as soon as you touch it there is a bump.

Just tested it with the latest update "DaVinci Resolve Studio 19.1.2" and the problem is still there.

The OP said this same bug had been happening in version 18.6. Given it's still happening, do you think there's any chance it will ever be fixed? It's pretty major as far as I'm concerned, when grading using the hdr panel, clips keep getting pushed to magenta and I keep having to correct for it, sometimes I miss that it's happened and have to fix and re export. I have emailed blackmagic but no reply. Wonder if their support won't see this thread as its based on a very old bug report. Should I post this in a new thread to get their attention on this? I wonder if the bug went away after 18.6 and has come back?

Should I post this in a new thread to get their attention on this?

I don't thin that's necessary. Better to keep things consolidated.

They read the forums. They just don't respond to every report.

I've recently moved to DWG/Intermediate Timeline colour space as a test and am also observing this.

Seems totally bonkers that this is a even a thing... I think the right thing to do is still to fix it, as it just makes no sense to have the 'bump' ...

That definitely looks like a bug.

This bug is still present in 19.1.3.

I'm very surprised that this hasn't been fixed as a priority.

It will be affecting anyone who uses the temp and tint features in HDR, which must be so many people.

Blackmagic support did get back to me about a month ago and said they were also seeing the bug and were going to escalate it, but I haven't heard anymore.

Just as an update to anyone reading this, I had an email to confirm Blackmagic have replicated the problem and it should be fixed on a future update.

Thanks for reporting!

Unbelievably, this still hasn't been fixed despite it having been 4 months and Blackmagic acknowledging the problem. It's been 4 months since Blackmagic said they were aware of the issue, and since then a whole new version of Resolve has been released and gone through all the beta testing and the issue hasn't been fixed.

I can't understand why there isn't more urgency since this issue effectively makes the temp and tint controls in HDR unusable.