KNOWLEDGE MAP · VIDEO & CAMERAS

Exposure first. Encoding second.

Change exposure and inspect the actual ARRI LogC4 curve: the encoded value, the decoded result and the effect of rounding.

Read the numbers. Notice the assumptions. Then apply the idea to your footage.

01 / LOGC4 / SIGNAL LAB

Exposure becomes a code.

00.250.50.751-10 EV-5 EV0 EV+5 EV+10 EVCode V · LogC4
LogC4 · software0 EV → E = 0.18
Linear input E0.18000
12-bit code1140 / 4095Before rounding: 0.27840
Decoded E0.17998Δ = -1.687e-5
Code increment for the next stopΔV(+1 EV) = 0.05814

ARRI LogC4 software curve (§4), not a sensor model. ARRI specifies ≥12-bit storage; 8/10 bits deliberately test insufficient precision. This is not a camera or LUT viewer.

COLOR SCIENCE / 01 / VIDEO & CAMERAS

An experiment, not a preset.

On this page ↓
TOPIC ILLUSTRATION

THE ESSENTIAL IDEA

Camera log curves: LogC, S-Log and Blackmagic Film

Log distributes a captured light range across code values. It creates no new sensor range, does not independently define a gamut and does not turn a recording into RAW. First identify what was recorded; then decide how to view and process it.

  • Separate encoding from sensor range and gamut.
  • Verify the source pair and avoid double normalisation.
  • Distinguish rounding error from actual saturation.
Topic artwork, not an application screenshot, camera measurement or an exact sensor diagram.
01

Why encode light non-uniformly

A scene can contain a bright window and dark objects at once. Light ratios are conveniently described in stops: one stop doubles or halves exposure. In linear integer encoding, the top half of the range receives as many codes as all lower stops combined. This is not a defect of linear light; it is a question of distributing finitely many levels.

Log encoding reallocates those levels to make a large relative range convenient to store and process. It does not require immediately fitting the scene to one display contrast. Retained detail still depends on the complete acquisition chain: sensor, exposure, noise, encoding and compression. Not every display curve necessarily clips highlights, and the label log alone does not guarantee their survival.

What this means in practice

Increase exposure by one stop repeatedly in the lab. The linear value doubles each time; the LogC4 increment varies much less. This compares code allocation, not the dynamic range of an ALEXA.

02

A logarithmic curve and its linear segment

A pure logarithm turns multiplication into addition: log₂(2x) = log₂(x) + 1. Equal stops therefore occupy similar code intervals in its logarithmic region. Actual camera curves include scale, offsets and piecewise sections. Black need not have code zero, and an 18% reference need not encode to 0.18.

The lab implements ARRI’s software functions in specification §4.1. Threshold t separates the logarithmic branch from a linear extension for negative values introduced during processing. This is not the sensor hardware curve in §3. The inverse function first restores relative linear values; it performs neither a gamut transform nor a complete rendering for a monitor.

What this means in practice

At zero stops the linear value is 0.18 and LogC4 is about 0.2784. Without rounding, inverse conversion restores 0.18 within numerical precision.

03

Why direct log viewing looks flat

Log numbers describe a scene-relative signal, not the display codes expected for your final image. Direct viewing interprets midtones, black and highlights incorrectly. Misassigned primaries can alter colour relationships too. Raising Contrast and Saturation may produce a pleasing image without proving the transform is correct.

Not every flat clip is log, however. A Video/Full mismatch, a baked soft grade or incorrect HDR viewing can look similar. Conversely, a log file can appear contrasty because a monitoring LUT is enabled. Establish what the file contains first, then which transforms affect the Viewer.

What this means in practice

Disable only the viewing LUT and compare file values: toggling monitoring should not rewrite them. A LUT baked into recording instead changes the source state.

04

Curve and gamut are separate required facts

A transfer function relates linear values to codes; it does not define primary chromaticities. “S-Log3” is therefore incomplete without S-Gamut3 or S-Gamut3.Cine. ARRI generations of LogC and Wide Gamut must also be distinguished rather than mixed by familiar names.

An input transform must match the actual signal arriving at it. For RAW, that may be the chosen decoder output rather than the original sensor representation. Record gamut, curve and processing version first, then check whether colour management already performs the input transform. Transforming correctly decoded footage twice creates a new error rather than greater accuracy.

