Cutsio Blog

Camera Originals vs Review Proxies: What Must Survive for Online Conform

The complete guide to what metadata must survive from camera original ingestion through cloud dailies to final conform — timecode, reel names, folder structure, sidecars, look files, audio sync, and checksums.

What metadata must survive from camera originals through cloud dailies to final conform?

For a successful online conform, six categories of metadata must survive intact from the camera original through the cloud dailies pipeline: timecode and reel names, folder structure, RAW parameter metadata, look files, audio sync references, and data integrity checksums. If any of these are lost or corrupted between ingestion and conform, the online editor will face offline clips, mismatched frames, lost looks, or audio sync drift.

The conform is the most fragile step in the post pipeline. Every intermediate system — DIT workstation, offload software, cloud upload, review platform, download, NLE import — is an opportunity for metadata to be lost or transformed. Understanding what must survive and how to verify it is essential for a clean conform.

This guide covers each metadata category with format-specific notes for ARRIRAW and RED R3D, and explains how to use look-approved ProRes files for Cutsio review while preserving camera originals and sidecars for conform.

Deliver videos professionally with How to Share Video Cuts With No Account Required for Viewers.

Timecode and Reel Names

Timecode and reel names are the most critical metadata for conform. Every clip must have continuous, matching timecode and a unique reel name for the conform to succeed.

The most common conform failure is reel name mismatch. If the offline edit uses a different reel naming convention than the source files — for example, if the offline uses "A001C001" but the source reel name is "A001_C001_240101" — Resolve cannot automatically match clips.

To prevent reel name issues:

• Use the native camera reel naming throughout the pipeline — do not rename clips
• If reel names must be modified, create a rename manifest that maps old to new names
• Verify that the offline edit uses the same reel names as the camera files
• Test a single clip through the full conform pipeline before principal photography begins

Cutsio preserves the original timecode and reel name metadata from the uploaded camera files. The download package contains the files with their original metadata intact.

Folder Structure

The folder structure of the camera originals must be preserved for conform, particularly for RED footage.

For RED footage specifically, flattening the RDM folder structure can break the association between R3D files and their sidecar metadata files. The online editor needs those files and reports for the approved RAW parameters and look references.

Cutsio preserves the original upload folder structure in the download package. If the RDM folder structure was uploaded, it is available for download. If individual files were uploaded without structure, the metadata is preserved in the file headers.

RAW Parameter Metadata

RAW parameter metadata controls how the raw sensor data is decoded during conform and grading.

The most fragile RAW parameter metadata is RED's RMD sidecar. If the RMD file is separated from its R3D during upload or download, the RAW parameters revert to camera defaults. Embedding the RMD metadata into the R3D file header before upload eliminates this risk.

Look Files (ALF4, RLM, CDL)

Look metadata carries the creative intent from set through dailies to the grade.

ALF4 look files travel inside the MXF container and are the most reliable to preserve. RED look metadata is more dependent on the RMD/sidecar workflow and should be verified before upload. 3D LUT files referenced by look metadata or CDL settings must be delivered alongside the camera originals as separate files.

Cutsio reads ALF4 and embedded RED look metadata for the review stream display. The original look files are preserved in the download package.

Audio Sync References

Audio metadata must survive for dual-system sound sync and audio conform.

For dual-system sound workflows, the scratch audio timecode must match the external recorder's timecode for automatic sync. Verify timecode alignment before uploading to the cloud dailies platform.

Cutsio indexes both the embedded scratch audio and any synced audio tracks in the review stream. The original camera files retain their embedded audio metadata in the download package.

Data Integrity Checksums

File integrity verification ensures that the conform source files are identical to the camera originals.

Cutsio provides checksum verification for downloaded files. The upload checksum manifest should be saved and compared to the download checksums to verify file integrity through the entire pipeline.

A conform-ready checklist for DITs and post supervisors

Use this checklist to verify that every element required for conform has survived the cloud dailies pipeline.

• [ ] Timecode: Source timecode matches between offline edit and camera originals
• [ ] Reel names: Offline edit reel names match camera file reel names
• [ ] Folder structure: RED RDM/RDC structure preserved; ARRI MXF folder organized logically
• [ ] RAW metadata: ARRIRAW MXF headers intact; RED RMD embedded in R3D or present as sidecar
• [ ] Look files: ALF4 or RED look metadata present; any 3D LUT files included in package
• [ ] Audio: Timecode aligns with dual-system sound; scratch audio present as reference
• [ ] Checksums: MD5 or SHA-256 match between upload manifest and download verification
• [ ] Frame count: Test clip frame count matches between review stream and original file
• [ ] Color: Test clip color in Resolve matches Cutsio review stream reference

FAQ

Can I use the Cutsio review stream as a conform source?

No. The review stream is a transcoded viewing proxy — it does not have the full resolution or RAW metadata required for finishing. Always download the original camera files from Cutsio for conform. The review stream is for review, not for finishing.

Which metadata element causes the most conform failures?

Reel name mismatch is the most common conform failure. Reel names must match between the offline edit and the camera original files. If the reel names differ, DaVinci Resolve cannot automatically relink clips during conform.

How do I verify that a cloud download package is complete?

Compare the file count and total size of the download to the upload manifest. Cutsio provides file listings for each download package. Check that all expected R3D files, RMD sidecars, and LUT files are present.

Is embedded ARRI MXF metadata more reliable than RED sidecar metadata?

Generally, yes. ARRI MXF files carry extensive metadata inside the file container, making them relatively self-contained. RED R3D workflows often rely on RMD files and other look-package references that can be separated during transfer, so preserve the full RDM/RDC folder and verify the look in the finishing application.

What should I do if conform metadata is lost during the pipeline?

If timecode or reel names are lost, the conform must be done manually by comparing the offline edit against the source files by eye — a time-consuming process. If RAW metadata or look files are lost, the colorist must recreate the look from scratch. Data integrity verification at each pipeline stage is the only prevention.