LUT or nodes: color grading in DaVinci Resolve
The table brings the picture in fast and in the same way on every shot, the nodes give control and stay in the project. We look at the formats, the purpose and the order of operations that sometimes makes a table get in the way.
LUT or nodes: color grading in DaVinci Resolve is not a matter of taste but of the task: the table works fast and the same way on every shot, while nodes give control and stay in the project. One does not replace the other. We look at what a LUT actually is, how a technical table differs from a creative one, why the table is tied to a color space and what to choose for a single clip.
What a LUT is
A LUT is a file, not a tool. Blackmagic describes such files simply: they look like plugins, but are much narrower and have no user interface, and they set the operations of image processing. The classic way is a 1D table or a 3D “cube” of pre-computed values that perform the color transformation. In the newer CLF and DCTL formats a mathematical script can lie inside.
In Resolve such files are read and written in the .cube format: 3D LUTs are exported as 17x17x17, 33x33x33 or 65x65x65 cubes, and the processing runs in 32-bit floating point. A separate technique is the shaper LUT: it is a 1D and a 3D LUT together, made specifically for signals with data outside the range, which a 3D LUT clips.
The size of the cube is worth saying separately. Blackmagic does not recommend 17-point LUTs for grading — they are useful to carry to the set, for different displays, for calibration and for signal conversion. For working with the picture, cubes of a larger size are taken.
Technical and creative LUT
Tables have two different purposes, and it is useful to tell them apart. The technical table is responsible for normalisation. Blackmagic gives as an example material shot in a logarithmic encoding: DPX log scans, ARRI ALEXA Log-C, Sony S-Log or RED R3D, debayered with REDFilmLog. Log video keeps a lot of data, but the picture is flat and is not fit without a grade: exposure and color are brought to a normalised view, and the table does that faster than by hand.
The creative table is a look, the stylistic component of a grade, which gives a quick start for the edit. It is exactly from such sets that the ecosystem of ready “looks” has grown, which are put in one folder and dragged from project to project.
The third purpose is the set. Every take of a scene is shot with the corresponding LUT, and it sets the baseline, how the scene should look. Cameras do the same: the Blackmagic Pocket Cinema Camera shows the LUT on the LCD and on the HDMI output, up to 10 LUTs of 17 or 33 points up to 1.5 megabytes each fit on the camera, and the applied table is written into the file as metadata — Resolve shows it in the “LUT used” field. An important detail: by default the camera does not bake the LUT into the material, but such an option can be turned on.
A LUT and the color space
The main thing to understand about a table is this: it does not convert the picture from one space to another by itself. A LUT is a transformation calculated for a specific input space. Applied to another source, it will not give the result the author intended, and overexposure or a grey cast will look like a grading mistake.
From here come two rules. The first: the technical table goes before any meaningful corrections, because it calculates the picture in the space it was made for. The second: if color management is switched on in the project, the same task is solved by Color Space Transform — it calculates the transformation with the same mathematics as the color management and does not require matching a table to each space.
With ACES it is subtler still. An ordinary LUT does not work there: it has to be preceded by a conversion to the space it was made for, and after that the picture has to be brought back into ACES. Blackmagic warns that such a workaround does not always give an ideal result. For ACES there are its own formats: CLF is an XML structure that holds both tables and mathematical transformations, and the Academy recommends exactly it for LMT; DCTL is a color transformation file, that is, a script that Resolve applies as an ordinary table, and it calculates by itself, with combinations of mathematical functions.
One clip in two ways
It is convenient to compare the two ways by criteria and not by taste.
The key difference is in the order of operations inside the node. LUTs added to a node perform their transformation as the last operation in that node, after all the other Color corrections that the node applies. The practical meaning: the color and contrast of the same node can trim the data before it enters the table. If the table cuts the highlights too hard, the details can be brought back with the Contrast control before it.
There is one more place where the choice is obvious. A LUT set for a source clip cannot be copied from timeline to timeline through ColorTrace — so for most processes it is better to apply the table directly in the node editor, so that it lives in the grade of each clip. The LUT group of settings in the Color Management panel of the project settings, on the contrary, applies the table to the whole timeline at once.
The other side is export. A grade can be exported into a table, but not everything is transferred: into a LUT the nodes with Primaries, Custom Curves and compatible ResolveFX corrections are mathematically reduced, including Color Space Transform, ACES Transform and Gamut Mapping, while the nodes with qualifiers, windows and incompatible filters are ignored completely. The export formats are Generate 3D LUT: 17 Point Cube, 33 Point Cube, 65 Point Cube and Panasonic VLUT. If the project has a skin selection or masks, they do not get into the table, and the grade has to be assembled by hand.
Frequently asked questions
Can you combine a LUT and nodes?
You can, but in a strict order. Inside a node the LUT runs as the last operation, after all the Color corrections — and that is not a restriction but an opportunity: the color and contrast of the same node trim the data before the table. The working scheme is a normalising table in the first node, and the meaningful corrections in the next ones. What is not worth doing: putting the table in the middle of the chain, where the picture has not been normalised yet — then the table will convert the wrong space.
Do you need a LUT after CST?
No. Color Space Transform and a LUT solve the same task, but CST calculates the transformation with the same mathematics as the color management of Resolve, and does not match values by a table. Putting a LUT after CST means converting the picture twice. The exception is ACES: there an ordinary LUT requires a conversion to the space it was made for and back into ACES, and Blackmagic warns that such a workaround does not always give an ideal result. For ACES the right way is a table made for ACES: CLF or DCTL.
What to read next
Need this done as a project?
We take on projects like this — with the same settings we walk through in this piece.