Receive images with their context
Before compositing begins, verify that the render sequence is complete and matches the approved version. Check the frame range, resolution, naming pattern and channel inventory. Missing frames and accidental duplicates can survive a casual still review. Compare the first, middle and last frames against the render manifest, then play the entire sequence. Confirm that editorial handles are present if the edit requires them.
OpenEXR is widely used for high-dynamic-range image interchange and can carry multiple channels. That flexibility does not establish a shared interpretation automatically. Record channel names, compression choices, alpha behavior and color space. Agree whether the receiving application should treat the images as scene-linear data and identify any display transform that was used during approval. A reference movie is useful, but it should not become the only record of the intended appearance.
Correct the image without losing the garment
Foundry Nuke, Fusion in DaVinci Resolve and Adobe After Effects can support different compositing workflows. Choose an approach that preserves the necessary image precision and gives the team a reproducible result. Begin by reconstructing the intended beauty image from the supplied inputs where applicable. Check that pass combinations match the renderer’s expectations before introducing creative adjustments. Incorrect reconstruction can create material changes that look like grading choices.
Use masks and utility passes to make targeted changes, but resist treating every garment component as an unrelated graphic layer. A large local contrast adjustment can destroy the relationship between a fold’s highlight and shadow. The result may look sharper while making the textile less coherent. Review the entire silhouette after close-up work. If a correction requires inventing missing structure across many frames, consider whether a source render fix is more reliable.
Cryptomatte can help isolate objects or materials when supported by the pipeline. Test its output early, especially around transparency and motion blur. Edge behavior depends on how the renderer, file and compositor handle coverage. Inspect bright garments against dark backgrounds and the reverse. Halos, incorrect premultiplication and contaminated edges often become obvious only after a background or exposure change.
Keep color decisions traceable
Separate working-space operations from output rendering. A scene-linear compositing adjustment and a display-referred finishing adjustment do not behave identically. Document the chosen OpenColorIO configuration, input interpretation and viewing transform. If ACES is used, specify the actual workflow rather than assuming the acronym defines every decision. Avoid applying the same display transform twice when producing review movies.
For an SDR deliverable, confirm the requested viewing and encoding conditions, including whether Rec.709 is expected. HDR delivery introduces additional mastering and metadata requirements that should be agreed with the recipient. Do not infer them from a high-dynamic-range render file. Review garment colors across the intended deliverables, paying particular attention to deep saturated textiles, subtle neutral fabrics and bright specular details.
Color review also needs a human agreement. Establish who approves material fidelity, who approves the overall grade and how conflicting notes are resolved. A producer asking for a warmer scene may not intend the hero garment to change hue. Keep those requests separate in the review log. Versioned notes reduce the risk of a late global adjustment undoing an earlier product-specific approval.
Deliver a specification, not a guess
| Field | Decision to record | Why it matters |
|---|---|---|
| Picture | Dimensions, aspect ratio and frame rate | Prevents accidental reframing or conversion |
| Color | Output space and transform | Preserves the approved viewing intent |
| File | Container, codec and naming | Matches recipient requirements |
| Audio | Channels, level specification and rights | Avoids incomplete or unusable masters |
Retain a high-quality master separately from platform-specific encodes. H.264 can be appropriate for many review or distribution files, while ProRes is commonly requested in editorial and delivery workflows. The right choice depends on the recipient’s written specification, not a universal quality ranking. Test the target encode on a difficult range containing fast cloth motion, fine weave and dark gradients.
Watch the exported file from beginning to end, preferably in the expected playback environment. Look for missing frames, compression shimmer, banding, unintended borders and audio synchronization issues. Compare the first and last visible frames with the approved edit. Confirm captions or text-safe requirements where relevant. A successful export dialog does not verify the contents of the file.
Archive the final master, approved review copy, project files, relevant caches, dependencies and a readable manifest. Note software versions and any assets that cannot be redistributed. Preserve licensing information for music, fonts, photographs and third-party models. An archive should help another person reconstruct the delivery’s context without relying on the original artist’s memory.
Final gate
The job is complete when the approved version, delivery specification and checked output agree. Keep that evidence together with the master.
