How to Configure S-Log3 and S-Gamut3.Cine for Multicam

For multicam Sony shoots, the safest default is simple: put every camera that can support it in S-Log3 with S-Gamut3.Cine, expose from the same reference, and tell post exactly which cameras weren't actually recording that combination. Most matching problems start when one body is in S-Gamut3.Cine/S-Log3, another is in S-Gamut3/S-Log3, and a third is showing a Rec.709 monitor LUT that somebody mistakes for the recorded image. The camera settings are only half the job. Multicam works when production, editorial, and color all agree on the recorded color space, the monitoring transform, and the exposure target. If production doesn't document those three things, the colorist has to reverse-engineer the shoot from flattened-looking log clips, camera metadata that may not survive transcodes, and angle names like “A Cam Sony” that don't say enough.

The base configuration

For a Sony multicam package, use one shared acquisition target unless there's a strong reason not to:

Gamma: S-Log3
Color gamut / color mode: S-Gamut3.Cine
White balance: fixed Kelvin value, not auto
Tint / color compensation: match manually if the body exposes it
Shutter: matched by angle or speed across cameras
ISO / EI method: agreed per camera model and exposure plan
Monitoring LUT: same creative or technical LUT on every camera and monitor
Recording format: 10-bit 4:2:2 or better where possible

S-Log3 is the tone curve. S-Gamut3.Cine is the color space. They're often presented together in Sony menus, but they aren't the same setting. S-Log3 controls how brightness is encoded. S-Gamut3.Cine controls the primaries used to encode color.

Gamma and gamut are separate choices: one describes brightness encoding, the other describes color primaries.

That distinction matters because two clips can both be “S-Log3” and still not match if one was recorded as S-Gamut3.Cine and the other as S-Gamut3. The first grade node or color management input transform will treat color differently, especially in saturated costumes, LEDs, signage, gels, and deep blues or reds. Sony describes S-Gamut3.Cine/S-Log3 as a grading space built for a pure log workflow, with a color space similar in intent to negative film scan workflows and slightly wider than DCI-P3. In plain production terms, it's the more common choice when the footage is going into a conventional post pipeline, will be matched with other Cinema Line bodies, and will be transformed through Resolve color management, ACES, or a Sony technical LUT. S-Gamut3 is wider. On higher-end bodies, it can capture a very broad range, even beyond Rec.2020 in some contexts. That extra width is useful in some cinema and RAW workflows, but it isn't automatically easier. If the show doesn't need it, S-Gamut3.Cine is usually the better multicam target because it's widely supported, easier to monitor, and less likely to surprise editorial or finishing.

Why “all Sony” doesn't mean “already matched”

A common trap is assuming Sony bodies match because the menu labels look similar; even when they share S-Log3, check the camera mix and the post-relevant differences:

VENICE, FX9, and FX6
FX3, FX30, and Alpha bodies
Older FS-series cameras
Sensor, internal processing, and noise behavior
Dual-base ISO values and ND system; codec options and LUT handling

The goal is to remove avoidable variables before the colorist starts balancing sensor differences. The production should agree on the settings that affect matching most:

S-Log3 for all log cameras
S-Gamut3.Cine for all cameras that offer it
Matching project frame rate and shutter angle or shutter speed
Fixed white balance from the same lighting condition
Same exposure reference, such as a gray card, chart, or waveform target
Same monitor LUT from the same LUT file when possible
Same data range interpretation in post, especially after transcodes

If one camera can't record S-Gamut3.Cine/S-Log3, don't hide that fact. Label it clearly in the camera report and in the media organization. A small mismatch that's documented is much easier to handle than a small mismatch that post discovers after the multicam edit is locked.

S-Gamut3.Cine versus S-Gamut3 in post

The important difference for post is that the input transform must match the recorded gamut.

The recorded gamut needs a matching input transform; a mismatch can bend color in the wrong direction.

S-Gamut3.Cine is designed around a grading workflow that sits closer to common cinema delivery spaces. It's wider than DCI-P3, but not as extremely wide as S-Gamut3. For most multicam documentary, interview, and branded work, S-Gamut3.Cine/S-Log3 is the cleaner handoff. S-Gamut3 is the wider Sony color space. It can be useful when working from higher-end cinema cameras, RAW or X-OCN material, or a pipeline designed to preserve the widest possible camera gamut before the final grade. But if your pipeline treats S-Gamut3 footage as S-Gamut3.Cine, the image may not simply look a little off. It can produce hue errors that are hard to diagnose if your team has already built the grade on top of the wrong transform. In Resolve, this shows up as skin that never quite sits right, saturated colors that bend strangely, or a camera that seems to need secondaries on every shot even though exposure and white balance were sensible. The fix is to correct the input color space assignment. For mixed Sony gamuts, organize the footage by actual recording state:

Recorded state	Input assignment	Post treatment	If assigned incorrectly
S-Gamut3.Cine/S-Log3	Sony S-Gamut3.Cine/S-Log3	Standard log input for most Sony multicam angles	Matching stays predictable once exposure and white balance are balanced
S-Gamut3/S-Log3	Sony S-Gamut3/S-Log3	Wider Sony gamut, assigned separately from Cine clips	Saturated colors and skin tones can shift when treated as S-Gamut3.Cine
Rec.709 or S-Cinetone	Rec.709 or the matching camera-rendered input	Display-referred or camera-rendered footage, not log	Log transforms can distort contrast, saturation, and highlight rolloff
RAW or X-OCN	Camera raw decode to the chosen Sony gamma and gamut before color management	Decode settings establish the starting color state for the grade	Decode mismatches change the baseline before any creative correction

S-Gamut3.Cine/S-Log3 clips get a Sony S-Gamut3.Cine/S-Log3 input transform.
S-Gamut3/S-Log3 clips get a Sony S-Gamut3/S-Log3 input transform.
Treat Rec.709 or S-Cinetone clips as display-referred or camera-rendered footage, not log.
Decode RAW or X-OCN clips through camera raw settings before the project color pipeline sees them.

Once the inputs are correct, matching becomes a normal color job. When the inputs are wrong, every downstream adjustment is compensating for a pipeline error.

Exposure consistency matters more than exposure fashion

S-Log3 gives you room to grade, but it doesn't make exposure irrelevant. In multicam, inconsistent exposure is one of the fastest ways to make matching slow and noisy. The useful question is “what reference are all cameras using today?” Some crews rate Sony log a little brighter than nominal to keep noise down, especially on smaller bodies. That can work, but only if every camera operator exposes every camera to the same intent and the colorist knows what happened. For a controlled setup, use a chart or gray card under the key light and set every angle from the same reference. Crews commonly treat Sony’s S-Log3 middle gray target around 41 IRE, with official materials showing 18% gray in roughly the high-30s to low-40s range depending on implementation and display scale. One stop over middle gray lands around the high-40s. That gives you a useful language for exposure: nominal gray around 41, or a deliberate brighter placement around 48 to 50.

Set every angle from the same gray card or chart under the key light to keep exposure consistent.

There are two common ways to make that repeatable on set. If you're using zebras on the log signal, set the zebra target to the reference you actually want:

Around 41 IRE for nominal 18% gray in S-Log3
Around 48 to 50 IRE if the show is intentionally rating gray about one stop brighter
A separate higher zebra for highlight protection if the camera allows multiple zebra levels

The key is to zebra the card, not random parts of the frame. If one camera operator exposes skin by eye through a LUT, another exposes a gray card at 41, and a third rides ISO because the monitor looks dark, the cameras won't cut cleanly. If you're using a monitor LUT, make sure the LUT is only for viewing unless the workflow explicitly records baked footage. A standard S-Log3/S-Gamut3.Cine to Rec.709 or show LUT can make exposure easier for directors, clients, and camera operators, but it can also hide log placement errors. A LUT may make a slightly underexposed camera look acceptable on the day while leaving post with noisy shadows. The best on-set monitoring setup gives the camera operator both:

A consistent viewing LUT for judging contrast and color
A waveform, false color, or zebras reading the log signal or a known transformed signal

Don't mix those up. If the waveform is measuring the LUT output, your numeric targets are different from S-Log3 log targets. That's fine if everyone understands it, but it's a different exposure system.

Camera reports should capture the color pipeline, not just lens data

For multicam, the camera report needs to say more than roll, scene, lens, and FPS. Editorial and post need the information that determines how post should interpret the clip.

Camera reports and LUT notes keep each clip’s color interpretation clear for editorial and post.

Capture the actual color state for each camera body:

Camera model and firmware if relevant
Gamma setting
Gamut / color mode setting
Recording codec and bit depth
ISO, base ISO, EI, or Cine EI mode
White balance and tint
Monitoring LUT name
Whether your team used the LUT for viewing only or baked it into the recording
Any known exceptions by card, scene, or camera angle

This matters most when production mixes smaller cameras with larger bodies, and a post team shouldn't have to infer the pipeline from the camera name; some Alpha and FX cameras can record S-Gamut3.Cine/S-Log3 internally, but these vary by model:

menus
picture profiles
Cine EI behavior
LUT options
metadata support

If the production is using on-set CDLs or show LUTs, pass those along with the media. Sony’s CineAlta workflow materials describe on-set look management through ASC CDL values and LUTs as a way to carry the intended look into dailies and final grading. Even if the finishing colorist doesn't use the exact on-set look, having it explains what the DP and director were seeing.

Resolve setup for S-Gamut3.Cine/S-Log3

In DaVinci Resolve, you have three common approaches: Resolve Color Management, ACES, or manual CST/LUT nodes. Any can work, but the mistake is mixing them casually. For most editorial-to-color pipelines, Resolve Color Management is clean and easy to audit. A typical setup is:

Color science: DaVinci YRGB Color Managed
Automatic color management: off, if you want explicit control
Timeline color space: DaVinci Wide Gamut Intermediate
Output color space: Rec.709 Gamma 2.4 for standard SDR finishing, or the show’s required output
Clip input color space: Sony S-Gamut3.Cine/S-Log3 for the matching Sony log clips

DaVinci Wide Gamut Intermediate is designed as a large working space with a log-based intermediate tone curve. In practice, that means Resolve can transform the Sony log material into a broad scene-referred working space, then transform it to the output display. This is usually preferable to dropping a Rec.709 LUT directly onto every clip before balancing. For mixed gamuts, set the input color space per clip or per group. Don't rely on one global setting if some clips are S-Gamut3 and others are S-Gamut3.Cine. Use bins, clip colors, metadata columns, or camera angle naming to keep the assignments visible. ACES is also valid if your show uses it, and in that case, the critical choice is the Input Device Transform. S-Gamut3.Cine/S-Log3 clips need the matching Sony IDT. S-Gamut3/S-Log3 clips need their own matching Sony IDT. The same rule applies: gamma and gamut both matter. Manual node-based transforms can be useful for colorists who want everything visible in the node tree. A common pattern is an input Color Space Transform from Sony S-Gamut3.Cine/S-Log3 into a working space, then creative grading, then an output transform. This can be very clear in a grading session, but it requires discipline. If an editor also applied LUTs in the timeline or adjustment layers, you can end up double-transforming the image.

LUTs are for viewing unless you decide otherwise

Sony provides Look Profiles and LUT downloads for S-Gamut3.Cine/S-Log3 workflows, and many cameras and monitors can load LUTs for on-set viewing. That's useful, but it isn't the same thing as color management. A technical LUT can transform S-Log3/S-Gamut3.Cine toward Rec.709 for monitoring or quick editorial viewing. A creative LUT can add a show look. Both assume a specific input. If the LUT expects S-Gamut3.Cine/S-Log3 and the clip is actually S-Gamut3/S-Log3, Rec.709, or S-Cinetone, the result isn't trustworthy. For multicam, decide where LUTs live:

In camera or monitor for viewing only
In dailies generation for editorial reference
In Resolve as a temporary viewing transform
In the final grade as part of the approved look

Those are different uses, so don't bake a viewing LUT into proxies without telling editorial and color. If editorial cuts with LUT-baked proxies but finishing relinks to log camera originals, the locked edit may look different when conformed unless your team rebuilds the same viewing transform properly. For dailies, burn-ins or file naming can help. Mark whether the file is “log,” “LUT preview,” or “Rec.709 transcode.” Ambiguous proxy files are a common reason assistant editors and colorists lose time later.

Where multicam pipelines usually break

Most S-Log3 multicam problems come from repeatable setup mistakes, which is good news because they're preventable. Common failure modes include:

A camera operator sets one camera to S-Gamut3 while the others are S-Gamut3.Cine
Auto white balance drifts during an interview or live event
Your team bakes a LUT into one angle but uses it only for monitoring on the others
An editor or colorist applies a CST node or LUT twice, once at the clip level and once at the timeline level
Post interprets legal/full data range differently after transcode or export

The pattern is always the same: the image problem looks creative, but the cause is metadata, monitoring, or transform mismatch. That's why your team should keep the color pipeline visible to the whole team, not buried in one person’s camera menu.

A clean handoff for editorial and color

A good S-Log3/S-Gamut3.Cine multicam handoff gives post enough information to recreate the viewing intent and enough original data to grade properly. Editorial should know which files are camera originals, which are proxies, and whether any viewing LUT was applied. Assistant editors should preserve camera angle names and avoid flattening useful metadata during transcode. Post supervisors should make sure dailies, proxies, and finishing media don't silently change color interpretation. The colorist needs the camera reports, LUTs, CDLs if used, and a note explaining the exposure method. “All cameras S-Gamut3.Cine/S-Log3, gray exposed around 48 IRE for plus-one placement, LC-709A viewing LUT only, not baked” is the kind of sentence that saves real time. If the show used mixed Sony bodies, include the exceptions directly in the turnover notes. For example: “A/B cameras were FX6 in S-Gamut3.Cine/S-Log3. C camera was FX3 in S-Gamut3.Cine/S-Log3. Drone was Rec.709. Stage pickup on day 3 was S-Gamut3/S-Log3 by mistake.” That last sentence may feel painful to write, but it's much better than making the colorist discover it at midnight. The durable rule is this: match what you can in camera, measure exposure from a shared reference, and make the input transform unambiguous in Resolve. S-Log3 and S-Gamut3.Cine are strong multicam choices when the whole pipeline treats them as acquisition settings, not magic words.

FAQ

Use S-Log3 with S-Gamut3.Cine on every camera that supports it unless the production has a specific reason to use a different gamut or a camera-rendered profile. This gives post a consistent input transform and makes matching easier. If any camera records S-Gamut3, Rec.709, S-Cinetone, RAW, or another setting, document that clearly in the camera report and turnover notes.

S-Log3 is the gamma curve, which controls how brightness is encoded. S-Gamut3 and S-Gamut3.Cine are color gamuts, which control how color is encoded. S-Gamut3.Cine is commonly used for grading and standard post workflows, while S-Gamut3 is wider and may be used in higher-end cinema, RAW, or wide-gamut preservation workflows. In post, the input transform must match both the gamma and the gamut.

A common working target for 18% gray in S-Log3 is around 41 IRE. Some crews intentionally expose a little brighter, often placing gray around 48 to 50 IRE, to reduce noise or follow a show-specific exposure method. The important point in multicam is that all cameras use the same reference and that the exposure choice is communicated to post.

Yes, but make sure the LUT is used only for monitoring unless the workflow intentionally records a baked-in image. A Rec.709 or show LUT can help operators, clients, and directors view a more normal-looking image on set, but exposure tools must be understood correctly. If the waveform or zebras are reading the LUT output instead of the log signal, the numeric targets won't be the same as S-Log3 log targets.

In Resolve Color Management, a common setup is DaVinci YRGB Color Managed, automatic color management off for explicit control, DaVinci Wide Gamut Intermediate as the timeline color space, and Rec.709 Gamma 2.4 or the required delivery space as output. Assign each clip the correct input color space, such as Sony S-Gamut3.Cine/S-Log3 or Sony S-Gamut3/S-Log3. Don't use one global input setting if the cameras were recorded with different gamuts.

Treat gamma, gamut, LUT status, white balance, and exposure method as searchable production metadata, not just text in a PDF. Aspect supports project-level fields for camera and workflow notes, so assistants can keep those details attached to the assets as custom metadata.