Why Applying a LUT Directly to S-Log3 Looks Flat — The CST Node You're Missing

You drop a Rec.709 LUT onto your Sony S-Log3 clip and the image goes milky. The blacks lift, the saturation flattens, the skin looks like it's been through a scanner. The LUT isn't broken — you just skipped the step it assumes you already did.

This trips up almost every working DP the first time they grade Sony log footage. You shoot a wedding on the FX3, bring it into Resolve, slap your favourite Rec.709 LUT on the first node, and the result looks worse than the raw log image. Saturation is anaemic, contrast is mush, the highlights have this weird plastic roll-off. Most people respond by stacking a Curves node and crushing the blacks until it "looks right." That works for one shot. Then you cut to the next angle and everything has shifted again.

The fix is one node. It's been sitting in the OpenFX panel the whole time. It's called Color Space Transform, and once you understand what it actually does, you'll never grade log footage without it again.

What a LUT actually expects

A LUT — a .cube file — is a lookup table. You give it an input pixel value, it gives you an output pixel value. That's the whole machine. It does not know what camera you shot on. It does not know what color space your footage is in. It just maps numbers.

When a colorist builds a "Rec.709 creative LUT" and exports it, they were grading against an image already in Rec.709 gamma and Rec.709 primaries on their monitor. The LUT's input/output table is calibrated to that assumption. So when you feed it a Rec.709-ready image, the math works and the look lands.

Your Sony footage is not that. An .MP4 or .MXF recorded in S-Log3 mode is encoded in S-Log3/S-Gamut3.Cine — a logarithmic gamma curve sitting in a much wider color space than Rec.709. The whole point of S-Log3 is to compress more dynamic range into the available bits, which is why it looks washed out before grading. It's supposed to.

When you put a Rec.709 LUT on top of S-Log3 raw, you're asking a Rec.709 calculator to interpret log data. The LUT remaps numbers it was never calibrated for. Blacks lift because S-Log3 doesn't sit black at code value 64 the way Rec.709 does. Saturation drops because S-Gamut3.Cine's primaries are pulled inward when sampled by a Rec.709 LUT. The result is the milky, anaemic image you're staring at.

The node tree that fixes it

Here's the order of operations in DaVinci Resolve. Build it once, save it as a PowerGrade, drop it on every clip:

Node 1  →  Color Space Transform   (S-Log3/S-Gamut3.Cine  →  Rec.709/Rec.709)
Node 2  →  Creative LUT             (your Rec.709 .cube)
Node 3  →  Trim                     (lift / gamma / gain, contrast, sat)

Node 1 is the conversion step the LUT was assuming. In Resolve, right-click your first node, add an OpenFX, find ResolveFX Color → Color Space Transform. Set Input Color Space: S-Log3, Input Gamma: S-Log3, Output Color Space: Rec.709, Output Gamma: Rec.709. Tone Mapping: DaVinci. Gamut Mapping: Saturation Compression. Apply Forward OOTF: enabled.

That last toggle — Forward OOTF — is the one most tutorials skip. OOTF stands for "opto-optical transfer function." In plain language it's the tonal curve that broadcast standards apply when going from scene-referred light to display-referred light. Without it, your midtones will sit too low; with it, they land where Rec.709 broadcast intended. Turn it on. Always.

Now look at your image. It already looks like a normal video clip — punchy, saturated, broadcast-legal. You haven't even added the LUT yet. That's the giveaway: the CST is doing the work the LUT could never do alone.

Node 2 is the creative LUT. Drag your .cube onto it. Because the input is now genuinely Rec.709, the LUT sees what it was built to see and the look lands clean. Skin tones sit where they belong on the vectorscope. Contrast snaps to the curve the colorist intended.

Node 3 is your trim — per-shot lift/gamma/gain, a touch of saturation, maybe a hue-vs-hue tweak on the bridal red. This is where you adapt the canned look to this specific clip. Never trim inside Node 1 or Node 2. Keep transforms and looks pristine and editable.

Why putting the LUT first breaks everything

You might think: can I just put the LUT on Node 1 and the CST after it to "fix" the result? No. The order is load-bearing.

If the LUT runs first on log data, it has already mangled the values before any conversion happens. By the time the CST sees the image, you're not transforming S-Log3 anymore — you're transforming whatever the LUT made it. The CST's input setting (S-Log3) no longer describes the actual data, and you'll get a double-broken result. Saturation goes nuclear, highlights clip, skin tones drift orange.

The CST has to run on the original log values, untouched, before any creative pass. Think of it as translation: you have to translate the sentence into English before you can edit it for tone.

The same logic in Premiere and FCP

Resolve makes this explicit, but the principle is universal. If you cut in Premiere, Lumetri Color has a Color Space Override under the Master clip's Modify menu — set the input to Rec. 2100 HLG or interpret the footage through Color Settings on the sequence, then apply your LUT on a Lumetri instance below. Better yet, in modern Premiere builds, set the working color space on the sequence to Rec.709 and toggle Tone Mapping on, which performs the equivalent S-Log3 to Rec.709 transform internally before your effects chain runs.

In Final Cut Pro, set the Library color processing to Wide Gamut HDR, the project to Standard - Rec. 709, and apply a Custom LUT effect. FCP handles the input transform automatically based on the clip's tagged color space, which Sony cameras embed correctly — so the LUT lands on already-converted data. If your LUT still looks flat, check the clip's color space tag in the inspector; an incorrectly tagged file is the most common culprit.

Why this matters across the Sony lineup

If you're shooting in India right now, you're probably on one of these: FX3, A7S III, FX30, A7 IV, A7C II, or the older FS5/FS7. Every one of those records S-Log3/S-Gamut3.Cine when set to picture profile PP8 or PP9 (PP10 is HLG, different conversation). The CST workflow is identical across all of them. There is no "FX3 LUT" or "A7S III LUT" — there's a Rec.709 LUT, and there's the CST that gets your camera's log data into Rec.709 so the LUT can do its job.

This is why a single creative LUT pack works across a whole Sony kit. Once the CST is doing the heavy lifting on Node 1, the camera body becomes irrelevant. Your second-shooter's A7 IV and your FX3 will match in the timeline because they both got transformed to the same Rec.709 reference before the look got applied.

One sanity check before you commit

After you've built the three-node stack, throw a Parade scope on the viewer and check three things. First, blacks should sit at or just above 0 IRE on all three channels — if they're floating at 5-10 IRE, the CST didn't run or the OOTF is off. Second, a properly exposed face should land between 50 and 70 IRE on the luma trace. Third, a 100% white surface (a wedding sehra, a chef's coat, a temple wall in noon sun) should hit close to but not clip at 100 IRE.

If any of those are off by more than a stop, the problem is upstream of the LUT — either an exposure issue on set or a CST setting that doesn't match what the camera actually recorded. Don't fight it with the trim node. Go back, fix the transform, then re-evaluate.

This single node is the difference between "my LUTs never look like the YouTube tutorial" and "my LUTs always work." It's not the LUT's fault. It's not the camera's fault. It's a missing translation step that the entire color pipeline assumes you'll add. Add it once, save the node tree, and your S-Log3 grade becomes a one-click operation for the rest of your career.

If you want a head start — including the PowerGrade, the matching CST presets, and creative looks built specifically for Indian skin and venue lighting — have a look at the Positiva LUT packs. Or browse the full set of tools we use on every wedding and travel project.