DCP

A Digital Cinema Package (DCP) is a collection of files stored on a formatted hard drive (typically Linux ext2/ext3 or FAT32) that conform to the Digital Cinema Initiatives (DCI) specification. A DCP is not a single video file — it is a structured set of MXF (Material Exchange Format) containers and XML (Extensible Markup Language) metadata documents that cinema servers read to project the film. A standard DCP contains: a Picture Track File (JPEG2000 compressed video in an MXF container, per SMPTE ST 422M), an Audio Track File (24-bit, 48kHz or 96kHz PCM audio in an MXF container, up to 16 channels for Atmos/SMPTE layouts), a Composition Playlist (CPL — an XML file that describes the order and timing of all reels, subtitles, and markers), a Packing List (PKL — an XML manifest of all files with SHA-1 checksums for verification), and an Asset Map (an XML index that maps file URIs to physical locations on the drive). Per the DCI specification, the JPEG2000 compression inside a DCP uses wavelet-based intra-frame encoding capped at a maximum variable bitrate of 250 Mbps for both 2K (2048x1080) and 4K (4096x2160) at 24fps; the higher 500 Mbps ceiling applies only to High Frame Rate or HDR content. These are significantly higher than any web delivery codec — a 2-hour 2K DCP is approximately 200-250 GB. The color space is XYZ (CIE 1931), which is display-independent: the projector converts XYZ to its native gamut. Frame rates are locked to 24 or 48 fps for 2K, 24 fps for 4K. Frame rates like 23.976, 25, or 29.97 are not DCI-compliant and will be rejected by cinema servers. Subtitles in DCP are either burned into the picture track (interoperable but inflexible) or delivered as separate XML/SMPTE timed text files (the standard approach for multi-language distribution).

Adobe Premiere Pro does not have a native DCP export option. You cannot select File > Export > DCP because the DCI specification requires specific MXF wrapping, JPEG2000 encoding at exact bitrates, XYZ color space conversion, and XML metadata that consumer NLEs do not generate. Even DaVinci Resolve's built-in DCP export (available in Studio) is limited — it creates unencrypted DCPs suitable for small screenings but not for wide theatrical release with KDM (Key Delivery Message) encryption. The professional DCP creation workflow: finish your master in Resolve or your preferred NLE, export a TIFF image sequence or high-quality ProRes 4444 XQ master, then use dedicated DCP software to encode. OpenDCP (open-source) handles JPEG2000 encoding, MXF wrapping, and XML generation. DCP-o-matic provides a GUI front-end for OpenDCP and is widely used for festival screenings. For theatrical release, facilities use GDC, Dolby, or QuVis DCP servers with SMPTE KDM encryption that locks the DCP to specific projector serial numbers and time windows. Color accuracy is the biggest gotcha. Your timeline is in Rec.709 or DCI-P3. The DCP requires XYZ color space. The conversion matrix is defined in SMPTE ST 428-7, and an incorrect conversion shifts every color in your film — skin tones go green, blacks lift, whites go blue. Always preview your DCP on a calibrated DCI projector before distribution. A screening room with a Barco Series 4 or Christie Solaria projector, calibrated to the DCI standard of 14 foot-lamberts (48 cd/m², +/- 3 ftL) for 2D or 7 fL for 3D, will reveal problems that no desktop monitor can. Budget consideration: professional DCP mastering costs $2,000-8,000 depending on resolution, audio channel count, and encryption requirements.