Video clipping issue with various codecs
I have run into what seems like a very disturbing bug in Premiere Pro. Currently running 13.1.2 on an iMac with OS 10.14.1 and Blackmagic IO card.
I have a 1920x1080 23.976p sequence with Maximum Bit Depth and Maximum Render Quality selected.
I have camera original clips of various codecs. The problem occurs when a camera original clip has levels above 100ire.
When I put a .mp4 based clip with over 100 levels in the sequence the levels are preserved.
When I put a .mov file containing an XDCam 35 codec with over 100 levels in the sequence, the levels are clipped at 100 ire. If I look at the clip in the source window the levels are preserved. I can force Premiere to reveal those over 100 levels by merely applying the Lumetri effect to the clip in the sequence (no adjustments to that effect need be made).
When I put a ProRes 422 .mov file with over 100 levels in the sequence, the levels are clipped at 100 ire. If I look at the clip in the source window the levels are preserved. In this case nothing can be done to retrieve the levels above 100. If I place a Lumetri effect on it, there is no change. If I reduce the levels in Lumetri with any of the tools, the overall level is scaled down, but the overs are not retrieved. Putting a Lumetri effect on the clip as a Master Effect also does not help.
Exporting samples of these clips as ProRes 422 HQ and then inspecting in DaVinci Resolve confirms that what I see in Premiere is in fact burned into the new media.
Using either OpenCl, Metal or Software rendering makes no change.
I have upgraded another similar system to the latest Premiere Pro version - 13.1.5. The only difference I see there is that when I am viewing the ProRes clip, if I press play, the clipping goes away. When I press stop, the clipping returns. But when exported, again, the clipping is burned in.
Jefry Huey commented
I have just tested this issue on Premiere Pro 2020 on Mac with OS 10.14.6. The issue is still present.
I have also spoken with other users who tell me they do NOT see this on Windows systems.
I can provide sample material if that would be helpful.
Jef Huey commented
I would like to add that I just had time to test this with previous versions of Premiere. The problem with ProRes does not appear when using either 2017 or 2018. I have not checked the other mentioned codecs.
I also had another user check this on a PC system and they could not replicate it.
So it seems to be isolated to Mac OS and CC2019.