From camera to display. Explain every connection.

A processing diagram is more than an order of boxes. Every connection carries an image state: colour coordinates, encoding, range and the history of completed operations. A label saying Color explains none of this. A useful label states what the next tool is entitled to expect.

Separate states from storage. The same working signal may exist in memory or a suitable intermediate file; the same container may carry different states. EXR, MOV, log or HDR alone is not enough to reconstruct a pipeline.

Capture and decoding precede most visible colour nodes. The sensor, camera processing, RAW settings, codec, Y′CbCr matrix and range interpretation determine the RGB received by the application. Grading on Color does not automatically undo a clipped channel or an earlier decode error.

Preserve source information and compare originals and proxies through the same procedure. An intermediate may change profile, range or baked look as well as bit depth and compression. Matching appearance does not prove equal latitude for further processing.

The input transform brings a known source into a working representation. For a camera this may include its gamut and curve; a finished image must be recognised as already having an intended appearance. One operation for every file is justified only if they share an input contract.

A wrong assignment does not become correct because the picture looks more familiar. Confirm the source using documentation or recording settings, then inspect neutral and saturated areas. Separate coordinate conversion from creative reconstruction that the source may no longer support.

Some operations are easier to reason about before output rendering, while original channel relationships and highlight values remain available. But before output does not mean any operation in any log encoding. Light addition, keying, blur and exposure adjustments may require different numerical representations.

Find out whether a tool operates on current codes or internally converts them. When changing order, inspect highlights, edges and saturated colours as well as midtones. Floating point cannot correct a conceptually wrong operation.

A shared working representation helps reconcile sources but does not make all cameras identical. It normalises the description of data; differences in lighting, exposure, spectral response and source processing still require judgement and grading. Technical normalisation and creative matching are separate tasks.

Store working definitions with the project. Changing systems, configuration versions or rendering parameters may affect the result without editing a node. A short reference render helps verify reproducibility after moving to another workstation.

A look has its own input and output; it is not a file that understands every image. A LUT may combine a technical transform with a creative style. Placement depends on both endpoints: camera log → Rec.709 cannot automatically be treated as a working look inside DWG/Intermediate.

A table has an input domain and an interpolation method. Its grid is not equivalent to an exact formula, especially outside its designed range. Preserve the file, checksum, expected representations and application history for reproducibility. Renaming it does not describe its mathematics.

The rendering boundary decides how the scene is reproduced within a target image’s capabilities. Beyond it, values describe the prepared output. Display or file encoding may be a separate step. Do not confuse this with pressing Render on Deliver: one button may save the result of an entire chain.

The laboratory uses a deliberately simple T curve. It explains the boundary rather than reproducing ACES or Resolve. Omitting T leaves more high values, but a bounded export cannot retain them all. Repeating T changes tones without changing metadata.

Working pixels, a stored master and monitor light are different stages. An application may apply a view transform only for viewing; the display and operating system add interpretation conditions. A monitoring LUT is not necessarily baked into an export. A Viewer/player mismatch therefore does not prove the grade is wrong.

Compare the same frame under matched conditions with a known viewing state. Re-import as an already prepared output, without repeating camera input and creative processing. Then separately verify what is sent to the external path.

Agree the VFX handoff state in advance: linear scene, a log working encoding or a finished image. Specify whether look and output are baked, which channels carry colour, how alpha is represented and where processing is view-only. EXR alone does not guarantee scene-linear ACEScg.

On return, inspect translucent edges, highlights and saturated objects as well as overall appearance. A UI logo and a virtual scene element may belong at different compositing points. The rule of putting all graphics after the grade misses that distinction.

Separate the shared creative result from deliverable versions. SDR, HDR and web graphics may differ in tone rendering, white, gamut and title composition as well as tags. Specify the branch point and where output-specific trims belong.

Preserve shared work before output losses and verify each branch separately. Inverting a finished 8-bit master cannot restore original precision even when primaries and transfer function are known. Keep version control after approval too: replacing a LUT or output transform requires a newly verified render.

Node order matters because operations generally do not commute. Gain before nonlinear rendering and gain after it process different data. Similarly, moving an input-specific LUT to Timeline does not make it universal, and conversion to linear encoding is not necessarily display rendering.

Re-label the expected state after moving an operation. Account for Group Pre-Clip, Clip, Group Post-Clip and Timeline levels where used: the clip graph is not the whole history. Project transforms and monitoring operations may exist outside visible nodes.

Find the first divergence rather than the final visible symptom. If working values are wrong immediately after input, inspect source description and decoding. If working data is correct but the file differs, inspect output, clipping, encoding and range. If the file matches but viewing differs, inspect interpretation and display handling.

Flat means log and contrasty means double CST are not conclusive diagnoses. Several causes share these symptoms. A neutral test helps separate range and transfer behaviour, but gamut and LUT checks also require coloured and bright samples.

A workflow record should let another person reproduce the result without verbal guesswork. Save application/version, decode settings, inputs, working representation, look checksum, output and its parameters, range, export format and viewing conditions. Mark what is already baked into each intermediate file.

Include a short reference and comparison criteria. An uncompressed or reproducible mathematical chain can use numerical tolerances; compressed video needs allowances for decoding and losses. A matching screenshot is not a substitute for checking motion, edges and all delivery variants.