Skip to main content
BUS74
Known Participant
January 14, 2022
Question

Problem with ProRes 422 HQ codec

  • January 14, 2022
  • 5 replies
  • 7203 views

Good morning.
I have a ZCAM E2 F6 with Atomos Ninja V and I use Premiere PRO rel. 22.1.2 for editing and color grading.

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. This is most noticeable in controlled light recording, but it also happens in landscape shots, especially in the sky.
The same clip developed on Apple Final Cut with the same Lut is perfect!
The same recording in H.265 codec in Zcam camera is perfect on both Premiere Pro and Final Cut.

I am attaching 3 screenshots of a frame with the three versions where the halos are clearly visible. Obviously processed with Premiere Pro rel 22.1.2

The problem also occurs in the older version of Premiere Pro.

I use a Macbook Pro 16 "with macos 12.1 64gb ram and AMD Radeon Pro 5500M 8 GB

Has anyone ever had a problem like this?
Is there a particular way to parameterize Premiere Pro?

Thanks for your suggestions!

 

clauio

Italy

This topic has been closed for replies.

5 replies

R Neil Haugen
Brainiac
January 18, 2022

The camera recorded file seems quite clean to me. The Ninja file has the little gaps in the Parade and Waveform scopes which the camera footage does not. The fine horizontal dark lines running across the scopes. That typically is missing data at that 'level'.

 

This camera file is not really what I'd call "log".  The black point is lifted to about 20, the highlights dropped to what, 90? And the saturation is low.

 

So it was simple to 'normalize' For the shadow/black, I went to the Color Wheels, and pulled the Luma slider of the Shadow wheel set down until black point was around 4 or 5 on the nits scale on the left side of the scopes.

 

Then pulled the image up very slightly ... with the Exposure control. Didn't need much just a tiny amount, so to 0.1 on the Exposure settings. Takes the white point just above 90 on the left-side nits scale.

 

And I went to the Creative tab and lifted Vibrance to 39. That's it.

 

Neil

chrisw44157881
Inspiring
January 19, 2022

Neil

 

Transcode the original H.265 to Prores 422 HQ and then the Prores 422 HQ you just transcoded again to Prores 444XQ.

Why does the RGB parade get better from the same 422 source when becoming 444HQ? That doesn't make any sense.

R Neil Haugen
Brainiac
January 21, 2022

Hi crisw44157881

Maybe I understood what you tried to explain to me and I did the tests you suggested.
In fact I have to confirm that it works !!


Basically I try to summarize and sorry but undoubtedly I'm a beginner !! I am also attaching screenshots where I recall the letters next to the red arrows:

 

1) I develop the ProRes HQ clip recorded on the Ninja V on Premiere Pro by applying Lut, various corrections.


2) when I run the clip on Premiere PRO I see the famous "banding"


3) if I export it with CMD-M on MAC in H.264 or H.265 the "banding" remains and it shows !!!


4) if I export with CMD-M on MAC in ProRes 422 or ProRes 422 HQ or ProRes 4444XQ with the parameters you see in the screenshot under items A-B-C the final result is perfect!

 

So if I understood correctly Preiemre PRO, when viewing an H.265 clip with all the settings, it shows it well and if you always export it in H.265 or H.264 it is perfect.


If, on the other hand, the original clip is a ProRes HQ Premiere Pro does not display it correctly by inserting the "banding". Then when I export it to ProRes (here I noticed whether it is 422 or 422 HQ or 4444XQ) the file produced by viewing it with Quiktime palyer is perfect.

 

Do you think the explanation is the correct one?

 

If so, does Premiere PRO in editing and color grading with an original clip in ProRes HQ have a bug in displaying the clip in the main monitor?

Do you think this is a correct statement?

 

Thanks for the support you are super!


How about going to the sequence settings for the original Zcam & Ninja ProRes clips, and set the Max Bit Depth and Max Render Q switches to on?

 

I think that would do it. Make sure of the same thing in exports.

 

Neil

R Neil Haugen
Brainiac
January 17, 2022

Here's some more images of the scopes signal. This is the Nikon recorded image, frame 1, no LUT:

Here's the Ninja recorded frame 1, again no LUT:

And here's the Nikon with the z-Log LUT:

 And the Ninja with the z-log LUT:

 Here's the Ninja, Waveform RGB, no LUT:

 And the Ninja, Waveform RGB, z-log LUT:

