OCF
summary
Original Camera Files are treated as raw sensor negatives and Netflix describes a working system that ingests, inspects and serves only needed frames using Content Hub and a Conform Pull pipeline so editors fetch handles not terabytes. It leverages ACES, AMF and OpenTimelineIO/OTIO via EditDroid, runs processing on Sagan atop Cosmos, handles productions like 12 cameras 8 TB/day, preserves 3‑2‑1 backups, and is proven on La Casa de Papel Part 5.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:00What are OCF
- 2:19Why OCF
- 4:07Acronyms
- 8:12Amf
- 10:58On Set
- 13:21Media Inspections
- 14:31Metadata
- 15:12Demo
- 15:50Behind the Scenes
- 17:18Submission
- 19:01Internal Tools
related talks
28mDigital El Mariachi: the Beginnings of Cinema Workflows for Online Video
22mThe User (has) Generated Content... so what now?
36mArkisto: an open-source, standards-based framework for digital preservation
31mLights, Colors, Artwork
28mNanoColor - Light, Compact, OCIO-Based Color Management
24mAV1 at Netflix
14mContent Credentials - Identities for Media Content
47mHDR10+ Contents Generation Tools and Workflow