What this means in practice

Two Sony clips may share S-Log3 while using different gamuts. The same Input Gamma does not make the same Input Color Space correct for both.

05

LogC4 and ARRI Wide Gamut 4

LogC4 combines a defined transfer curve with ARRI Wide Gamut 4. The gamut specifies its primaries and D65; the curve represents relative scene values. Software LogC4 decoding does not require selecting a different curve shape for each EI. This does not make exposure or EI irrelevant to acquisition and headroom.

The specification includes an important constraint: LogC4 was designed for at least 12-bit quantisation, and ARRI explicitly discourages 10-bit LogC4 for archive or interchange. The lab therefore labels its 8/10-bit options as loss demonstrations, not production recording recommendations. LogC4 cannot be decoded as LogC3 simply because the names are similar.

What this means in practice

Compare 12 and 8 bits in the lab’s deep shadows. The restored linear-value error reveals rounding cost, not a real take’s noise level or usability.

06

S-Log3, S-Gamut3 and S-Gamut3.Cine

Sony S-Log3 can accompany different sets of primaries. S-Gamut3 and S-Gamut3.Cine are not two saturation strengths: they are different RGB definitions requiring matching transforms. The Cine suffix does not mean that a file is already DCI-P3 or ready for theatrical projection.

Sony’s technical summary describes S-Gamut3.Cine as a cinema-oriented gamut encompassing P3 without being identical to it. The practical lesson is not to choose a “better” triangle, but to retain the recording-mode information. A historical specification table should not be treated as a list of currently supported cameras; verify each device separately.

What this means in practice

Include the complete pair in the handover notes. “Sony Log” is insufficient for a reproducible input transform.

07

Film Gen 5 is not DaVinci Intermediate

Blackmagic Film and DaVinci Intermediate serve different purposes. Film describes a camera-oriented nonlinear representation for its colour-science generation; Intermediate accompanies DaVinci Wide Gamut as a working representation. They must not be substituted as Input Gamma just to obtain a similar contrast.

BRAW retains data and metadata for controlled decoding. Decode settings can change the RGB delivered to later tools. The current decoder output therefore matters as well as the original camera mode. Available controls depend on format and version; inspect the actual clip. This lab implements neither the Film Gen 5 curve nor the BRAW SDK rendering.

What this means in practice

If the decoder already produces working DWG/Intermediate, a CST expecting Blackmagic Film describes the wrong signal. Check what actually enters the node.

08

RAW and log are not opposites

RAW describes a class of retained data and deferred processing decisions. Log describes value encoding. RAW files can also use nonlinear packing, and decoding can produce log RGB. Thus “RAW is always linear and log is always non-RAW” is too crude.

An ordinary recorded log video clip has already undergone some camera processing and does not become RAW by assigning another gamma. Post-capture white-balance flexibility depends on retained information and decoder support. BRAW performs part of its demosaic in camera, illustrating why all RAW formats cannot be assigned one identical processing diagram.

What this means in practice

Record file format, decode mode and output gamut/curve separately. These three entries describe the material more clearly than “RAW Log”.

09

Input conversion and viewing are separate stages

A technical transform starts from a known source state. Managed projects use RCM or ACES rules; explicit workflows use a correctly configured transform. Its destination can be a working representation, not immediately Rec.709. Output rendering then prepares the result for the target display.

Balance and exposure operations can occupy different positions in a properly designed workflow. What matters is knowing which values each tool expects. It is incorrect to insist that all creative processing must follow a display LUT. A viewing LUT and a LUT baked into pixels are different states too. Bypass stages one at a time on a test clip to locate duplicate input or output transforms.

What this means in practice

For a diagnostic pass keep only input, working representation and output. If this chain is wrong, an additional look makes the cause harder to locate.

10

Exposure, noise and the measurement limit

Log cannot repair a saturated photosite or retroactively improve signal-to-noise ratio. Brightening an underexposed take lifts noise alongside signal. Darkening a clipped area can make it grey without restoring distinctions that were never measured.

“Overexpose every log camera by two stops” is not a reliable rule. Exposure decisions depend on camera, mode, noise, motion and important highlights. EI/ISO can affect analogue gain, metadata and headroom allocation differently. The lab studies only encoding: its slider is neither an ISO model nor a real sensor-noise simulation.

What this means in practice

