• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

More Color problems.

Contributor ,
May 19, 2023 May 19, 2023

Copy link to clipboard

Copied

What is going ON with Media encoder changing things!? 

Previously, it screwed up only Specific letters from a mogrt. Now, it's messing up just a Few clips.

This time it's not involving AE at all. And I Think I might have an idea of where the issue is coming from. 

Premiere has ben automatically enabling the "Auto Tone Map Media" checkbox between versions. 

Honestly, I don't even know what it does other than screw things up. I tried it when it first came out, and it Seemed like it automatically added the correct LUT, only I think maybe it was doing it as an input lut rather than a creative LUT, even though Premiere's documentation Specifically says NOT to do that because Lumetri works top down, so that means you adjust your colors Before adjusting basic corrections and if the input lut causes something to be under/over exposed, you can't get that information back. 

 

So, what's a bug? I have no clue, other than I think it's related to that because I have check the preference off multiple times, and it mysteriously turns itself back on. 

Most of the footage, even from the same camera, is fine within the same video. There are probably a few slight shifts, but 2 of the videos became Very washed out. 

I rendered the exact same sequence directly from Premiere and it rendered just like my timeline.

Checking the clips > Interpret Footage > Color management > Input LUT = None. -- Use Media Color Space from File: Rec. 709

Which is what all of the other footage, except for the RED footage, is set to. 

 

When I tried out the tone map setting previously, I had the same issue without realizing what had happened, so I decided whatever that setting was doing wasn't a great idea, and turned it off. 

It seems like it turns itself on after some of the updates, but again, unsure exactly. I thought there was a setting in the preferences at one point, but now it's only in the sequence options? 

I'd actually use it if it just automatically added the correct LUT to Lumetri, if a Lumetri effect didn't already exist, but that doesn't seem to be how it works. It just changes the colors Fairly close to what they should be after the LUT is applied...without telling you which one it chose, or at what point it's doing it? And when I tried it originally, I created a nested sequence, things were fine. I opened premiere, and it applied the auto-tone map twice to every clip I had nested, without providing a way to turn it off (that I could find).

 

Regardless of my frustration with why we would get half-baked releases from the Adobe dev team; this is one project, renders fine from Premiere, and Some of the clips have color issues when rendering with Media Encoder, while others from the same camera on the same shoot do Not have any issue if I render from premiere. I even closed premiere and opened it, then rendered again for good measure Just in case I had made an error that was only showing up when opened again for some reason, but it rendered fine.

 

I mentioned mogrts because I had the same issue there. They work and render fine within premiere, but when I sent the render to AME, within text that was set to change to all caps, only a few specific letters ignored that. 

 

Bug Unresolved
TOPICS
Preference and Settings , Stability , User experience or interface

Views

154

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
3 Comments
Adobe Employee ,
May 24, 2023 May 24, 2023

Copy link to clipboard

Copied

We are not clear which preference you are changing. Seems like auto detect log checkbox state is changed due to which you are seeing the difference in colors. Using 709 colorspace in IF which should not  be impacted by tone map. 


Which build and which OS are you using?


Votes

Translate

Translate

Report

Report
Adobe Employee ,
May 24, 2023 May 24, 2023

Copy link to clipboard

Copied

Thank you for reaching out to us . We try to solve your problem.

Could you please tell us what is the current version of Premiere Pro and which was the old version from where you updated it?
Also we want to know which preference setting you are changing and to which state?

 

If washed out media is the Log Media then you can try by disabling the preference setting Auto Detect Log Video Color Space.

 

Tone Mapping setting is available for sequence only. Its not under preferences.

 

 You can turn off the auto tone map by unchecking the check box  Auto Tone Map Media under sequence settings.

 

Votes

Translate

Translate

Report

Report
Contributor ,
May 25, 2023 May 25, 2023

Copy link to clipboard

Copied

LATEST

I assumed it was related to the tone mapping. 

I have the "Auto Detect Log Video Color Space" in preference turned off.

After updating one of the more recent versions (I have auto update turned on, so don't know which version from/to it was related) the sequences got the "Auto Tone Map Media" button checked. I had turned that off on some C-Log footage, and it is now turned back on again.

I wanted to not use any of it because it was causing some terrible errors when media was nested. I think that bug is fixed, now, but it doesn't really save me much time and since it still seems like you folks are trying to figure it out I'd rather not have it. 

 

Regardless of what the cause is, there's a bug somewhere because premiere renders the file as I see it. Sending it to AME renders Some of the clips with incorrect color. 

 

This is windows 11 Pro 10.0.22621 Build 2261

Premiere pro v23.4.0 build 56

Media Encoder  v23.4 build 47

Votes

Translate

Translate

Report

Report