Before approving a camera image, establish whether its look is being recorded into the footage or applied only to the preview. The same monitor can show a finished-looking picture while the recorded source retains a different appearance. That can be intentional, but the buyer and finishing team need to share the same understanding.
This is especially important when a client approves contrast, colour or a stylised treatment on set. An approval of the preview does not automatically explain how that appearance will be reproduced later or whether it can still be changed.
Trace the look through the image path
Ask for a simple description of the route from camera recording to monitor and final output. Identify any look-up table, usually called a LUT, or other transformation at each stage. The client does not need a technical wiring diagram; a labelled description is enough to locate the decisions.
ARRI's colour FAQ distinguishes creative transforms from display transforms in its specified workflows. It also makes clear that transforms relate to particular source encodings and camera generations. A LUT should therefore be identified by its intended use, not treated as a universal colour preset.
Confirm whether the transformation affects the recording, an external recorder, the monitor only or several outputs. Different paths can produce different answers on the same production.
Keep the approved appearance reproducible
If the look is a preview, ask how the finishing team will receive the correct reference and transformation information. A screenshot alone may communicate an intention but leave uncertainty about the actual image path.
If the treatment is recorded irreversibly, review it with that consequence in mind. Strongly altered contrast or colour may limit later options. The decision can still be appropriate when the required appearance and workflow are settled.
Test an exported sample through the intended review route. This checks whether the image the client approved is the image the delivery process produces, without assuming that a monitor and a file viewer are interpreting the material identically.
A hypothetical approval problem avoided
A corporate team approves a warm, contrast-rich preview for an interview. The producer explains that the camera records a more flexible source and the monitor applies a viewing look.
Before the full shoot, the team receives a short finished test with the intended transformation. They approve the result and record the reference. A later editor can distinguish the agreed appearance from the underlying source, rather than guessing why the camera files look flatter than the on-set screen.
In a different commission, a direct recorded treatment might be preferred. What matters is that its permanence is understood before capture.
Make approval specific
Record what was approved, where the look was applied and how it reaches delivery. Name any separate clean source or alternate output only if it is actually included in the scope.
If the preview transform changes during production, retain the association between each reference and the relevant material. Avoid a folder of unlabeled looks with no explanation of which one guided capture. A clear image path lets the buyer approve an appearance confidently without accidentally approving a different recording commitment.
Sources and scope
- ARRI colour management FAQ. ARRI separates creative look transforms and display transforms in specified workflows, with transforms dependent on the source encoding.
Discuss the capture brief
Contact Live Images to discuss this image requirement, the proposed scope and suitability for your production.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.