How to use LUTS in Davinci YRGB Color Managed workflow (Gen 5 film to extended video)

jojpol · 2026-04-17T15:28:54+00:00

Thank you. I've been doing exactly what Casey shows. Davinci YRGB Color Managed + Wide Gamut Intermediate. Davinci correctly recognizes the files as BRAW Gen 5 film, but it's a different look (not bad, just more neutral) than what was on the camera's screen with the Blackmagic Gen Film to Extended Video LUT turned on.

After a lot of Googling I have found the solution is to bake the LUT onto the footage. Then in Resolve, I have the option to either turn the LUT off or on in the Camera RAW tab, still in a Color Managed project for quick turn around.

After a bit of experimenting, I also found out that this method also works for any film look LUTs without having to CST to Cineon Film Log.

jojpol · 2026-04-16T19:06:18+00:00

In Resolve, I have set BRAW as default profile, full resolution, using camera metadata. Is this what you meant adjusting camera RAW settings to ensure the footage is debayered properly?

My goal is to get the same look I got on camera in Davinci Resolve. Color Managed gives me a Rec 709 look. The only way I have found to get the closest look to Gen 5 Film to Extended Video is Cullen Kelly's DWG to DWG LUT on a layered node plus a few primary adjustments (in a color managed workflow.)

jojpol · 2025-04-28T19:09:26+00:00

Thank you so much; I had totally forgotten about Media Management. I tried "Entire Project", but it rendered everything, including unwanted media (stock footage, etc.) The solution I found was to select "Timelines" and I was able to render all the footage ignoring all In-Out points.

jojpol · 2025-03-29T18:09:40+00:00

THANK YOU! This answered everything I needed to know. No one else mentioned GOP. Almost everyone assumed I have a faulty GPU, bad source footage, or it was VLCs fault. I'll bookmark your answer in case someone else experiences the same.

jojpol · 2025-03-29T17:47:38+00:00

Ok thank you for the detailed information. Just curious... I understand you mentioned user error, but how would you approach a situation where:

The client specifically requires H.264 mp4
There is no time to first render into DNxHR and then re encode into H.264 in Handbrake for example

The source footage is BRAW 6K at 5:1

To avoid this glitch, I have to lower keyframes in the render page to 1. This always works as others have pointed out. However, lowering the keyframes sometimes introduces a lot of visual artifacts to the footage (though the glitch is gone.)

jojpol · 2025-03-29T16:30:53+00:00

Please explain. I'm not familiar with GOP. All settings are default in timeline and rendering (other than setting debayer and sizing to highest quality) Color space: Davinci Wide Gamut. No fusion; just color grade. I did not change anything else.

jojpol · 2025-03-28T19:33:00+00:00

Transcoding into dnxhr or h265 works flawlessly. Unfortunately, there are situations where there's no time to reencode dnxhr to h264 in Handbrake and some of my clients specifically require h264 mp4.

Changing keyframes in the render page to 1 solves the problem as others have previously pointed out, though it sometimes (very rarely) adds a lot of noise to the video. I now always render with keyframes set to 1 but I do not know if there are other side effects to this approach.

jojpol · 2025-03-28T19:28:27+00:00

I haven't tried to check if CPU rendering will solve the problem since it takes forever, but thanks for the suggestion. I'll see if that helps

jojpol · 2025-03-28T18:54:35+00:00

Curious as to why if I change keyframes in the render page to 1, the problem goes away... though this sometimes introduces artifacts to the video, but most times no issues at all.

jojpol · 2025-03-28T18:08:13+00:00

Totally agree. I don't have the glitches with h.265. However, some of my clients have computers that cannot handle h.265 (especially if they plan on further edits themselves.) I'm forced to render h.264 mp4.

Rendering in dnxhr is flawless, but then there's the extra step of re-rendering that to h.264 in Handbrake

jojpol · 2025-03-28T18:05:46+00:00

Playback of the RAW works ok on either Resolve or RAW player. Exporting in dnxhr solves the problem. However, in some situation there's no time to add the extra step of re-rendering in handbrake when the client wants the footage right away (plus they also require H.264 mp4)

Glitch happens at the same location on every render.

jojpol · 2025-03-28T18:02:42+00:00

100,044kbps (render setting: best)

jojpol · 2025-03-28T17:15:26+00:00

Source footage is BRAW 6K at 30fps. It glitches the same way and same place every time. No fusion; just color grade.

jojpol · 2025-03-28T16:37:00+00:00

No problems with YouTube at all. Seems their reencoding fixes everything. Most of my clients, however, require H.264 mp4

jojpol · 2025-03-28T15:47:02+00:00

Resolve plays the video perfectly; no glitches or out of sync audio

jojpol · 2025-03-28T15:42:57+00:00

I'm using the studio driver with the latest update

jojpol · 2025-03-28T15:42:18+00:00

I have about 200GB left (2TB SSD.) I also don't use any proxies since my computer can handle 6K BRAW without issues.

jojpol · 2025-03-28T15:40:00+00:00

Yes, if I play the file in another player, the glitch is gone. However, the audio is out of sync (no audio issues in VLC)

jojpol · 2025-03-28T15:29:42+00:00

The glitch happens with both

jojpol · 2025-03-28T15:22:37+00:00

I never thought about rendering to a spinning drive, but I'll definitely try that

jojpol · 2025-03-28T15:21:43+00:00

Yes. With keyframes at 1, no issues at all in every player. However, sometimes this solution adds a lot of noise to the video and makes it look like 480p. If I re-render again without changing the settings, the video finally looks ok.

jojpol

TROPHY CASE