11/24/2023 0 Comments Lut range for lutcalc![]() ![]() (ACES) You need a monitor which is calibrated to your target deliverable. Logarist LUTs can all access the full range of color values produced by the camera, including values in the 100-109% range, and values below 0% for some cameras too.Įdit: had to check my notes for the behavior of LUTs in Lumetri.Įdit: I just found the LUTCalc bug for setting input scaling in DaVinci Cube LUTs, fixed in v3.1.2. Incidentally, Logarist doesn't have that limitation because it doesn't rely on Lumetri for loading LUTs. So practically speaking with LUTs in Lumetri input values above 100% will be clipped. LUTCalc can create a LUT that will access values above 100%, but Lumetri doesn't properly apply the LUT to values in the 100-109% range. So for Premiere, set LUTCalc's input range to 100%, in which case input values above 100% will be clipped. For Sony cameras and S-Log1/2/3, I believe both Resolve and Premiere decode video in the same correct way. Premiere's decoding largely matches what Resolve does when the clip attributes data levels in Resolve is set to "video", though there are a number of different corner cases that Resolve and Premiere each decode incorrectly. "Unclipped" can produce values below 0% and above 100% that would normally be clipped by your display, but you could manually manipulate the color values to bring some of those within the 0-100% range if you wanted. Hard Clip "Both B&W" creates a broadcast-legal signal with no RGB values outside of 0-100%. It's up to you how you want to set Hard Clip for your output. BT.709), the output range should be set to 100%. If your LUTCalc output is a display color space (e.g. Set LUTCalc's input range to 109% for this case. In Resolve when the clip attributes data levels is set to "full", Resolve places the display-referenced black point (0% R'G'B') of the decoded video at 0.063 (64/1023) in the RGB working space and the display-referenced white point (100% R'G'B') of the decoded video at 0.92 (940/1023) in the RGB working space. Use LUTCalc 3.1.2 or later and set the LUT Type to DaVinci Resolve 12+ auto to ensure that the LUT will be able to access values in the 100-109% range. ![]() Set LUTCalc's input range to 100% for this case. In Resolve when the clip attributes data levels is set to "video", Resolve places the display-referenced black point (0% R'G'B') of the decoded video at 0.0 in the RGB working space, and the display-referenced white point (100% R'G'B') of the decoded video at 1.0 in the RGB working space. So you need different LUTs depending on which camera, format, and video software you're using. It's that they decode video in a few different ways. Can anyone explain that difference?It's not just that Premiere and Resolve handle LUTs differently. Also it seems to be taken for granted that Premiere and Resolve handle LUT's differently. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |