DCI Specs - Digital Cinema Initiatives

Length (Value Length), followed by the data Value as shown below in Figure 9. One ormore of these data items are combined to form the logical parts shown above.Figure 9: Example of KLV Coding5.3.1.2. Format InformationEach track file is required to be a self-contained element, such that its essence ormetadata can be understood and presented as it was packaged by a compliant decoder.The information is required to be located in the predetermined specified area. The TrackFile is required to contain the following minimum information:• Required metadata for unique asset identification• Required metadata for decompression (optional)• Required metadata for decryption (optional)The following information is required to be configured in a human readable format:• Essence physical format description (e.g., 4096 x 2160)• Essence title asset information (e.g., The_Perfect_Movie_English_R2)5.3.1.3. ReelA Reel is a conceptual period of time having a specific duration, as defined below:• Track Files are required to be associated with a particular Reel.• A Track File is required to not cross over a reel boundary that is a playableportion of a track file, between the mark in and mark out points.• Reels are required to be composed of one or more Essence Track Files (e.g.,Picture Only, Sound and Picture, Sound and Picture and Subtitle, etc.)• The minimum duration of a Track File is required to be an integer number offrames, such that the length is greater than or equal to one (1) second.5.3.1.4. Track File ReplacementA Track File is the smallest unit that can be managed or replaced as a discrete file in thefield.5.3.1.5. SynchronizationEach Track File is required to contain the following synchronization information:• Start of Essence Data (mark in)DCI Digital Cinema System Specification v.1.2 Page 48