Cutsio Blog

RED R3D .rlm Look Files: How Metadata Travels from Set to Grade in a Cloud Dailies Pipeline

Learn how RED .rlm look files, .rsx color settings, and RMD sidecar metadata travel from camera through cloud dailies to DaVinci Resolve grade — and how to prevent the 'it looked better in dailies' problem.

How do RED .rlm look files travel from set to grade in a cloud dailies workflow?

RED looks travel through a dailies workflow as camera metadata, REDCINE-X metadata, or sidecar metadata such as RMD files, depending on how the DIT saves the look. In a cloud dailies pipeline, the safest workflow is to keep the original R3D folder structure intact, preserve any RMD/metadata sidecars, and treat the dailies look as a non-destructive viewing reference rather than a baked proxy. Cutsio's enterprise R3D ingestion is designed around that principle: generate a review stream from camera originals while keeping the original R3D media attached for grade and conform.

The traditional problem with RED look workflows is that the look the DP and director approved in dailies is not always the look the colorist starts with in the grade. This disconnect happens when the look is baked into proxies, stripped during proxy creation, or stored in a sidecar file that does not travel with the R3D folder. The director remembers a specific dailies image, the colorist starts from a different interpretation of the same raw clip, and the first grading session begins with "it looked better in the dailies."

RED's metadata ecosystem is more complex than a simple LUT handoff because RED has iterated through multiple color science generations and metadata sidecar conventions. Understanding how in-camera looks, REDCINE-X changes, RMD sidecars, and NLE raw settings interact is essential for a predictable workflow.

Working with raw camera footage? Check out How to Build a Searchable Library From ARRIRAW, RED R3D, and ProRes Footage.

Perfect your color grade with How to use the node editor for color grading in DaVinci Resolve.

What are the different RED metadata files and how do they relate to each other?

RED footage generates multiple metadata files and embedded data structures that serve different purposes in the pipeline.

| Metadata Type | File Extension | Storage Location | Purpose |

| :--- | :--- | :--- | :--- |

| In-camera look | Embedded metadata | Inside the R3D metadata | The color settings used for camera monitoring and default interpretation |

| RED metadata | .rmd | Sidecar in the R3D clip folder | REDCINE-X metadata changes and look adjustments for the clip |

| Legacy RED metadata | .rsx | Sidecar for older workflows | Older RED metadata XML convention, generally superseded by RMD |

| RED look export | Varies by camera/software generation | Sidecar or camera transfer file | A saved creative look or metadata preset from RED software |

| CDL/LUT references | Varies | Embedded metadata or sidecar | Basic color correction or creative transform used as a reference |

The RMD file is the most important sidecar in many modern RED workflows because REDCINE-X creates it when a clip's metadata is changed. If the RMD is lost, an NLE or color system may still read the R3D, but it may not see the same look or raw-setting interpretation that editorial saw.

The key distinction for dailies: camera-original metadata and RMD sidecars are not the same as a baked review proxy. Metadata can guide interpretation while preserving raw flexibility; a baked proxy cannot be unbaked into the original camera data.

What happens to RED look files when R3D footage passes through a cloud dailies platform?

When R3D footage is uploaded to Cutsio through the enterprise raw ingestion add-on, the platform should receive the complete R3D folder structure, including any RMD sidecars and metadata files created during the DIT workflow. The review stream can then be generated from the camera-original media while the original R3D package remains available for finishing.

The behavior by look file scenario:

| Scenario | Metadata present? | Sidecar present? | Review-stream implication |

| :--- | :--- | :--- | :--- |

| On-camera look applied | Yes | Maybe | Review can follow the camera metadata if preserved |

| Look adjusted in REDCINE-X | Maybe | Usually RMD | Preserve the RMD with the R3D folder |

| No look metadata | No | No | Use the default RED color pipeline or project transform |

| Look baked into proxy | N/A (proxy is baked) | N/A | Not applicable — Cutsio uses original R3D |

The critical advantage of the metadata-driven approach is that the original R3D media is not replaced by a baked proxy. The review stream can reflect the intended viewing transform while the colorist still receives the original R3D package for raw settings, debayer control, and final grade decisions.

How does the DIT ensure RED look files survive the dailies pipeline?

The DIT must verify that the intended look metadata travels with the R3D package before upload. The workflow varies depending on where the look was created.

For on-camera looks: keep the original RDM/RDC folder structure intact during offload. Do not flatten the folder to isolated R3D files unless the finishing team has explicitly approved that workflow.

