12/17/2023 0 Comments Editready proresThat both Resolve and Premiere show banding with that LUT immediately puts the LUT in use. in the questionable area.įCP is applying a lower gamma to the file, an incorrect gamma for Rec.709/SDR standards. I am guessing, but I think that is why you are not getting the banding appearing in FCP. it isn't that the data issue isn't there, it's likely that the lower gamma means you won't see the issue. LUTs are the dumbest math out there, and they will do things exactly like this unless the user takes control of them. That is why one is SUPPOSED to use a tech or 'corrective' LUT like this one, where you can "trim" the file data by corrections to the image applied before the LUT. In Premiere, that means applying the LUT in the Creative tab's slot, then using the Basic tab tonal/saturation controls to change contrast/white/saturation/exposure to avoid the problems caused by the LUT being mis-matched to the clip. You would try to use the Basic tab controls to get rid of the banding. In Resolve, if you apply a LUT in a node, any corrections of the 'normal' controls of that node are processed before that LUT is. So it's easy to apply a LUT, then trim the clip properly to fit the LUT. that LUT was "built" in a studio setup using perfectly set up lighting/contrast/camera controls. No field-produced media will ever come in with exactly the same exposure/saturation/contrast data of the LUT creation. So that is why you need to trim the clip prior to applying the LUT. If that clip has 'stretched' data, that doesn't show as an issue with a low-gamma presentation, but does with proper gamma.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |