Why Monsoon Greens in Kerala Look Radioactive on Sony Cameras

Kerala in monsoon looks unreal on location — and it will look genuinely radioactive on your Sony footage if you don't catch the saturation problem before it compounds through your grade. Here's why it happens and exactly how to fix it.

The Problem Isn't Your LUT — It's the Gamut

You've shot a morning in Munnar. Tea estates rolling fog, rain-slicked roads, backwater channels framed by banana leaves the size of ironing boards. On the monitor it looked controlled. Back at the desk, after your Color Space Transform from S-Log3/S-Gamut3.Cine to DaVinci Wide Gamut / DaVinci Intermediate, you drop a travel LUT and the greens go full nuclear. The foliage isn't green anymore — it's emitting light.

This isn't user error. It's a geometry problem inside S-Gamut3.Cine itself. Sony's wide-gamut color space has a green primary that sits noticeably further out than Rec.709, and specifically further toward the yellow-green axis than the DCI-P3 primary. Kerala's monsoon foliage — predominantly Ficus, rubber tree, banana, rice paddy, and tea — is optically clustered right in that zone. When the CST remaps those values, it brings them into the working color space still carrying enormous saturation energy that was latent in the original encoding.

Compare this with footage from a Canon R5 C in Cinema Gamut/Canon Log 3, or a Blackmagic Pocket 6K in BMPCC Film. Neither of those cameras encodes green with the same primary position. Canon Log 3 is more conservative in the green-yellow axis; BMPCC Film clips that region earlier. Sony's cameras — the FX3, A7S III, FX30, ZV-E1 — all share the same underlying color science, so they all share the same vulnerability to this specific environment.

Reading the Problem on Scopes

Before you reach for a node, read what you're actually dealing with. On a vectorscope, correctly graded Rec.709 footage should have your greenery sitting roughly halfway between the Mg and Yl targets, pointing toward G. Kerala monsoon footage on Sony, after a straight CST, will typically push past 75% of the vectorscope radius — sometimes nearly touching the boundary — in the green-yellow quadrant. That's the excess you're correcting.

On the parade (RGB), your green channel will be elevated relative to red and blue in any shot containing foliage. But watch for the separation: if green is 30–35 IRE above red in a midtone foliage shot, that's the specific signature. In normal temperate-climate green, that spread is closer to 15–20 IRE.

The hue angle matters too. Pull up an HSL Qualifier and sample the worst leaves. You'll often find the hue sitting between 90° and 130° — that yellow-green band is precisely where S-Gamut3.Cine has the most primary expansion relative to Rec.709.

The Node Tree That Solves It

This is the chain for DaVinci Resolve. Adapt equivalently in Baselight or Flame.

1. Node 1 — CST In: S-Log3/S-Gamut3.Cine → DaVinci Wide Gamut / DaVinci Intermediate. Tone mapping: None. This is a pure gamut-log transform — don't let Resolve "help" you by applying any automatic tone mapping here.
2. Node 2 — Green Hue Rotation: Open Hue vs Hue in the Curves panel. Find the green band (roughly 90°–150°). Rotate it approximately +8° to +12° toward cyan (pulling the hue away from yellow-green). This is subtle — you're not making the leaves teal, you're taking the yellow edge off them so they read as a natural green rather than a lime spike. Start at +8° and check the vectorscope; stop when the cluster drops below 65% radius.
3. Node 3 — HSL Qualifier + Sat Reduction: Use an HSL Qualifier to isolate the 90°–140° hue range. Set Hue to center around 115°, width ~50°, softness 30%. In the Hue vs Sat curve, pull that same green-yellow band down by about 15–22%. Don't apply a global saturation reduction — you'll flatten your sky and skin simultaneously. The qualifier keeps the reduction surgical.
4. Node 4 — Creative LUT: Drop your travel LUT here. By the time signal reaches this node, the green channel is behaving, and the LUT does what it's designed to do instead of amplifying a problem it was never tested against.
5. Node 5 — CST Out (optional): DaVinci Wide Gamut / DaVinci Intermediate → Rec.709 Gamma 2.4 if you're delivering broadcast-spec. Skip if you're exporting to a working space for a client who will do their own output transform.