Shoot a short exposure bracket in the actual recording mode and normalise the viewing conditions. Compare detail and noise, not just average brightness.

A MODEL YOU CAN CHECK

One source, several independent definitions.

Keep the meaning, the calculation and the limitation together.

E = 0.18 × 2^EV; V = LogC4(E); Ê = LogC4⁻¹(V)

EV is relative to a teaching reference of 0.18, not a camera exposure-meter reading. This uses §4 of ARRI’s software specification. Full-scale 12/10/8-bit rounding is separate; 8/10 bits are deliberate stress tests, not recommended LogC4 archival formats.

ConceptWhat it describesWhat not to conclude
LogEncoding of light values.Does not independently specify gamut or RAW.
Camera gamutPrimaries and white point of the representation.Does not replace the correct log curve.
RAWFormat and deferred decode operations.Does not guarantee no processing.
Viewing transformPreparation for a defined viewing target.Need not be an inverse technical encoding.

DO. OBSERVE. EXPLAIN.

Verify one input instead of guessing a LUT.

Start in the lab. For Resolve use your own clip with a verified gamut/log pair, in a project copy without arbitrary normalising LUTs.

  1. 01

    Set the reference

    Set EV = 0 with rounding off. Compare 0.18, its LogC4 code and the decoded value.

    CHECK

    The return to 0.18 differs only by floating-point precision.

  2. 02

    Separate range from precision

    Compare EV −6, 0 and +6, then enable 12 bits and deliberately 8 bits while watching error.

    CHECK

    Changing bit depth did not change the input light value.

  3. 03

    Verify the clip state

    In a project copy identify RAW decoding or the recorded log/gamut pair and colour-management input.

    CHECK

    The exact curve, gamut and already-applied transforms are documented.

  4. 04

    Check a single transform

    Inspect neutrals, highlight detail and the whole shot through one correct input→output path.

    CHECK

    There is no second normalising LUT/CST compensating the first.

Check your understanding

0 / 4

Tick only what you can explain yourself.

TEST THE EXPLANATION

A situation, not a trick question.

Answer first. Open the reasoning afterwards.

01A LogC3 LUT looks nicer on a LogC4 clip. Is it the correct input?

No. Appearance does not verify the curve and gamut. Establish correct interpretation first, then create the desired look separately.

02A different curve reveals detail in the window. Was sensor clipping recovered?

Not necessarily: the previous view may have clipped retained values. Measurement saturation and display-transform clipping occur at different stages.

03Why offer ten bits if ARRI requires twelve?

To expose insufficient precision. That mode deliberately violates the recommendation and is labelled a stress test, not a production export.

Avoid these shortcuts

  • Treating all Log curves as interchangeable.
  • Choosing the correct Log curve but the wrong camera gamut.
  • Treating flat Log as a finished creative look.
  • Treating RAW and Log as the same type of data.
  • Using a random LUT instead of a correct input transform.
  • Assuming Log can rescue clipped highlights or noise-buried shadows.
COLOR / DAVINCI RESOLVE

From the model to your workflow.

First identify the incoming values and operations already applied. Then check decoding, colour processing and the final export separately. The lab demonstrates its stated calculation; it does not measure your display, decode uploaded footage or certify camera settings.

Color Management ↗Scopes ↗Color Space Transform ↗

CHECK THE FOUNDATION

Sources and model limits.

Editorial review: 1 October 2026. Links identify the definitions and formulas; exercises are independent teaching examples.

  1. [1]
    ARRI · LogC4 specification, §4.1–4.3 ↗

    LogC4 software functions, AWG4, domain and bit-depth requirement. The lab uses §4, not the hardware curve in §3.

  2. [2]
    Sony · S-Gamut3.Cine / S-Log3 technical summary ↗

    S-Gamut3 versus S-Gamut3.Cine and their relationship to S-Log3. Used for definitions, not a current camera-compatibility list.

  3. [3]
    Blackmagic Design · Blackmagic RAW ↗

    Partial demosaic, embedded and sidecar metadata, decode controls. These properties are not attributed to every RAW format.

  4. [11]
    Adobe · Digital Negative specification resources ↗

    RAW formats and the DNG specification: data requires interpretation and a compatible decoder.

  5. [12]
    Blackmagic Design · DaVinci Resolve Color ↗

    Colour management and RAW processing. Available controls depend on the format, version and project mode.