For looks adjusted in REDCINE-X or other metadata-aware tools: preserve the RMD sidecar created for the clip and upload it alongside the matching R3D media. The RMD is often the record of the metadata interpretation that editorial or dailies approved.

For looks created in Livegrade or third-party grading tools: export a clear CDL/LUT/reference package and document whether it is for monitoring, dailies, editorial, or final grade. Keep that reference package with the camera originals instead of relying on a rendered proxy as the only record.

The recommended practice: preserve the full RED folder structure and include a short metadata handoff note for post. Sidecar files are fragile because they can be separated from their parent clip during drive handoffs or cloud uploads. Folder integrity matters as much as the R3D file itself.

How does the colorist recover the dailies look in DaVinci Resolve?

The colorist working with RED R3D files in DaVinci Resolve has three practical options for recovering the dailies look:

1. Use the R3D metadata interpretation: DaVinci Resolve can read RED raw metadata and expose raw settings for the clip. The colorist should confirm that the project's RED settings match the intended camera or clip metadata behavior.
2. Keep the RMD sidecar with the clip: If an RMD file is part of the approved dailies interpretation, it should remain next to the matching R3D media throughout conform and grade handoff.
3. Match to the Cutsio review stream: Use the review stream as a visual reference when metadata is incomplete or when the final grade intentionally starts from a different baseline.

The most reliable method is to test the exact camera, DIT, dailies, and Resolve settings before principal photography. RED metadata behavior is software-version dependent enough that a one-clip pipeline test is worth doing.

What happens when RED color science versions don't match between the dailies platform and the NLE?

Different RED color science settings and SDK versions can produce different visual interpretations from the same R3D file. If the dailies platform, NLE, and grading system use different RED SDK versions or different default raw settings, the same clip can appear differently in review versus grade.

Cutsio's enterprise R3D workflow should be validated against the production's selected RED color pipeline before the shoot. If the R3D was recorded for an IPP2 / REDWideGamutRGB / Log3G10 workflow, confirm that the review stream and grade setup use compatible assumptions.

To verify color science version alignment:

1. Check the RED SDK version in each piece of software
2. Confirm the R3D was recorded in a consistent REDCODE color science version
3. Test a single clip through the full pipeline before principal photography begins

If the dailies look and the grade look still do not match after confirming SDK alignment, the mismatch may be a metadata handoff issue, a project color-management setting, or an intentional creative reset in the grade. The point of preserving metadata is to make that difference visible and controllable.

How does Visual Intelligence index RED footage with look files applied?

Cutsio's Visual Intelligence indexes the generated review media, not a manually exported proxy from editorial. That means search results reflect the appearance of the review stream that the team is actually using, while the original R3D media remains attached for conform and grade.

The original R3D files remain the source for finishing. The review index is for finding moments, references, and selects quickly; the original media is for the final image pipeline.

FAQ

Does Cutsio support RED .rlm sidecar files uploaded alongside R3D footage?

Cutsio's enterprise raw ingestion add-on is designed for camera-original workflows. For RED footage, upload the complete R3D folder structure and preserve RMD or other sidecar metadata files when they are part of the approved look. Contact the Cutsio team for production-specific sidecar handling requirements.

What happens if the .rlm look file is missing or corrupted?

If look metadata is missing, the review stream may fall back to the production's default RED viewing transform or require a corrected upload with the missing sidecar/reference files. The original R3D file is unaffected, which is why camera-original retention matters.

Can the director approve a look in dailies and have that look carry through to the final grade?

Yes, if the look metadata, sidecars, and color-management assumptions are preserved and documented. The colorist can then treat the dailies look as a reference and choose to honor, modify, or replace it in the final grade.

How does the RED .rlm workflow differ from ARRI look files?

RED look workflows often involve R3D metadata plus RMD or other sidecar files, while ARRI workflows commonly center on ALF2 or ALF4 look files carried through the ARRI metadata ecosystem. Both can be non-destructive when handled correctly. The key difference is that RED's color science and metadata conventions vary by camera generation and software version, so the handoff needs more explicit verification.

Do REDCODE compression ratios affect look file metadata?

No. REDCODE compression ratios affect image compression and file size, not whether a production should preserve metadata sidecars and folder structure. A 5:1 clip and a 12:1 clip still need the same disciplined handoff if the dailies look is expected to travel to grade.