SMPTE ST 429-5-2009 D-Cinema Packaging Timed Text Track File.pdf

1、 Copyright 2009 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved March 9, 2009 Table of Contents Page Foreword . 2 Intellectual Property 2 1 Scope 3 2 Conformance Notation 3 3 Normative References 3 4 Glossary of Acronyms and T

2、erms. 4 5 Overview (Informative). 4 6 Ancillary Resource Wrapping 6 6.1 Generic Stream Repetition 6 6.2 Indexing Generic Stream Data 6 7 Timed Text Track File Structure 7 7.1 Essence Encoding 7 7.2 Index Table . 7 7.3 Timed Text Resource Constraints 7 7.4 Header MetadataConstruction 7 7.5 Essence De

3、scriptors . 8 7.6 Header MetadataConstraints 8 7.6.1 General 8 8 Essence Encryption 9 9 Synchronization. 10 10 Random Access to Ancillary Resources (Informative). 10 Annex A Labels and Descriptor Sets (Normative) 11 A.1 UL Values . 11 A.2 TimedText Descriptor Set. 12 A.3 TimedText resource SubDescri

4、ptor Set . 12 Annex B Bibliography (Informative) . 14 Page 1 of 14 pages SMPTE 429-5-2009SMPTE STANDARD D-Cinema Packaging Timed Text Track File SMPTE 429-5-2009 Page 2 of 14 pages Foreword SMPTE (the Society of Motion Picture and Television Engineers) is an internationally-recognized standards deve

5、loping organization. Headquartered and incorporated in the United States of America, 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. Participat

6、ion in these Committees is open to all with a bona fide interest in their work. SMPTE 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.

7、 SMPTE Standard 429-5 was prepared by Technology Committee DC28. Intellectual Property SMPTE draws attention to the fact that it is claimed that compliance with this Standard may involve the use of one or more patents or other intellectual property rights (collectively, “IPR“). The Society takes no

8、position concerning the evidence, validity, or scope of this IPR. Each holder of claimed IPR has assured the Society that it is willing to License all IPR it owns, and any third party IPR it has the right to sublicense, that is essential to the implementation of this Standard to those (Members and n

9、on-Members alike) desiring to implement this Standard under reasonable terms and conditions, demonstrably free of discrimination. Each holder of claimed IPR has filed a statement to such effect with SMPTE. Information may be obtained from the Director, Standards or that a certain course of action is

10、 preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. The keywords “may“ and “need not“ indicate courses of action permissible within the limits of the document. The keyword “reserved” indicates a provision

11、 that is not defined at this time, shall not be used, and may be defined in the future. The keyword “forbidden” indicates “reserved” and in addition indicates that the provision will never be defined in the future. A conformant implementation according to this document is one that includes all manda

12、tory provisions (“shall“) and, if implemented, all recommended provisions (“should“) as described. A conformant implementation need not implement optional provisions (“may“) and need not implement them as described. Unless otherwise specified the order of precedence of the types of normative informa

13、tion in this document shall be as follows. Normative prose shall be the authoritative definition. Tables shall be next, followed by formal languages, then figures, and then any other language forms. 3 Normative References The following standards contain provisions which, through reference in this te

14、xt, 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 to investigate the possibility of applying the most recent edition of the standards indica

15、ted below. SMPTE 377M-2004 Television Material Exchange Format (MXF) File Format Specification SMPTE 379M-2004 Television Material Exchange Format (MXF) MXF Generic Container SMPTE 410-2008 Material Exchange Format Generic Stream Partition SMPTE 429-5-2009 Page 4 of 14 pages SMPTE 429-3-2007 D-Cinem

16、a Packaging Sound and Picture Track File SMPTE 429-6-2006 D-Cinema Packaging MXF Track File Essence Encryption Internet Engineering Task Force (IETF) (1996, November). RFC 2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies Internet Engineering Task Force (I

17、ETF) (1996, November). RFC 2396 Uniform Resource Identifiers (URI): Generic Syntax Internet Engineering Task Force (IETF) (2005, July). RFC 4122 A Universally Unique Identifier (UUID) URN Namespace ISO/IEC 10646:2003 Information Technology Universal Multiple-Octet Coded Character Set (UCS) 4 Glossar

18、y of Acronyms and Terms Note: See also the list of acronyms and terms in SMPTE 377M. Closed Caption: Timed-text intended for display on a device other than the theater screen. Composition: A complete artistic or informational motion picture work, such as a feature, a trailer, or an advertisement, et

