I played with the ColorCheckMacbeth gizmo in Nuke. It generates the color matrix. If you take this matrix and plug it into a ColorMatrix matchbox, the calibration translates. If you have a pipeline where you’re already doing this for Nuke, you can replicate those values in Flame. Maybe even write a python script that can auto-generate an importable node in Flame.
Be mindful that the gamut in the Nuke gizmo and Flame has to match. I set my project up with ACES 1.2 and had a color mgmt node with input transform to ACEScg in the batch,.
So you’re half-way there on your original request. You have the backend, for the front end it’s either already in your pipeline, you can use an external tool you have access to, or over time we can write some OpenCV python scripts to generate that matrix.
Or twist ADSK’s arm to build it into Flame to start with.
Thanks for the detailed reply, and yes, I do neutralise all plates and HDRIs using the macbeth charts I gather on set. If I can’t get one, things get a bit messy but our approach is pretty much on rails once the footage gets inside Nuke.
In terms of colorists balancing things and producing a technical grade, visually may work very well and client may be happy but given our bread and butter is CGI, that is not a solution I can buy into… the CGI won’t sit on the plate and we will end up fudging it in comp which is very time consuming.
I had a go at this years and years ago, as a Pybox node which I’m not sure anyone ever used because it’s pretty slow and clunky… you can see a demo here on two different colour chart layouts: https://www.youtube.com/watch?v=df2yIh3nx_4
It exports the matrix as a .ctf you can load in ColorMgmt although a tiny Matchbox would also work. To keep the python side simpler it relies on aligning the charts beforehand with an action bilinear… unfortunately like the mmColorTarget gizmo for Nuke it requires a few dependencies which can be annoying to install, and I tried to wrap them up inside the script itself in what seems like a really stupid way in retrospect - but anyone is very welcome to take the script itself and re-package it as something you can run from the logik portal or a right-click menu: https://raw.githubusercontent.com/lcrs/pyboxes/master/Ls_LUTy.py
@leovfx Not sure what the logic of the Color Corrector is. This matchbox only works on basic white balance of black and white point.
Here’s the math behind it:
result = vec3( (source - s_blackPoint) / s_whitePoint);
result = vec3( (result * t_whitePoint) + t_blackPoint);
Whereas the various Macbeth plugins/tools run a much more complex algorithm to match the two images. Though they still only derive a global 3x3 matrix, not a match that might take highlights and shadows into consideration, such as LUT could.
Can the results be pretty similar in most circumstances? Probably. But you were looking for something more precise.