1、 Table of Contents Page 1 Scope 3 2 Normative References 3 3 Overview . 4 4 Terminology 5 5 Synchronization. 6 6 CompositionPlaylist Structure . 7 6.1 Id 7 6.2 AnnotationText optional . 7 6.3 IconId optional 8 6.4 Issue Date 8 6.5 Issuer optional 8 6.6 Creator optional 8 6.7 ContentTitleText. 8 6.8
2、ContentKind . 8 6.9 ContentVersion 9 6.10 RatingList 10 6.11 ReelList . 10 6.12 Signer optional 10 6.13 Signature optional . 11 7 Reel Structure . 11 7.1 Id 12 7.2 AnnotationText optional . 12 7.3 AssetList. 12 8 Asset Structure 13 8.1 GenericAssetType 13 8.2 TrackFileAssetType . 15 8.3 MarkerAssetT
3、ype. 16 8.4 PictureTrackFileAssetType 18 8.5 SoundTrackFileAssetType. 19 8.6 SubtitleTrackFileAssetType . 19 9 CPL Constraints 20 9.1 Content Markers 20 9.2 Minimum Reel Duration 21 Page 1 of 30 pages SMPTE 429-7-2006 SMPTE STANDARD D-Cinema Packaging Composition Playlist Copyright 2006 by THE SOCIE
4、TY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved October 3, 2006 SMPTE 429-7-2006 Page 2 of 30 pages 10 XML Schema .22 11 Sample (Informative) .26 12 XML Diagram Legend (Informative) 27 12.1 Element symbols 27 12.2 Model symbols (“composit
5、ors“) 28 12.3 Types28 12.4 Model groups and references.29 Annex A Bibliography (Informative).30 Foreword SMPTE (the Society of Motion Picture and Television Engineers) is an internationally-recognized standards developing organization. Headquartered and incorporated in the United States of America,
6、SMPTE has members in over 80 countries on six continents. SMPTEs Engineering Documents, including Standards, Recommended Practices and Engineering Guidelines, are prepared by SMPTEs Technology Committees. Participation in these Committees is open to all with a bona fide interest in their work. SMPTE
7、 cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering Documents are drafted in accordance with the rules given in Part XIII of its Administrative practices. Proposed SMPTE Standard 429-7 was prepared by Technology Committee DC28. SMPTE 429-7
8、-2006 Page 3 of 30 pages 1 Scope This document specifies the Composition Playlist structure. The Composition Playlist is a self-contained representation of a single complete D-Cinema work, such as a motion picture, or a trailer, or an advertisement, etc. The Composition Playlist consists of an order
9、ed sequence of Reel structures, each referencing a set of external Track Files, e.g. a sound or picture Track File, which are meant to be reproduced in parallel. Each Reel is analogous to a film reel and the Composition Playlist controls the order and timing of the playout of the Reels. 2 Normative
10、References The following standards contain provisions which, through reference in this text, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged t
11、o investigate the possibility of applying the most recent edition of the standards indicated below. World Wide Web Consortium (W3C) (2004, February 4). Extensible Markup Language (XML) 1.0 (Third Edition). World Wide Web Consortium (W3C) (2004, October 28). XML Schema Part 1: Structures (Second Edit
12、ion). World Wide Web Consortium (W3C) (2004, October 28). XML Schema Part 2: Datatypes (Second Edition). World Wide Web Consortium (W3C) (2002, February 12). XML-Signature Syntax and Processing. Internet Engineering Task Force (IETF) (1996, November). RFC 2045 Multipurpose Internet Mail Extensions (
13、MIME) Part One: Format of Internet Message Bodies. Internet Engineering Task Force (IETF) RFC2046 (November 1996) Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types. Internet Engineering Task Force (IETF) (1996, November). RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax.
14、Internet Engineering Task Force (IETF) (2001, September). RFC 3174 US Secure Hash Algorithm 1 (SHA-1). Internet Engineering Task Force (IETF) (1997, May) RFC 2141 URN Syntax. Internet Engineering Task Force (IETF) (2001, April) RFC 4051 Additional XML Security Uniform Resource Identifiers (URIs). In
15、ternet Engineering Task Force (IETF) (2005, July). RFC 4122 A Universally Unique Identifier (UUID) URN Namespace. SMPTE 429-7-2006 Page 4 of 30 pages 3 Overview A composition, depicted in Figure 1, is a self-contained representation of a single complete D-Cinema work, such as a motion picture, or a
16、trailer, or an advertisement, etc. It tangibly consists of a Composition Playlist file and one or more track files which contain the actual essence. Specifications of track file formats are beyond the scope of this document. A Composition Playlist (CPL) is a document which specifies the manner in wh
17、ich track files are rendered. A CPL represents a composition as an ordered sequence of Reels. Each Reel contains one or more Assets, which identify Track File segments to be reproduced in parallel. In other words, it specifies the assembly of track files both in parallel, e.g. sound with picture, an
18、d in sequence; e.g., Reel 2 after Reel 1. The Composition Playlist is typically created under editorial control in the mastering environment and is then included in the D-Cinema package distributed to exhibition. Composition PlaylistMain Picture Asset #1 Main Picture Asset #2 Main Picture Asset #3Ma
19、in Sound Asset #1 Main Sound Asset #2 Main Sound Asset #3Main Subtitle Asset #1 Main Subtitle Asset #2 Main Subtitle Asset #3Reel 1 Reel 2 Reel 3SubtitleTrackFile #1PictureTrackFile #1SoundTrack File#1PictureTrackFile #2PictureTrackFile #3SubtitleTrackFile #2SoundTrack File#2SubtitleTrackFile #3Soun
20、dTrack File#3Figure 1 Prototypical Composition Playlist The structures defined in this document are represented using the Extensible Markup Language (XML) XML 1.0, and specified using XML Schema XML Schema Part 1: Structures and XML Schema Part 2: Datatypes. This specification shall be associated wi
21、th a unique XML namespace name Namespaces in XML. The namespace name shall be the string value “http:/www.smpte-ra.org/schemas/429-7/2006/CPL“. This namespace name conveys both structural and semantic version information, and serves the purpose of a traditional version number field. Table 1 lists th
22、e XML namespace names used in this specification. Namespace names are represented as Uniform Resource Identifier (URI) values RFC 2396. These values shall be considered as simple strings, and applications should not attempt to resolve them as URLs. SMPTE 429-7-2006 Page 5 of 30 pages Table 1 XML Nam
23、espaces Qualifier URI cpl http:/www.smpte-ra.org/schemas/429-7/2006/CPL xs http:/www.w3.org/2001/XMLSchema ds http:/www.w3.org/2000/09/xmldsig The namespace qualifier values (namespace prefixes in XML jargon) used in this document (cpl, xs, ds), are not normative values. Implementations shall perfor
24、m correctly with any XML compliant namespace prefix value that is associated with a URI from table 1. Datatypes from other schemas that are used in this document will be prefixed with the appropriate namespace qualifier (e.g., xs:dateTime). See XML Schema Part 2: Datatypes and XML-Signature Syntax a
25、nd Processing for further information about these types. The MIME type IETF RFC 2046 for a document containing a single Composition Playlist element as its root shall be “text/xml“. 4 Terminology The following terms are used to describe the features of this standard. Clip: A contiguous set of Editab
26、le Units intended to be reproduced sequentially. Composition: A complete artistic or informational motion picture work, such as a feature, or a trailer, or an advertisement, etc. Editable Unit: The smallest temporal increment of access to Essence, e.g. a frame or a sample. Edit Rate: A number of Edi
27、table Units to be reproduced during a temporal interval having a duration of exactly one (1.0) second. Because Edit Rate values are not always integer values and sometimes require many digits of precision, Edit Rate values are expressed as a rational number (the ratio of two integers). Essence: The
28、sound, picture and data resources that make up a Composition. Native Duration: The total number of Editable Units in a Track File. Native Start Point: The first Editable Unit of a Track File. All Track Files are viewed by a Composition Playlist as a sequence of Editable Units numbered from 0 (zero).
29、 Consequently, the Editable Unit number of the Native Start Point of a Track File will always be 0 (zero). Native End Point: The last Editable Unit of a Track File. Playable Region: The set of Editable Units within a Track File that are intended to be reproduced as part of a Composition. A Track Fil
30、e may contain Editable Units before and/or after the Playable Region. Track File: A file containing a single Clip of simple Essence, such as sound, picture or subtitle essence. Sample Rate: The number of essence samples per second. Sample Rate values are expressed as a rational number (the ratio of
31、two integers). SMPTE 429-7-2006 Page 6 of 30 pages Frame Rate: The number of frames per second. Frame Rate values are expressed as a rational number (the ratio of two integers). Rational Number: A number value that is expressed as the ratio of two integers. This provides for the definition of precis
32、e values that are not subject to the inaccuracies of floating point representation. 5 Synchronization The Composition Playlist defines an idealized playback timeline. As depicted in Figure 2, the timeline consists of a sequence of contiguous Reels. A Reel defines a temporal segment of the compositio
33、n and consists of a set of single-essence Assets. start of Composition end of CompositionReel nReel 1Figure 2 Composition timeline An Asset identifies a segment of a Track File to be reproduced in parallel with the other Assets in the same Reel. The Assets Entry Point and Duration parameters define
34、the sequence of Editable Units within the Track File that is to be reproduced (the Playable Region). For a given time offset T from the start of the Reel, the corresponding time offset Tnwithin a Track File F shall be equal to (EntryPointF / EditRateF) + T. Editable Units across Track Files aligned
35、with the same time offset T are synchronized and shall be reproduced simultaneously. Figure 3 illustrates the timing relationship between Assets within a Reel. MainPicture AssetMainSound AssetMainSubtitle Assetstart of Reelend of ReelEntry PointT2T1T3TFigure 3 Timing relationships within a Reel At t
36、he start of a given Reel, playback of all Assets contained within the Reel shall start simultaneously at the Entry Point given for each respective Track File. The duration of a Reel shall be equal to the duration of the Reels MainPicture Asset, or the Asset with the shortest duration if the MainPict
37、ure Asset is not present. The Assets within each Reel shall be in editorial sync. In other words, the Composition Playlist timeline shall not compensate1 for any processing delay that may occur in the exhibition environment, such as the internal image processing delay in a projector, and shall refle
38、ct the same time relationships the editor intended the audience to observe in exhibition. 1Any compensation for essence delay through the exhibition equipment is to be applied in-theatre, not in the mastering process. Such compensation may be applied by the digital cinema playback system, the cinema
39、 sound processor, or some other device. SMPTE 429-7-2006 Page 7 of 30 pages 6 CompositionPlaylist Structure As depicted in Figure 4, a Composition Playlist shall be represented by a unique XML element, the CompositionPlaylist element. The Composition Playlist shall be encoded using the UTF-8 charact
40、er encoding XML 1.0. The CompositionPlaylist element is defined using XML Schema in Section 10. The CompositionPlaylist element is illustrated in Figure 4 and the individual elements that comprise the CompositionPlaylist element are defined in the remaining sub-sections. Figure 4 CompositionPlaylist
41、 structure (Dotted lines denote optional elements) 6.1 Id The Id element uniquely identifies the Composition Playlist for asset management purposes. It shall not uniquely identify the content represented by the composition see Section 6.9. It shall be encoded as a urn:uuid per RFC 4122. 6.2 Annotati
42、onText optional The AnnotationText element shall be a free-form, human-readable annotation describing the composition. It is meant strictly as a display hint to the user. The optional language attribute is an xs:language language SMPTE 429-7-2006 Page 8 of 30 pages code and indicates the language us
43、ed for the text. If the language attribute is not present, the default value en shall be used. 6.3 IconId optional The IconId element uniquely identifies an external image resource containing a picture icon illustrating the composition. The icon may be rendered, for instance, from a frame of the und
44、erlying content. The IconId element shall be encoded as a urn:uuid per RFC 4122. The mapping of UUID values to actual image resources is beyond the scope of this document. 6.4 IssueDate The IssueDate element shall be used to define the time and date at which the Composition Playlist was issued. It m
45、ay be displayed to the user. It shall be encoded as an xs:dateTime. 6.5 Issuer optional The Issuer element shall be a free-form, human-readable annotation that shall identify the entity that created the Composition Playlist. It is meant strictly for display to the user. The optional language attribu
46、te is an xs:language language code and indicates the text language of the content of the element. If the language attribute is not present, the default value en shall be used. 6.6 Creator optional The Creator element shall be a free-form, human-readable annotation that shall identify the application
47、 used to create the Composition Playlist. It is meant strictly for display to the user. The optional language attribute is an xs:language language code and indicates the text language of the content of the element. If the language attribute is not present, the default value en shall be used. 6.7 Con
48、tentTitleText The ContentTitleText element shall contain a human-readable title for the composition, e.g. The Jazz Singer. It is strictly meant as a display hint to the user. The optional language attribute is an xs:language language code and indicates the language of the content of the element. If
49、the language attribute is not present, the default value en shall be used. 6.8 ContentKind The ContentKind element defines the kind of material referred to by the Composition Playlist. It is meant to be both human and machine-readable. An optional scope attribute with default URI value http:/www.smpte-ra.org/schemas/429-7/2006/CPL#standard-content determines the permissible values of the element. If the scope attribute is absent, or set to it
