The Handoff Where Quality Lives or Dies
A DP shoots a feature on an ARRI Alexa Mini LF in LogC4. The data wrangler delivers ProRes 422 HQ files to the colorist. The colorist opens the files and discovers the DP applied a custom LUT in-camera that baked into the ProRes output. The LogC4 data is gone. The colorist cannot grade from the baked-in look. The film must be re-transcoded from the original ARRIRAW files, which the data wrangler did not back up because the ProRes files were "good enough." The ARRIRAW files sat on a drive that was formatted and reused on day 4.
Get the handoff wrong and the image data you captured on set is gone before the colorist ever sees it. No amount of grading, power windows, or node trees can recover Log data that was destroyed by a baked-in LUT or overwritten by a reused drive.
This post covers the 6 decision points that determine whether your colorist receives maximum image data or a compromised file: recording format, LUT management, color space metadata, file organization, camera reports, and delivery medium. The standards referenced are ARRI's LogC4 and REVEAL Color Science documentation and RED's IPP2 pipeline specifications.
How the Set-to-Colorist Handoff Works
The handoff has 6 decision points. Each one either preserves or destroys image data.
Recording format is the first and most critical decision. RAW formats (ARRIRAW, R3D) preserve maximum sensor data. Log-encoded ProRes or XAVC preserves most data. ProRes with a baked-in LUT destroys data permanently. ARRI's REVEAL Color Science processes ARRIRAW through four stages: ADA-7 debayer, ACE4 color engine, AWG4 wide gamut, and the LogC4 curve. If you record ProRes with a LUT baked in, none of that pipeline data survives.
LUT management determines whether the colorist sees the intended look or has to guess it. On-set monitoring LUTs belong in the monitor, not in the recording. ARRI cameras support dual output: Log to recording media, LUT to monitor output via SDI. RED cameras apply IPP2 transforms as metadata in R3D files, not baked into the image. The colorist can override or reference the IPP2 settings in DaVinci Resolve.
Color space metadata tells the colorist what they are looking at. The colorist needs the recording color space (LogC4, S-Log3, RedLogFilm, Log3G10) and the intended display color space (Rec.709, Rec.2020, P3-D65). Without this information, the colorist spends the first hour of the session reverse-engineering the color space from a gray card reference.
File organization affects grading speed. Clips organized by scene and camera body let the colorist group shots by lighting setup. Clips organized by card number force the colorist to reorganize everything before grading begins.
Camera reports provide the metadata the colorist needs: lens, filter, aperture, white balance, and ISO for each clip. A gray card reference at the head of each lighting setup gives the colorist a grading anchor.
Delivery medium determines transfer speed. A 90-minute feature in ARRIRAW is approximately 3 TB. Use a high-speed SSD for features, an HDD for shorts, and cloud transfer for small projects.
Three Real-World Handoff Scenarios
Scenario 1: ARRI Alexa Mini LF, ARRIRAW + ProRes 4444 XQ Proxy
Context: A 20-day indie feature shooting on the Alexa Mini LF, recording ARRIRAW to Codex Compact Drive and ProRes 4444 XQ proxies to an SD card simultaneously. The colorist receives both ARRIRAW for grading and ProRes proxies for the editor. The DP applied a monitoring LUT through the SDI output only, not to the recorded file. Camera reports list lens (Cooke S4/i 32mm), aperture (f/2.8), and white balance (3,200K) for each scene. The colorist grades from ARRIRAW in LogC4 using ARRI's REVEAL Color Science pipeline in DaVinci Resolve Studio. Full dynamic range preserved: 14+ stops.
Scenario 2: Sony FX3, XAVC-I S-Log3
Context: A documentary shoot on the Sony FX3, which has no RAW recording option. The DP records XAVC-I in S-Log3 with S-Gamut3.Cine color space. A monitoring LUT is applied through the SDI output to a SmallHD monitor. The colorist receives XAVC-I files in S-Log3 with 14+ stops of dynamic range. No camera reports exist because the shoot was run-and-gun, so the colorist uses a gray card shot at the start of each location to establish a grading baseline. Quality preserved within the codec limits of XAVC-I (10-bit 4:2:2, 240 Mbps).
Scenario 3: RED Komodo, R3D RAW + ProRes Proxy
Context: A short film shot on the RED Komodo, recording R3D RAW internally and ProRes proxies to an SD card. The data wrangler delivers R3D files organized by scene number, with RMD sidecar files containing IPP2 color space and gamma settings. The colorist opens the R3D files in DaVinci Resolve, sets the Camera RAW profile to REDWideGamutRGB / Log3G10, and applies the IPP2 output transform as the last node. The RMD sidecar carries the DP's on-set look decisions as metadata, not baked into the image. The colorist grades from the full 16-bit RAW data with complete IPP2 flexibility.
Recording Format Comparison for Set-to-Colorist Handoff
The table below compares the recording formats most commonly used for the set-to-colorist handoff. The key column is colorist flexibility: how much grading latitude the colorist retains after the file leaves set.
| Format | Bit Depth | Color Space | Data Rate | Size per Hour | Colorist Flexibility | Quality Retention | Risk Level |
|---|---|---|---|---|---|---|---|
| ARRIRAW | 12-bit | LogC4 / AWG4 | ~330 MB/s | ~1.2 TB | Maximum | 100% | Low |
| R3D RAW | 16-bit | REDWideGamutRGB / Log3G10 | ~140 MB/s | ~500 GB | Maximum | 100% | Low |
| ProRes 4444 XQ (Log) | 12-bit | LogC4 or S-Log3 | ~500 Mbps | ~225 GB | High | ~95% | Low |
| ProRes 422 HQ (Log) | 10-bit | LogC4 or S-Log3 | ~220 Mbps | ~100 GB | Good | ~90% | Low |
| XAVC-I (S-Log3) | 10-bit | S-Log3 / S-Gamut3.Cine | ~240 Mbps | ~108 GB | Good | ~88% | Low |
| ProRes with baked-in LUT | 10-bit | Rec.709 (baked) | ~220 Mbps | ~100 GB | None | ~50% | High |
The critical row is the last one. A baked-in LUT collapses 12 or 14 stops of dynamic range into the 7 stops that Rec.709 can display. The colorist cannot recover highlights or shadows that were clipped during recording.
Step-by-Step: The Clean Handoff
- Before the shoot: Select your recording format. Choose RAW if the camera supports it. Choose Log-encoded ProRes or XAVC if it does not. Never record with a baked-in LUT.
- Configure dual output: Set the camera to record Log or RAW to the recording media. Route the monitoring LUT to the SDI or HDMI output only. On ARRI cameras, use the built-in LUT pipeline for monitoring. On RED, set the Output Color Space to Rec.709 for monitoring while R3D records RAW.
- Verify the LUT is not baked in: Record a 10-second test clip. Open it in DaVinci Resolve. If the image looks flat and desaturated, the Log data is intact. If it looks contrasty and saturated, the LUT is baked in. Fix the camera settings before the shoot.
- On set: Have the data wrangler organize clips by scene number and camera body, not by card number. Create a folder structure: Scene 01 / Camera A / Clip 001.mov.
- At each slate: The camera assistant records lens, filter, aperture, white balance, and ISO on the slate or in a digital camera report app like Shot Lister or ScriptE.
- At wrap: The data wrangler delivers camera reports with the footage. Back up all RAW or original files to two separate drives before formatting any card.
- Delivery to colorist: Include the recording format, color space, camera reports, and any on-set monitoring LUTs as separate .cube files. The colorist references the .cube LUT to understand the intended look without being locked to it.
- Plan drive capacity: Use the Storage Footage Calculator to estimate delivery drive capacity based on your recording format and shoot length.
Pro Tips and Common Mistakes
Pro Tip: Always record in Log or RAW, never with a baked-in LUT. A baked-in LUT permanently destroys highlight and shadow data that no colorist can recover.
Pro Tip: Deliver on-set monitoring LUTs as .cube files alongside the footage. The colorist can reference the DP's intended look without being constrained by it.
Pro Tip: Include a neutral gray card reference at the head of each lighting setup. The colorist uses this as a grading anchor to match shots across scenes and camera bodies.
Pro Tip: If mixing LogC3 and LogC4 footage from different ARRI cameras, use DaVinci Resolve Studio's "Decode as LogC4" option to bring LogC3 ARRIRAW into the REVEAL pipeline. This only works with ARRIRAW, not ProRes.
Common Mistake: Baking the monitoring LUT into the recorded file. The fix: verify the camera's recording color space is set to Log or RAW, and the LUT is routed to monitor output only. Test a clip in DaVinci Resolve before the shoot begins.
Common Mistake: Not delivering camera reports. The fix: use a digital camera report app or have the 1st AC record metadata on every slate. The colorist needs lens, filter, aperture, and white balance to match shots efficiently.
Common Mistake: Delivering files organized by card number instead of scene number. The fix: instruct the data wrangler to create a scene-based folder structure during offload, not after.
FAQ
What is the difference between Log and RAW?
RAW is unprocessed sensor data. The colorist controls debayering, white balance, ISO, and color space during grading. Log is a processed image encoded in a logarithmic gamma curve that preserves dynamic range but has already been debayered. RAW gives maximum flexibility. Log gives slightly less but with smaller file sizes and broader codec compatibility.
Should I apply a LUT in-camera or in the monitor?
Apply the LUT in the monitor only. ARRI and RED cameras both support routing a monitoring LUT to the SDI or HDMI output while recording Log or RAW to the card. If you apply the LUT in the camera's recording pipeline, it bakes into the file and destroys the Log data permanently.
What metadata does the colorist need?
The colorist needs: recording format, color space (LogC4, S-Log3, Log3G10), lens, filter, aperture, white balance, ISO, and any on-set LUTs as .cube files. Camera reports from the 1st AC or DIT provide this metadata. Without it, the colorist spends the first session reverse-engineering the production setup.
Can the colorist fix a baked-in LUT?
No. Once a LUT is baked into the recording, the Log data is gone. The colorist can make secondary adjustments to the baked-in image, but cannot recover the highlight and shadow detail that was clipped during the LUT application. The only fix is re-transcoding from the original RAW files, if they were backed up.
Related Tools
The Storage Footage Calculator lets you estimate delivery drive capacity based on your recording format and shoot length. For planning the full post pipeline, the Post-Production Timeline Calculator helps you schedule color, sound, and delivery phases. The Backup Strategy Calculator verifies your redundancy plan before a drive gets formatted and reused. For deeper reading, see our posts on small crew data management workflow and film production storage guide.
Conclusion
The set-to-colorist handoff is a one-way street. Once data is lost in recording, no amount of post-production can recover it. Record in Log or RAW. Keep LUTs in the monitor. Deliver metadata. Back up originals before formatting any card. Format availability varies by camera: the Sony FX3 has no RAW option, so XAVC-I in S-Log3 is the best available choice. The ARRI Alexa Mini LF and RED Komodo both offer RAW recording, and both should use it when the project budget allows for the storage. What handoff problem did your colorist discover on the last project, and could it have been prevented on set?