19、c. MXF: Material Exchange Format (see SMPTE 377M). Open Caption: Timed-text intended for display on the theater screen, usually written in the same language as the sound essence. Reel: A unit of essence comprising all or part of a composition. Resource: An integral unit of data, such as an XML docum

20、ent, a font, or a sub-picture image. Sub-picture: An ancillary image intended for display over a larger main image. Subtitle: Timed-text intended for display on the theater screen, usually written in a language other than the language of the sound essence. Timed-text: Text intended for display over

21、a timeline, in synchronization with image and sound essence. URI: A Uniform Resource Identifier, defined by RFC 2396, is a text string which uniquely identifies a resource, such as an XML Schema. URI values often identify objects not accessible via a computer network. UUID: Universally Unique Identi

22、fier, defined by RFC 4122. XML: eXtensible Markup Language, an abstract syntax for structured text with metadata. 5 Overview (Informative) D-Cinema compositions may contain subtitles, closed-captions or other forms of textual information in addition to sound and picture essence. The display of textu

23、al information varies according to purpose, but the essence encoding can be generalized as a timed-text resource (an XML document) that provides content, position and timing information (i.e., essence plus metadata), plus optional ancillary resources such as fonts and sub-pictures. SMPTE 429-5-2009

24、Page 5 of 14 pages In some cases the essence is entirely contained in one or more sub-pictures. In these cases the timed-text resource contains only timing and position information. Like sound and picture essence for D-Cinema, timed-text essence is encoded reel-by-reel. Each reel of timed-text essen

25、ce consists of one XML timed-text resource plus optional supporting resources. To simplify the delivery of what may potentially be many dozens of files for a given reel, all of the resources for a reel are wrapped in a single MXF Timed Text Track File as described in this document. To protect agains

26、t disclosure of the essence data to unauthorized parties, the essence may be encrypted. The Timed Text Track File is based on the D-Cinema Sound and Picture Track File SMPTE 429-3 with the exceptions stated in Section 7 of this document, with the additional use of Generic Stream Partitions SMPTE 410

27、 as required to carry Ancillary Resource data. Figure 1 below illustrates a simple Timed Text Track File containing text-based subtitle essence. The timed-text resource is contained in the Track File along with a font resource used to render the characters when the text is reproduced on the theater

28、screen. Figure 1 Example Timed Text Track File Structure using a Font Figure 2 illustrates a more complex Timed Text Track File containing sub-picture-based subtitles. The timed-text resource is contained in the Track File along with a number of sub-picture resources. Figure 2 Example Timed Text Tra

29、ck File Structure using Sub-Picture SMPTE 429-5-2009 Page 6 of 14 pages 6 Ancillary Resource Wrapping Each Ancillary Resource in a Timed Text Track File shall be entirely contained within an MXF Generic Stream Partition per SMPTE 410. Each Generic Stream Partition in the file shall contain exactly o

30、ne Ancillary Resource. Each Generic Stream Partition shall have a distinct BodySID per SMPTE 410. The Generic Stream Partition shall consist of a Generic Stream Partition Pack immediately followed by a single KLV packet containing all of the resource data. KLV Fill packets shall not be permitted bet

31、ween the Generic Stream Partition Pack and the resource KLV. The actual format of the resource data is beyond the scope of this document. Consult the defining document for the Timed Text Resource for more information. Figure 3 Timed Text Resource Partition Structure The Ancillary Resource KLV packet

32、 shall be identified by the Default Generic Stream Data Element key (see Generic Stream Data Element coding in SMPTE 410). Data Arrangement bit 1 shall be zero (the KL pair shall not be considered an intrinsic part of the Ancillary Resource data) and bits 3 and 2 shall be one and zero, respectively

33、(the Generic Stream payload is a byte string). Wrapping Signaling bits 1-3 shall be zero (there are no internal access units). The following UL value gives the Default Generic Stream Data Element key, set per the above constraints: Table 1 Ancillary Resource Key (hexadecimal) 06.0e.2b.34 01.01.01.0c

34、 0d.01.05.05 01.00.00.00 6.1 Generic Stream Repetition Generic Stream Repetition, as defined by SMPTE 410, shall not be used. 6.2 Indexing Generic Stream Data Generic Stream Data shall not be indexed using SMPTE 377M Index Tables. Generic Stream Partitions shall be included in the RIP. See Section 1

