Video becomes overexposed and washed out when applying LUT

Forum|Forum|1 year ago
June 25, 2024
3 replies
2296 views

I've had this issue from time to time over the last few years and I have yet to find a solution when it happens. I'm currently editing a video in 2024 Premiere Pro and when I apply a LUT under the Creative section in Lumetri Color, the image becomes very washed out and overexposed, even if the LUT intensity is at 0%. I don't believe it has anything to do with the LUT itself, but something about any LUT being applied whatsoever. I have tried to counter this washed-out look by adjusting other parameters in Lumetri Color, but it only begins to create a weird color-blocking look. (video attached below)

Premiere_pro_washed_out_LUT_issue.zip

Color

T

TTentertainment23

Participating Frequently

Got the same issue, when a LUT is applied to an adjustment layer, footage gets way overexposed, when I add the same LUT to the clip itself it works just fine. Weird bug

R Neil Haugen

Legend

As I teach pro colorists, I've done a lot of testing and pushing of PrPro's color stuff over the last decade, and I've never actually had this happen. I'd love to test that LUT myself, if you could pass it on? If we can replicate that, it's useful to inform the devs ...

Everyone's mileage always varies ...

R Neil Haugen

Legend

You haven't told us what the clip was, is it log or standard Rec.709 or what? Or what color space the clip was, the color space of the sequence, or what color management settings you're using.

We need all of that to understand what's going on.

For basics ... iPhone clips are typically HLG these days, and many other cams can be set to that also. Plus Premiere can recognize iPhone and some log media and use them easily. So in general, having auto detect log, and auto tonemapping set to on, working in a Rec.709 seqeunce, and using Rec.709 export presets is a more reliable workflow.

Premiere then manages everything into Rec.709 with a tone-mapping algorithm for you.

Everyone's mileage always varies ...

nickpensa1Author

Participant

My apologies. The clip was shot on a Sony a6300 in SLog2. Premiere reads it as Rec.709 even with auto detect log turned on, but I applied a color space override to both SLog2 and SLog3 and faced the same issues. I have also tried leaving it as Rec.709, but no luck there. Both the main and multicam sequences are set to a Rec.709 working color space with auto tonemapping turned on.