We are editing a big project. One morning we come in and the files from our fx9, s-log 3 look like they have a baked in LUT, even though we have turned off lumetri. This was fine before. The source files are good and desaturated, but when we put it in the timeline, it puts on a slight LUT.
I will attach photos of the source file look, the saturated (unwanted) look and what happens when we put the usual LUT on it.
Thank you! This helped. Why is this happening and do I have to force interprate all files from now on?
They completely rebuilt the underlying color system of Pr2022. Previous versions were built as Rec.709, and a couple versions back they added "the ability to work with HLG/PQ dynamic and color range values as over-range Rec.709..." ... a cadged together way to get some HDR capabilities in.
The 2022 version is color space agnostic, can work with anything the user wants. So it's a completly new system with different default behaviors and new user controls. Unfortuately the new controls are spread out around the app, and the changed default behaviors are puzzling to people.
First, understand ... all HDR is log-encoded, which most people of course don't know. But some media expected to be in SDR/Rec.709 is also shot log-encoded. Premiere is confusing the two from the media from certain Sony and Panny cameras at this time. It's an acknowledged bug, as is the total broking proxy creation process for HLG clips. We're all waiting for the fix.
So ... anything shot in HLG color space, and brought into a Rec.709 timeline must be transformed to Rec.709. And any time that Premiere mistakes a log-encoded Rec.709 clip as HLG, you need to ... again ... transform to Rec.709.
This is done currently in the Project panel bins, right-click/Modify/Interpret Footage, down to the color management options at the bottom. Use the Override to Rec.709 option.
There are times that Pr says a clip is Rec.709 but displays it as if it is HLG. And won't allow an override. That ... is a total pain.
I'm including links to two FAQs. The first covers the changes, how to work in the new system, and what's currently broken.
The second covers how to monitor in HDR if that is your wish, as monitoring HDR also dramatically changed this version.
Thank you for your detailed answer!
I hope this will be fixed as soon as possible!
So do many of us. The changes were needed, yes ... but as implemented, not very clear to SO many users, and with a number of totally broken parts also. Yea, we need the fix along with the rest of the new system tools. The partial implementation wasn't a great idea, methinks ...