35、0 for an informative description of locating an Ancillary Resource using its Resource ID as a lookup value. SMPTE 429-5-2009 Page 7 of 14 pages 7 Timed Text Track File Structure Timed Text Track Files shall conform to the provisions of SMPTE 429-3 with the following exceptions: a. The Timed-Text Res

36、ource shall be clip-wrapped, not frame-wrapped. b. The file shall contain more than three (3) partitions when Ancillary Resources are present. c. Essence Constraints shall be determined by this document. 7.1 Essence Encoding The essence container in the Timed Text Track File shall contain the Timed

37、Text Resource, an XML document that contains all of the timing and position information for the timed-text instances. A Timed Text Track File shall contain exactly one Timed Text Resource. The Timed Text Resource shall be clip wrapped as a single Data Element in a single Data Essence Item of a Gener

38、ic Container SMPTE 379M. The Timed Text Resource may refer to Ancillary Resources such as fonts and sub-pictures. All Ancillary Resources referenced by the Timed Text Resource shall be contained within the Timed Text Track File in separate Generic Stream Partitions (see Section 6 above). The Timed T

39、ext Track File shall not contain resources not referenced by the Timed Text Resource. 7.2 Index Table The Timed Text Track File shall contain in the Footer Partition a standard MXF Index Table as defined in SMPTE 377M and as constrained by SMPTE 429-3. The Index Table shall contain one entry, pointi

40、ng to the beginning of the single Data Element in the GC that holds the clip-wrapped Timed Text Resource. Because the Index Table will have only one entry, the table shall consist of a single IndexTableSegment. Within the segment, the DeltaEntryArray shall be empty and the value of EditUnitByteCount

41、 shall be 0 (zero). 7.3 Timed Text Resource Constraints While this specification does not define or reference a specific standard for the format of the Timed Text Resource, the following requirements must be met by the resource format for the resource to be used in a Timed Text Track File: 1. The re

42、source shall be encoded as an XML document. 2. The resource shall be identifiable using an embedded UUID value RFC 4122. 3. The resource shall refer to external resources using UUID values. For example, SMPTE 428-7 meets these requirements. 7.4 Header Metadata Construction The Timed Text Resource sh

43、all be described by a top-level File Package SMPTE 377M. The File Package shall contain one Data Essence Track (SMPTE 337M, B.14 and B.15) with a single Data Source Clip (SMPTE 377M, B.16). A single Material Package shall be present which shall contain one Data Essence Track with a single Data Sourc

44、e Clip referencing the File Package. If the Timed Text Track file contains encrypted essence (see Section 8 below), the header shall contain a Cryptographic Framework SMPTE 429-6. SMPTE 429-5-2009 Page 8 of 14 pages 7.5 Essence Descriptors The primary File Package in the header metadata shall have a

45、 strong reference to a TimedText Descriptor, which shall describe the Timed Text Resource (see Annex A.2). If the Timed Text Resource references one or more Ancillary Resources, the TimedText Descriptor shall contain the same number of strong references to TimedTextResource Descriptors (one for each

46、 Ancillary Resource, see Annex A.3). A TimedTextResource Descriptor contains the ResourceID and MIME Type RFC 2045 of the respective resource, and also the BodySID of the Generic Stream Partition containing the resource data. Figure 4 illustrates the metadata descriptors for a Timed Text Track File

47、containing a Timed Text Resource and two Ancillary Resources (a font and an image). Figure 4 Essence Descriptor example 7.6 Header Metadata Constraints 7.6.1 General The MXF Header Metadata of Timed Text Track Files shall conform to the section “Header Metadata Constraints” in SMPTE 429-3. SMPTE 429

48、-5-2009 Page 9 of 14 pages 8 Essence Encryption Timed Text Track Files may be encrypted. For this purpose, the Timed Text Resource shall be contained in an Encrypted Triplet per SMPTE 429-6. Ancillary Resources may also be encrypted. Because an Ancillary Resource is a component of the files essence

49、track, it shall be encrypted using the same Cryptographic Context used to encrypt the Timed Text Resource. Ancillary Resources shall not be encrypted unless the Timed Text Resource is also encrypted. When encrypting Ancillary Resources, the Generic Stream Data Element KLV packet in the Generic Stream Partition that contains the resource data shall be contained in an Encrypted Triplet per SMPTE 429-6. If the optional MIC value is present in the EKLV packet, the Seq