This article needs additional citations for verification. (June 2017) |
A Digital Cinema Package (DCP) is a collection of digital files used to store and convey digital cinema (DC) audio, image, and data streams.
The term was popularized by Digital Cinema Initiatives, LLC in its original recommendation[1] for packaging DC contents. However, the industry tends to apply the term to the structure more formally known as the composition.[2] A DCP is a container format for compositions,[3] a hierarchical file structure that represents a title version. The DCP may carry a partial composition (e.g. not a complete set of files), a single complete composition, or multiple and complete compositions.[3]
The composition consists of a Composition Playlist (in XML format) that defines the playback sequence of a set of Track Files. Track Files carry the essence, which is wrapped using Material eXchange Format (MXF). Two track files at a minimum must be present in every composition (see SMPTE ST429-2 D-Cinema Packaging – DCP Constraints, or Cinepedia[4]): a track file carrying picture essence, and a track file carrying audio essence. The composition, consisting of a Composition Playlist (CPL) and associated track files, are distributed as a Digital Cinema Package (DCP). A composition is a complete representation of a title version, while the DCP need not carry a full composition. However, as already noted, it is commonplace in the industry to discuss the title in terms of a DCP, as that is the deliverable to the cinema.
The Picture Track File essence is compressed using JPEG 2000 and the Audio Track File carries a 24-bit linear PCM uncompressed multichannel WAV file. Encryption may optionally be applied to the essence of a track file to protect it from unauthorized use. The encryption used is AES 128-bit in CBC mode.
In practice, there are two versions of composition in use. The original version is called Interop DCP.[5] In 2009, a specification was published by SMPTE (SMPTE ST 429-2 Digital Cinema Packaging – DCP Constraints) for what is commonly referred to as SMPTE DCP. SMPTE DCP is similar but not backwards compatible with Interop DCP, resulting in an uphill effort to transition the industry from Interop DCP to SMPTE DCP.[6] SMPTE DCP requires significant constraints to ensure success in the field, as shown by ISDCF.[7] While legacy support for Interop DCP is necessary for commercial products, new productions are encouraged to be distributed in SMPTE DCP.