Skip to main content
December 9, 2025
Answered

Premiere Pro treats my S-Log3 footage as Rec.709. What am I doing wrong?

  • December 9, 2025
  • 2 replies
  • 258 views

 

 

 

Hi! I’m shooting on a Sony a7IV in S-Log3 / S-Gamut3.Cine, but Premiere Pro keeps interpreting my footage as Rec.709 by default. I’m using the latest version of Pr.

 

I tried disabling everything I could:

• Tone Mapping: OFF

• Color Space Override: Rec.709 (default)

• When I switch the Color Space Override to S-Log3 / S-Gamut3.Cine, the image becomes insanely oversaturated and completely unusable.

 

I feel like Premiere is applying some kind of transform under the hood, but I can’t figure out how to get the actual flat S-Log3 image so I can grade it properly (or send it to DaVinci Resolve without a baked-in transform).

 

What makes this even more confusing is that Premiere handles my Osmo Pocket 3 D-Log footage perfectly — no weird transforms, no oversaturation, everything looks exactly as expected.

 

Any help would be really appreciated, I’m completely stuck on this.

Correct answer R Neil Haugen

Are you working in the Lumetri panel's Settings tab ... where the entire looooong chain of options is available?

 

If so, look up and down the list. You probably don't want auto=detect log on, especially in companion with a Rec.709 sequence, as it will do a full algorithmic transform to Rec.709.

 

Also, input tonemapping on the Sequence setting options should be off for you.

 

Their algorithmic transforms were designed in tandem with the camera makers, and are a good replacement for the rather more simplistic ... and problematic ... LUT transforms.

 

LUTs are just a basic look-up table ... they have like 32 o4 64 entries of 'this RGB triplicate changes to this RGB triplicate" ... and in-between, the app just applies a normally pretty straight line transform. No shaping or anything.

 

And LUTs are called the dumbest math out there by colorists for that reason. And they will crush and clip data if the field produced media does not quite closely match the exposure/contrast/saturation of the media used to create the LUT to begin with. 

 

I work for/with/teach pro colorists, and they tend to all go for algo-based transforms when they can. Safer for your pixels, is how several describe them. A slightly different starting place than any particular LUT you may have been using, but then, most makers have a wide selection of provided LUTs for each camera anyway. They are also only a starting point, like the algos.

 

Now ... to do a full pass through, without any changes, hit the "preserve RGB" option up top. At that point, if you have log-encoded media, and say do a ProRes output, that will be the same log-encoded data.

 

And ... if and when using their rather spiffy new CM setup, one thing you may have hit is to not have sequence input tonemapping on if you want to work in the wide gamut ACESScct working space and do your own normalization.

2 replies

R Neil Haugen
R Neil HaugenCorrect answer
Legend
December 10, 2025

Are you working in the Lumetri panel's Settings tab ... where the entire looooong chain of options is available?

 

If so, look up and down the list. You probably don't want auto=detect log on, especially in companion with a Rec.709 sequence, as it will do a full algorithmic transform to Rec.709.

 

Also, input tonemapping on the Sequence setting options should be off for you.

 

Their algorithmic transforms were designed in tandem with the camera makers, and are a good replacement for the rather more simplistic ... and problematic ... LUT transforms.

 

LUTs are just a basic look-up table ... they have like 32 o4 64 entries of 'this RGB triplicate changes to this RGB triplicate" ... and in-between, the app just applies a normally pretty straight line transform. No shaping or anything.

 

And LUTs are called the dumbest math out there by colorists for that reason. And they will crush and clip data if the field produced media does not quite closely match the exposure/contrast/saturation of the media used to create the LUT to begin with. 

 

I work for/with/teach pro colorists, and they tend to all go for algo-based transforms when they can. Safer for your pixels, is how several describe them. A slightly different starting place than any particular LUT you may have been using, but then, most makers have a wide selection of provided LUTs for each camera anyway. They are also only a starting point, like the algos.

 

Now ... to do a full pass through, without any changes, hit the "preserve RGB" option up top. At that point, if you have log-encoded media, and say do a ProRes output, that will be the same log-encoded data.

 

And ... if and when using their rather spiffy new CM setup, one thing you may have hit is to not have sequence input tonemapping on if you want to work in the wide gamut ACESScct working space and do your own normalization.

Everyone's mileage always varies ...
December 10, 2025

Thanks so much for your reply!

Just to make sure I understand correctly — are you suggesting that I should simply leave the footage interpreted as Rec.709 and do my color grading from there?

R Neil Haugen
Legend
December 10, 2025

I do. And note, I'm running a full Tangent Elements panel and have enough experience and muscle memory to normalize most log manually faster than most can find an apply a LUT.

 

But the algorithms get the clip within working space instantly and technically absolutely clean. Why not start there?

 

I do use the wide gamut workflow, specifically the ACEScct working space in Lumetri, normally with the Rec.709 sequence space. And as noted, the input tonemapping is turned off on the sequence so the wider gamut data is preserved.

 

Up top I have auto detect log and auto tonemapping on. That way it tonemaps to the specific working space, for me ACEScct.

Everyone's mileage always varies ...
Kevin J. Monahan Jr.
Legend
December 10, 2025

Hi,

Thanks for posting your question. Sounds frustrating. I'm sure a community member will be along shortly to assist you with your workflow. @R Neil Haugen, do you have any ideas? Sorry for the frustration.

 

Thanks,

Kevin

 

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio