Content Hub - Preparing Original Capture Assets
Folder and File Naming
Legal characters: [ a-z ], [ A-Z ], [ 0-9 ], [ . ], [ _ ], [ - ]
(ILLEGAL: spaces or any other symbols/characters)
The following section applies to productions that are NOT using a Netflix API-integrated dailies solution. Production assets should be prepared by a DMT / DIT according to the following specification.
- Root directory: PROJECT TITLE
- Second-level directory: ASSET TYPE
- OCF - Original Camera Files
- WAV - Production Sound
- LOOKS - Any on-set looks (.cdl, .ccc, .edl with CDLs)
- LUT - Any LUTs used (.cube, .3dl)
- ALE - Any ALEs generated, with all fields available, including CDL columns if applicable
- PROXIES - Any proxies recorded or generated, whether at camera or through dailies processing (for editorial and/or review)
- REPORTS - Any data or dailies reports generated
- Third-level directory: SHOOT DAY & DATE
- Example: Day_001_20161016
- Fourth-level directory: CAMERA / SOUND ROLL
Below this folder level, original folder structure and filenames must be maintained from camera or sound cards.
MD5 checksum manifest must accompany all original camera files, stored in the folder of files upon which the checksums are being run, at one of the following directory levels:
- camera card
- shoot day
- root level
Netflix MD5 Checksum and ZIP Tool
For those familiar with Python, Netflix has provided a freely available Python package called the “Netflix Packager” (aka “npack”) that can run MD5 checksums and create the required checksum.txt file. The tool can also ZIP archive the frame sequences in COPY/STORE ONLY mode which is required for Content Hub uploading. Instructions and example command can be found in the following article: Content Hub - npack Tool.
Production Assets Example:
- Updated article title from "Preparing Original Capture Media" to "Preparing Original Capture Assets"
- Minor adjustments to section headings