Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO 26429-7: Composition Playlist for Digital Cinema Packaging
Technical deep dive into the D-Cinema Composition Playlist (CPL) XML structure, reel organization, content markers, and digital signing
1. Composition Playlist Fundamentals
ISO 26429-7 (SMPTE 429-7) specifies the Composition Playlist (CPL) structure, a self-contained XML representation of a single complete D-Cinema work. The CPL consists of an ordered sequence of Reel structures, each referencing a set of external Track Files (picture, sound, subtitle) that are reproduced in parallel. The CPL is the editorial blueprint of a digital cinema presentation, created during mastering and included in the D-Cinema Package (DCP) distributed to theaters. Each Reel is analogous to a film reel, and the CPL controls the order and timing of reel playback. The CPL file itself is typically small (5-50 KB for a feature film), containing no actual media essence but rather the XML metadata that orchestrates how the media assets should be combined and presented. This separation of metadata from media assets is a fundamental architectural principle of the D-Cinema packaging model, enabling flexible content management without duplication of large media files. The CPL can be thought of as the “playlist” for the entire cinema presentation, defining not just what to play but also when to dim lights, trigger masking systems, and manage auxiliary content such as advertisements and trailers preceding the main feature. A single DCP distribution may contain multiple CPL files for different versions, language tracks, or regional variations of the same content.
The CPL uses rational numbers for EditRate, FrameRate, and ScreenAspectRatio values rather than floating point. This design choice eliminates precision errors in synchronization calculations, ensuring frame-accurate playback across diverse projector and sound processor implementations. For example, the common 24 fps rate is represented as 24/1 rather than 24.0, and NTSC-derived rates use 24000/1001 for precise synchronization.
2. XML Schema and Asset Structure
The CPL is encoded as UTF-8 XML using the namespace http://www.smpte-ra.org/schemas/429-7/2006/CPL. The top-level CompositionPlaylist element contains elements for identification (Id), content description (ContentTitleText, ContentKind), versioning (ContentVersion), ratings (RatingList), and the ReelList. Each Reel contains an AssetList with MainPicture, MainSound, MainSubtitle, and MainMarkers assets. Asset types form a type hierarchy rooted in GenericAssetType, with TrackFileAssetType adding KeyId (for encryption) and Hash (SHA-1 integrity) fields, and further specializations for picture (FrameRate, ScreenAspectRatio), sound (Language), and subtitle (Language) track files. The ContentVersion element supports version tracking with Id, LabelText, and Reason fields, enabling distributors to manage multiple versions of the same composition across different release windows (theatrical, airline, streaming). The RatingList allows region-specific rating information to be embedded directly in the CPL, with each Rating element containing a RatingSystem (e.g., “MPAA”, “BBFC”), a RatingValue, and optional RatingExtension metadata.
| Content Kind | Description | Required Markers |
|---|---|---|
| feature | A theatrical feature film | FFOC, LFOC, FFTC, LFTC, FFOI, LFOI, FFEC, FFOB, LFOB, LFEC |
| trailer | Short content promoting an upcoming feature (2-3 min) | FFOC, LFOC |
| rating | Slate indicating recommended age group | FFOC, LFOC, FFOB, LFOB |
| advertisement | Content promoting a product or service | FFOC, LFOC |
| transitional | Extremely short content (1-15 seconds) between compositions | FFOC, LFOC |
One critical engineering consideration: the CPL timeline reflects the editor’s intended synchronized playback it does NOT compensate for processing delays in exhibition equipment (projector image processing, sound processor latency). Any such compensation must be applied in-theater, not during mastering. This prevents a situation where the same CPL behaves differently on different auditorium configurations. Theater management systems typically handle playback offset configuration as a per-screen deployment parameter.
3. Digital Signing and Content Markers
The CPL supports optional XML digital signatures using RSA-SHA256 with X.509 certificate chains. The Signature element applies an enveloped signature to the entire CPL, providing authentication and integrity verification. Content Markers (defined in the MarkerAssetType) include standard positions such as FFOC (First Frame of Composition), LFOC (Last Frame of Composition), FFTC (First Frame of Title Credits), LFEC (Last Frame of End Credits), and the optional “FFLO” (First Frame Lights On) marker that allows production companies to signal when theater lights should be raised during end credits. The minimum reel duration is one second, and each asset’s playable region is defined by EntryPoint and Duration parameters relative to the IntrinsicDuration of the underlying track file. The marker system is extensible through EditHint values that provide additional metadata about each marker point, enabling automation of auxiliary exhibition systems such as masking control, curtain operation, and auditorium lighting cues synchronized to the content timeline. When a CPL is digitally signed, the signature is verified by the playback server before any content is decrypted or displayed, providing a strong authentication chain from the content creator to the exhibition system.
The extensibility mechanism through XML Schema’s “any” element allows future asset types (e.g., captions, haptic tracks, auxiliary data) to be added to the Reel’s AssetList without breaking existing implementations. Extension elements must belong to a namespace different from the CPL namespace and directly or indirectly extend GenericAssetType. This forward-compatibility mechanism has proven crucial for the evolution of the D-Cinema standard, allowing new features like high-frame-rate content and immersive audio formats to be added without requiring changes to the core CPL schema.
4. Frequently Asked Questions
Q: Can a single CPL reference track files on different storage volumes?
A: The CPL itself is agnostic to storage. The actual file location mapping is handled by the Asset Map (ISO 26429-9), which maps UUID identifiers in the CPL to physical file paths. A DCP with its CPL and assets can span multiple volumes.
A: The CPL itself is agnostic to storage. The actual file location mapping is handled by the Asset Map (ISO 26429-9), which maps UUID identifiers in the CPL to physical file paths. A DCP with its CPL and assets can span multiple volumes.
Q: How are different language versions handled?
A: Different language versions (e.g., French dubbed vs. original) are represented as different ContentVersion entries with distinct ContentVersion Id values. Each version would have its own CPL or the same CPL with different sound track file references, and would typically be distributed as separate DCPs.
A: Different language versions (e.g., French dubbed vs. original) are represented as different ContentVersion entries with distinct ContentVersion Id values. Each version would have its own CPL or the same CPL with different sound track file references, and would typically be distributed as separate DCPs.
Q: What is the purpose of the KeyId element in Track File Assets?
A: KeyId uniquely identifies the cryptographic key used to encrypt the underlying track file. It links to the Key Delivery Message (KDM, ISO 26430-1) which delivers the actual decryption key. If a track file is not encrypted, the KeyId element is omitted.
A: KeyId uniquely identifies the cryptographic key used to encrypt the underlying track file. It links to the Key Delivery Message (KDM, ISO 26430-1) which delivers the actual decryption key. If a track file is not encrypted, the KeyId element is omitted.
Q: Can a reel contain assets with different edit rates?
A: Each asset within a reel has its own EditRate parameter. However, all assets in a reel must be in editorial sync the Composition Playlist timeline does not compensate for processing delays, and synchronized Editable Units across different track files are expected to be reproduced simultaneously.
A: Each asset within a reel has its own EditRate parameter. However, all assets in a reel must be in editorial sync the Composition Playlist timeline does not compensate for processing delays, and synchronized Editable Units across different track files are expected to be reproduced simultaneously.
