Custom ACES IDT for Resolve
Note that DCTL scripts require the studio version of Resolve.
I was just involved in a discussion on creating IDTs for color grading in ACES cct in Resolve 14 when there is no built-in IDT. Or if the existing IDT isn't ideal.
Here's the process that I worked out:
When there is no IDT specified in the project and the clip, then Resolve expects the data to be in linear gamma and AP0 gamut. An input LUT can be applied before Resolve translates the clip to ACES cct color space. Thus a LUT that can translate the camera data into linear / AP0 is a proper replacement for an IDT.
This can easily be achieved in LUTCalc (https://cameramanben.github.io/LUTCalc/). To test this theory I took a clip and set the default Slog3/S-Gamut3.Cine IDT and took a screen grab for reference. I then created a custom LUT with these settings in LUTCalc. I set the clip's IDT to None and added the new LUT as the input LUT for the clip.
As seen below, the resulting image matches the reference images from the original IDT, suggesting that the two operations are equivalent.
This now opens the opportunity to make additional customizations to this input LUT to taste, or create a LUT that matches the camera specifics of unqiue cameras.
Based on this article, the other option is to create a DCTL script: http://acescentral.com/t/adding-idts-to-resolve/161/2. A DCTL script has the advantage that it's precise math rather than interpolated lookup table. The code in a DCTL script matches the math precision the built-in IDT use.
Using the Sony SLog-3 IDT and converting it to a DCTL file, which then is placed into the LUT folder and used instead of IDT or Input LUT also creates an equivalent image. In fact it creates an exact match when using a reference wipe, whereas the input LUT yields minor variations, presumably based on the less precise math or LUTCalc having slightly different input values.
Note that DCTL scripts require the studio version of Resolve.
// SLog3 / S-Gamut3 DCTL for ACES IDT replacement
__CONSTANT__ float color_xform[9] =
{
0.6387886672f, 0.2723514337f, 0.0888598991f,
-0.0039159060f, 1.0880732309f, -0.0841573249f,
-0.0299072021f, -0.0264325799f, 1.0563397820f
};
__DEVICE__ float slog3_to_linear(float v) {
float result;
if(v >= 171.2102946929f / 1023.0f)
{
result = _powf(10.0f,(v*1023.0f-420.0f)/261.5f)*(0.18f+0.01f)-0.01f;
}
else
{
result = (v*1023.0f-95.0f)*0.01125000f/(171.2102946929f-95.0f);
}
return result;
}
__DEVICE__ float3 transform(int p_Width, int p_Height, int p_X, int p_Y, float p_R, float p_G, float p_B)
{
// Convert from SLog3 to Linear
float3 linear;
linear.x = slog3_to_linear(p_R);
linear.y = slog3_to_linear(p_G);
linear.z = slog3_to_linear(p_B);
// Convert from S-Gamut3 to AP0
float3 aces;
aces.x = color_xform[0]*linear.x + color_xform[1]*linear.y + color_xform[2]*linear.z;
aces.y = color_xform[3]*linear.x + color_xform[4]*linear.y + color_xform[5]*linear.z;
aces.z = color_xform[6]*linear.x + color_xform[7]*linear.y + color_xform[8]*linear.z;
return aces;
}
Here is the same frame with all three different methods: the built-in IDT, the input LUT, and the DCTL script.
