Cutsio Blog

Use ProRes for Cloud Review While Keeping RAW Originals Linked

Use one ProRes file for cloud review, Visual Intelligence search, and streaming while supported RAW originals stay linked for conform.

What is the practical Cutsio workflow for camera RAW and cloud review?

Upload the ProRes review or editorial file to Cutsio for streaming and Visual Intelligence indexing. On Enterprise, attach the matching ARRIRAW, RED R3D, Blackmagic RAW, Sony RAW, or Canon RAW original to the same asset record. The ProRes powers search and review; the linked original remains downloadable for conform. Cutsio does not decode every camera-native RAW format into a review stream.

This paired workflow is especially useful when the production already generates ProRes for offline editorial or dailies. Rather than creating a second review-only encode, the same ProRes can serve editorial, AI search, streaming, and browser review while the original stays connected for finishing.

This post explains where the workflow saves duplication and where a production still needs its normal camera-to-ProRes process.

Where does the paired workflow save time?

It avoids creating and managing a second cloud-review encode when a usable ProRes file already exists. The exact savings depend on the camera format, editorial codec, hardware, checksum process, network, and whether the production already creates dailies. Cutsio should be evaluated as the searchable MAM and review layer around that pipeline, not as a replacement for the DIT's color-managed transcode.

What is the actual workflow difference between PIX and Cutsio for raw footage?

The six-step PIX workflow versus the three-step Cutsio workflow represents a fundamental difference in how dailies reach the review team.

PIX workflow:

1. DIT offloads camera cards to RAID storage
2. DIT renders H.264 ProRes Proxy files from ARRIRAW or R3D source using DaVinci Resolve or Adobe Media Encoder (2-4 hours per shoot day)
3. DIT organizes transcoded H.264 files to match camera file naming and folder structure
4. DIT uploads H.264 files to PIX (upload time varies by bandwidth)
5. DIT sends review links to director, DP, producers
6. Post team manages separate conform relink between PIX's H.264 files and camera originals on local storage

Cutsio paired workflow:

1. DIT offloads camera cards to RAID storage
2. DIT creates or selects the production's ProRes review/editorial media
3. Upload ProRes to Cutsio for Visual Intelligence and browser review; attach the matching supported RAW original on Enterprise

The searchable asset keeps review media and the conform source associated. The final NLE conform still uses the camera originals and the production's normal relink process.

playback-id="IRBqKFllfQTZRgUpvF00DnjqMROLtyclqpWYRLQez6KQ"

title="Cutsio Visual Intelligence — search video by what the camera saw"

poster="https://image.mux.com/IRBqKFllfQTZRgUpvF00DnjqMROLtyclqpWYRLQez6KQ/thumbnail.jpg">

What determines review-stream quality?

The uploaded ProRes determines the image, framing, color transform, and metadata available to the review stream. The DIT or dailies colorist remains responsible for producing a review master that represents the intended viewing transform.

The review stream is a viewing proxy, not a finishing master. The original camera files remain available for download, conform, and finishing in the NLE.

What about productions that already have a ProRes proxy workflow?

Many productions already generate ProRes proxies or dailies for offline editing. ProRes upload is available on Studio and Enterprise, and that existing file can also power Cutsio search and review.

Enterprise adds the option to pair supported camera originals with the ProRes asset. That keeps the finishing source connected without implying that the RAW file itself is indexed or streamed.

How does the DIT benefit from avoiding duplicate review encodes?

When the editorial ProRes can also serve cloud review, time otherwise spent creating and tracking a separate review-only encode can be reinvested in:

• Verifying card offloads with checksums
• Managing metadata and look files for the color pipeline
• Supporting the DP with monitoring and look creation
• Preparing camera cards for the next shoot day
• Resting between long shoot days

Cutsio makes the approved ProRes review file searchable and shareable; it does not replace checksum verification, color-managed dailies creation, or camera-original backup.

FAQ

Does Cutsio support all camera raw formats?

Cutsio indexes and streams ProRes on Studio and Enterprise. Enterprise can pair supported RAW originals with the ProRes asset for download and conform. Confirm the exact codec and container before production.

Is the Cutsio review stream the same quality as a ProRes 4444 transcode?

The review stream is optimized for viewing, not finishing. Its source is the uploaded ProRes. For finishing, use the linked camera original and the production's normal conform workflow.

Can I delete the local camera files after uploading to Cutsio?

Cutsio retains the original camera files as downloadable attachments, but local backup is always recommended. Follow the standard 3-2-1 backup protocol: three copies, two media types, one off-site. Cutsio can serve as the off-site copy but should not be the only copy.

Does PIX or Flow Capture accept camera-native RAW?

Autodesk's product and contract terms can change. Verify current accepted formats and limits directly with Autodesk for the exact camera workflow.

How much upload bandwidth do I need?

Budget bandwidth for both the ProRes review media and any camera originals the team chooses to attach. Test a representative shoot-day volume before production rather than assuming a theoretical transfer time.