Samsung Log LUTs DaVinci Resolve, DaVinci YRGB Color Managed

Have I missed something here?

While Resolve now has a couple of transform LUT options for the Samsung LOG gamma format. If I work in a "DaVinci YRGB Color Managed" "Color Managed" project, Resolve does not auto-transform Samsung LOG to my timeline and output processing and colour space settings. Is this correct?

I think Resolve only auto recognizes RAW input. The log inputs have to be set manually. At least that is what I do for my Panasonic Vlog and I know that is true for Sony too so do not see why that would be different for Samsung. I use colour managed with wide gamut intermediate and set colour space in media page for my Panasonic files.

I think Resolve only auto recognizes RAW input. The log inputs have to be set manually. At least that is what I do for my Panasonic Vlog and I know that is true for Sony too so do not see why that would be different for Samsung. I use colour managed with wide gamut intermediate and set colour space in media page for my Panasonic files.

Alright, Ron. Hope you are well buddy.

Resolve will actually auto-transform LOG as well in a colour managed project/workspace as long as it recognises the format, just as it does RAW.

Because BMD made a point of this latest update supporting Samsung LOG with some built-in transform LUTs, I'd assumed that Resolve would also auto-transform the Samsung LOG gamma in a colour managed workspace. It seems a little odd to add the transform/decode function but not via the colour managed workspace.

How is Edius doing?

Cheers,
Dave.

Hi Dave. Still breathing !! Don't use EDIUS much these days just when I need interlace stuff from the past. Resolve does not auto recognize log files from either my GH5S or GH6. It identifies both as rec709. I have to select in media page to get the colour space correction. True on both my PC and the Mac.

Because BMD made a point of this latest update supporting Samsung LOG with some built-in transform LUTs, I'd assumed that Resolve would also auto-transform the Samsung LOG gamma in a colour managed workspace.

You're assuming wrong. Most log formats are not recognized automatically by RCM. The ones that are, are the exceptions.

Resolve automatically recognises Nikon log (N-Log) and Apple Log files in a Resolve Color Managed (RCM) project. The N-Log files don't have to be raw. If they are N-Raw, the Input Color Space is not accessible. For non-raw log files, the Input Color Space can be seen by right clicking a clip in the Color Page timeline.

AFAIK they only added actual LUT files to the base LUT folder that comes with a Resolve installation. One to linearize the samsung log curve and one log to Rec.709 'video' connversion. There hasn't been any form of implementation of the log encoding into the CST/RCM system yet but maybe it comes in a future update.

AFAIK they only added actual LUT files to the base LUT folder that comes with a Resolve installation. One to linearize the samsung log curve and one log to Rec.709 'video' connversion. There hasn't been any form of implementation of the log encoding into the CST/RCM system yet but maybe it comes in a future update.

Yes, maybe it comes in the future. I can't see why not as I doubt Resolve will have any issues identifying the native media and its tags/meta data.

Resolve automatically recognises Nikon log (N-Log) and Apple Log files in a Resolve Color Managed (RCM) project. The N-Log files don't have to be raw. If they are N-Raw, the Input Color Space is not accessible. For non-raw log files, the Input Color Space can be seen by right clicking a clip in the Color Page timeline.

Resolve recognizes Raw formats that use log. If it's in a MP4 or such, it won't understand it.

The release notes say "Support for Samsung Log LUTs."

That reads to me like BM simply added Samsung luts into the luts folder. Not that they added Samsung log to the CST tool (like they have done with Apple log).

Can anyone on the newest version confirm?


The automatic color management tool has never used the luts, it has always been doing CSTs under the hood. So if BM is only doing LUTs for samsung, then the automatic tool can't be of use.


Is the Samsung log just something added in the s25? I don't think I have it in my S24. I am using MotionCam to get log in my s24.

Resolve automatically recognises Nikon log (N-Log) and Apple Log files in a Resolve Color Managed (RCM) project. The N-Log files don't have to be raw. If they are N-Raw, the Input Color Space is not accessible. For non-raw log files, the Input Color Space can be seen by right clicking a clip in the Color Page timeline.

Resolve recognizes Raw formats that use log. If it's in a MP4 or such, it won't understand it.

And yet NLog HEVC works

Resolve automatically recognises Nikon log (N-Log) and Apple Log files in a Resolve Color Managed (RCM) project. The N-Log files don't have to be raw. If they are N-Raw, the Input Color Space is not accessible. For non-raw log files, the Input Color Space can be seen by right clicking a clip in the Color Page timeline.

Resolve recognizes Raw formats that use log. If it's in a MP4 or such, it won't understand it.

And yet NLog HEVC works

Yes. I rechecked all this before I posted. There is no argument. I made sure I was on firm ground.

To reiterate, Resolve automatically recognises ProRes and H.265 (HEVC) N-Log formats from Nikon cameras in an RCM workflow. There is no log option on these cameras for H.264 so that is moot. These are not raw formats. It does of course recognise N-RAW N-Log as well.

It's the same for my iPhone 16 Pro. Apple Log in HEVC and ProRes are automatically recognised by Resolve in an RCM workflow. These are the only formats with which you can shoot log.