A note on Node 3 softness: if you're shooting in locations where the green foliage is directly adjacent to subjects wearing green or gold-green fabric — a common issue in Kerala wedding shoots or saree-clad subjects in paddy fields — increase softness to 40% and verify your qualifier isn't bleeding into costume. Toggle the qualifier highlight mode and walk through the scene cut by cut before rendering.

What You Lose If You Don't Do This

Some colorists default to bringing global saturation down across the board until the greens behave. The result is technically correct but visually dead. Kerala in monsoon is one of the most lushly saturated environments on earth — the sky behind overcast clouds has its own quality of diffuse grey-green bounce light, the rivers are almost black-green, the mist softens but doesn't desaturate. Flattening everything equally loses the very quality that made the location worth shooting.

The qualifier approach preserves that differentiation. Your overcast sky stays cool and moody. Skin tones in the frame — if you've got a subject — stay warm and present. Only the chromatic problem zone is corrected. That's the standard you should be holding yourself to.

Camera-Specific Notes: FX3 vs A7S III vs FX30

All three cameras share S-Gamut3.Cine, but there are differences in how they respond to this correction.

FX3 and A7S III

The FX3 and A7S III in XAVC S-I at 4:2:2 10-bit give you enough chroma resolution that the HSL qualifier edges cleanly. The transition zone between a saturated leaf and a pale sky holds. You can run softness at 25–30% and trust it.

FX30

The FX30's XAVC S 4:2:0 8-bit recording introduces chroma subsampling that makes qualifier edges rougher. If you're correcting FX30 footage from a Kerala shoot, push qualifier softness up to 40–45% to avoid the stepping artifact at leaf edges. Consider also adding a slight blur radius (0.3–0.5 px) on the matte output inside the qualifier settings. It costs you some precision but eliminates the stair-step fringing that will otherwise appear in areas of fine foliage detail against bright sky.

This is also an argument for recording in XAVC HS 4:2:2 10-bit on the FX30 when you know you're going to a high-saturation outdoor environment. The camera can do it. If you're shooting Kerala and you have the card space, use it.

The Munnar-to-Alleppey Grade Shift

A logistical note for travel DPs working a full Kerala itinerary: Munnar at altitude shoots very differently from the backwaters of Alleppey. In Munnar, the green problem is concentrated in the tea estate rows and the forest edge — highly saturated, but relatively uniform in hue. Your qualifier will lock in quickly.

In Alleppey, particularly on the houseboat channels, you're dealing with water-reflected sky mixed with overhanging coconut palm and water hyacinth. The green hue here is more varied — some leaves will read at 95°, others at 140°, and the water itself picks up a greenish cast from the canopy. A single qualifier node won't cover it cleanly. In this case, build a second HSL Qualifier node targeting the 140°–165° band (the darker, cooler palm greens) and apply a separate — and lighter — saturation pull there, around 8–12%. The two nodes in parallel (serial in the node tree, stacked) handle the full range without overcorrecting either.

If you're grading a piece that moves between both environments, use a LUT that was built against this kind of chroma variance rather than one calibrated to a single environment type. The Hue vs Sat nodes you built as corrections will have less work to do if the LUT's baseline expectation is already close to what Kerala footage actually looks like.

One Final Scope Check

Before you export, open the CIE chromaticity scope in Resolve (or the equivalent in your NLE) and look at the distribution of your green values. After correction, they should sit comfortably inside the Rec.709 triangle if that's your delivery target — not just below the boundary, but with genuine headroom. If you still see a cluster pushing toward the boundary edge, go back to Node 3 and pull the HSL sat curve an additional 5%. Better to have a hair of headroom than to deliver a grade that will clip on a reference monitor at the client's end.

The goal isn't to make Kerala look like it was shot in a studio. The goal is to make it look like what it is — one of the most visually overwhelming environments you can point a camera at — rendered faithfully on a system that wasn't designed with monsoon-season tea estates in mind. Fix the saturation geometry. Let the place do the rest.

For how the same Sony color science creates a different, but related, problem at the other end of the color wheel — specifically in late-afternoon golden hour on Indian coastlines — see the breakdown on magenta sunset handling in Goa. And if you're running a mixed-camera setup between an FX3 and a secondary shooter on FX30, the skin tone matching workflow in the FX30 vs FX3 node post applies directly here — same camera family, same color science, same corrective logic.