![]() ![]() If that clip has 'stretched' data, that doesn't show as an issue with a low-gamma presentation, but does with proper gamma. So that is why you need to trim the clip prior to applying the LUT. No field-produced media will ever come in with exactly the same exposure/saturation/contrast data of the LUT creation. that LUT was "built" in a studio setup using perfectly set up lighting/contrast/camera controls. ![]() So it's easy to apply a LUT, then trim the clip properly to fit the LUT. 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. You would try to use the Basic tab controls to get rid of the banding. 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. 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. LUTs are the dumbest math out there, and they will do things exactly like this unless the user takes control of them. it isn't that the data issue isn't there, it's likely that the lower gamma means you won't see the issue. I am guessing, but I think that is why you are not getting the banding appearing in FCP. in the questionable area.įCP is applying a lower gamma to the file, an incorrect gamma for Rec.709/SDR standards. That both Resolve and Premiere show banding with that LUT immediately puts the LUT in use. Resolve even better (as it's a full blown grading app) than Premiere. It would be testing the file header/structure via another processing chain.Īnd both Premiere and Resolve are built for heavy pro work, and treat LUTs pretty decently. But especially, if NOT played from the Ninja. Other than that it can process the specifics of the data it recorded.Īndy's comment about the TV is actually valid here. That the Ninja, which recorded the file, can show it proves nothing. Is there a particular way to parameterize Premiere Pro? I use a Macbook Pro 16 "with macos 12.1 64gb ram and AMD Radeon Pro 5500M 8 GB The problem also occurs in the older version of Premiere Pro. Obviously processed with Premiere Pro rel 22.1.2 I am attaching 3 screenshots of a frame with the three versions where the halos are clearly visible. The same recording in H.265 codec in Zcam camera is perfect on both Premiere Pro and Final Cut. The same clip developed on Apple Final Cut with the same Lut is perfect! This is most noticeable in controlled light recording, but it also happens in landscape shots, especially in the sky. I noticed that by recording in ProRes 422 HQ both on the ninja V and directly in the Zcam camera and then applying the Lut Zcam zlog2_ax2_normal, but also by manually intervening in the color grading, halos are created. ![]() I have a ZCAM E2 F6 with Atomos Ninja V and I use Premiere PRO rel. ![]()
0 Comments
Leave a Reply. |