Most of the pro colorists I work with are going away from LUT based transforms anywhere possible. Algorithmic transforms are available in Resolve, and some in PrPro 24.x. The public beta for 25.x has added a ton of media into the list with prepared alogrithmic transforms. And algorithmic processes are normally considered a better, safer transfer of image data.
As any transform process is a mix of technical things, along with the many necessary options set because of aesthetic choices, using a "manufacturer" LUT just means you get their aesthetic ideas, instead of someone else's. Which, as a starting point, are normally equally as valid.
Note that say Sony has several varieties of log-to-lin LUTs available for user choice? For the same media?
And past that, in my experience most editors do not apply log-to-lin or other transform LUTs in a manner that would be acceptable to colorists. As most colorists apply a LUT (when used) ... and then trim the clip with actions applied before the LUT so that the clip gets the data for exposure, contrast, and saturation, that it was built for.
Such is the resultant processing order in Resolve if you apply a LUT in a node, then do color correction work in the same node ... the LUT is processed last in that node.
Yet most editors will do something like apply a log-to-lin transform LUT in the Lumetri Basic tab's Input slot, doing all work on the clip after that LUT transform is processed. Which can easily result in clipped or crushed pixels, or out-of-whack sat channels.
If using that Basic tab Input slot, users should apply a Lumetri or Contrast effect prior to the Lumetri instance with the LUT, do basic clip adjustments to make sure all data is 'in bounds', then go into later color work past the LUT.
Or ... what I teach for PrPro workflows ... apply your transform LUT in the Creative tab's Look slot, and use the Basic tab's exposure/shadows/highiight/whites and sat controls to 'trim' the clip properly.
Or ... more sensibly, skip the LUT entirely if Premiere has an algorithmic transform for your media. Which the 24.x version does for iPhone log, btw. And 25.x has a ton more media algrorithmic transforms available.
9
Replies
AdChoices