Encoding error with Media Encoder vs PP encoding

[jeffb56004601]

I'm having a strange issue whcih is new on a project. When rendering in PP, everything is fine, when rendering in ME, the gamma and colour of one cameras clips is wrong and also an overlay that is hiding some cropping of the frame is not being rendered. This is a project that I have been working on for a few months and everyhting was fine until the latest update. The error occurs on both Windows 11 (latest) and Mac Sequoia 15.2. Both PP and ME versions are the latest. I would upload frame grabs of the issue, but the forum is not allowing me to upload jpegs for some reason. I've attempted to attach them.

[jeffb56004601]

[Rach McIntire]

Hi  @jeffb56004601,

Thanks for submitting your bug report.  Can you confirm what version of Premiere you are using?  Have you tried rolling back to the previous version and does the issue still persist in the old version?

Sorry for the frustration and thanks for reaching out.

[jeffb56004601]

I am using 25.1.0 build 73. Is there a way to save a 25 project so it opens in 24?

[jeffb56004601]

I used an online tool to downgrade the project and opened it in 24. Sending it ME 24 shows no errors...it's fine. So the issue is with PP 25 and ME 25.

[Rach McIntire]

Was this issue also in 25.0 or just 25.1?

[jeffb56004601]

I have not worked on the project since Oct 22 2024 so if 25 was out at that point, then 25 was fine. If 24 was current at that point,then I'll need to understand how to downgrade 25.1 to 25. Can you let me know how to do that? TIA

[R Neil Haugen]

What color management settings are you using?

And is this the only HDR, probably HLG, clip in that project/sequence?

[jeffb56004601]

No...both clips in the project are HLG3/Rec709 with color space override set to Rec709 for both clips. Timeline playback is fine, exporting in PP is fine, ME is obviously misinterpreting the color space of just one of the cameras clips. A cam was FX30 - that's the one causing issues. B cam was a6700. I was mistaken in thinking one layer was not rendering...what I'm seeing is the frame fix on the left as it should be over top of the overly bright FX30 footage. Make sense? Something is going wonky when the project gets sent over to ME. I'm confused as to why only one camera's clips are affected...is there something about the FX30 footage metadata???

[Rach McIntire]

Hi @jeffb56004601,

Here's a guide on how to choose which version of Premiere you are installing.

A few others have reported issues with 25.1 but found that 25.0 was working better, which is why I ask.  

Are you using adjustment layers?  Also are both cameras the same resolution/ file format?

[jeffb56004601]

Ok...noted. Both cameras are the same resolution, file type, colour and gamma space...HLG3/Rec.709...the offending clip is from an FX30, the other cam's clips are fine and they are from an a6700. Very, very similar Lumetri, etc. adjustments and effects are applied to both. Both have a frame fix overlay (which I've determined is rendering properly...it's just the brightness of the mis-rendered clip that made me think a layer was not being rendered). I can get by exporting within PP...it's just that I often batch export numerous timelines through ME.

[jeffb56004601]

Sorry...no adjustment layers...there are graphic and image layers as well as the ClosedCaption text layer. All colour correction is done on the clips in the bin.

[R Neil Haugen]

HLG3 ... and Rec.709 ... aren't the same. As those are two very different color spaces.

So your respons is puzzling.

[jeffb56004601]

HLG3 is the gamma, Rec. 709 is the color space. In Sony cameras, you can set HLG3/Rec. 709. The other option is HLG3/BT2020 color space which I don't like using as the colors are not as nice as Rec. 709.

[jeffb56004601]

I just tried disablng 'auto tone mapping' in the sequence and the results are the same...one clip is misinterpreted in ME.

[R Neil Haugen]

Do you have both auto detect log and auto tonemapping on? 

[jeffb56004601]

Hi...just checking in to see if there is any resolution to this bug upcoming? TIA

[R Neil Haugen]

You haven't answered the last question. It is important data.

[jeffb56004601]

Thanks but it is not the issue. I'll wait for Adobe to reply or a fix.

[R Neil Haugen]

Auto detect log and auto tonemapping are essentially inter-dependent. That's why I asked. I'm rather experienced in color management both in Premiere and Resolve, for near a decade now.

[jeffb56004601]

Thank you for your input.

[R Neil Haugen]

Of your two images up top, sadly unlabeled, the upper looks to be HDR improperly tone-mapped/normalized to Rec.709, the lower looks to be log-ish not normalized (expanded) to Rec.709.

So all "we" on the forum can know, is that you have an image not being correctly handled by the CM of 25.x, but "we" don't know which way the issue lies. Just that you have one.

Working troubleshooting from incomplete data is always a catch-up game. And as frustrating for 'use' as it is for you.

Which is why giving data always is wise. And helpful. And saves a ton of time.

[jeffb56004601]

Please stop. Thanks.

[R Neil Haugen]

You may not be aware that this is primarily a user to user forum? We get some assistance from staffers, for which we all are grateful. But the standard "help" here is peer assistance.

You may note my stats if you check, I do have rather a lot of help provided to users. And further, others pay me to advise and to train them on this stuff.

Your choice of course. Fix it, or wait. Ain't hurting me any.