I've got a few comments. First, the media recorded internally is on my system higher quality than that recorded on the Ninja. Look at the smoothness of scopes on the original Nikon versus the Ninja, both without the LUT.

 

Next, that LUT is stressing the media to, and really, past the breaking point. First, talking about the color changes it makes. Look at the Vectorscope changes, between no LUT and LUT applied, both on the camera recorded clip and the Ninja recorded clip. That LUT is pushing some data out actually slightly past the out-of-bounds lines of the Vectorscope. This is an extreme lifting of color data.

 

And here's the same image, again, first frame of the Nikon camera clip, lowering of the Shadows Luma control of the Color Wheels tab to bring Black down to about 4-5 nits, and slight boost to the Exposure control of the Basic tab,  just 0.1 up. With Creative tab's Vibrance control to 39. No banding. Image goes from 4 nits to 96 nits, with good "normal" color.

From this, I've got a concern with both the Ninja recording and with that LUT. No problem with the original media.

 

Neil

 

 

 

 

BUS74
BUS74Author
Known Participant
January 18, 2022

Thanks to everyone tonight I will read your considerations better even if it is not easy for me to translate from English.

 

Neil when you talk about Nikon you obviously mean ZCAM. am I right?

 

The streaks you see on ProRes HQ compared to H.265 I have noticed too and it seems to me that the H.265 file is cleaner!

However, I read carefully and look at the images and if anything I do other tests also in controlled light.

 

Neil if you please also take a screenshot of the settings you have set in Lumetri so I can get an idea.


Thank you

R Neil Haugen
Brainiac
January 17, 2022

Ok, just got them into Premiere. This is the original Nikon recorded file. And the signal trace in the scopes is not something I'm used to seeing.

That solid line at the bottom is just odd to me. I've not seen that sort of thing before. Plus there's a big divide between where most of the "upper" data would be, I'm assuming the sky, and the bright spots of the buildings on the left. The sky is pretty compressed, but the lights of the buildings are quite a ways above them.

 

I'll spend a bit more time with all of the clips in a while.

 

Neil

chrisw44157881
Inspiring
January 17, 2022

I got a pretty ouchie conclusion and honestly, I can't believe my eyes. I took the h.265, and encoded it to Prores HQ with shutter encoder. I then did a basic curves adjustment and saturation increase and got really bad banding in the sky. I took the Prores HQ I just transcoded and trancoded it again to h.264, copied the lumetri effect with the settings over and the sky was perfect. Semi-good news, Prores 444XQ works ok. The only conclusion I can draw is that there are many codecs that have premiere bugs. Since the banding is there before the lut, the lut would simply exacerbate the bug.

 

additional note: I forced Prores 444HQ back to 16-235 and got some banding back, so there may be a corralation of video levels. also h.264 which looked perfect, did have a 10% boost in gamma.

 

but I think there's enough here that a color engineer needs to sit down and take a look.

R Neil Haugen
Brainiac
January 14, 2022

 That is 'banding' technically, caused by the application of the LUT.

 

Are you applying the LUT in the Basic tab slot of PrPro? If so, try applying it from the Creative tab slot instead, then go into the Basic tab and adjust the White and Highlight controls a titch, see if you can get rid of it.

 

Colorist's call LUTs the dumbest math out there. Nearly all LUTs can and will clip and cause banding and artifacts unless the user has the ability to apply some 'trim' to the exposure, contrast, and saturation before the LUT while viewing the image with the LUT.

 

Hence my suggestions.

 

Neil

BUS74
BUS74Author
Known Participant
January 15, 2022

Thanks Neil for your support.

I tried to follow your advice but the situation does not change !!


The strange thing is that the ProRes 422 HQ clip without LUT as it was recorded has artifacts while in Final Cut it is perfect.
I tried to upload the same clip to Davicni Resolve and it behaves like Premiere PRO !!
The H.265 codec is perfect on both Premiere Pro, Final Cut and Davinci.


So it seems that already when the clip, without any LUT no color grading, no retouching of the parameters of the basic tab, is displayed by Premiere Pro it reports the problem. Putting the Lut highlights it more.

 

Tonight I try to make some screenshots to attach with some notes so as to explain myself better.

 

For now thanks again Neil.

 

claudio

R Neil Haugen
Brainiac
January 15, 2022

Will be interested to see the images.

 

Neil