SMPTE ST 408M-2006 for Television Material Exchange Format (MXF) Operational Patterns 1c 2c and 3c.pdf

1、 Table of contents Foreword 1 Scope 2 Normative references 3 Glossary of acronyms, terms and data types 4 Introduction Annex A Specification of operational pattern 1c Annex B Specification of operational pattern 2c Annex C Specification of operational pattern 3c Anned D Bibliography Foreword SMPTE (

2、the Society of Motion Picture and Television Engineers) is an internationally-recognized standards developing 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, Rec

3、ommended 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 cooperates closely with other standards-developing organizations, including ISO, IEC and ITU. SMPTE Engineering

4、 Documents are drafted in accordance with the rules given in Part XIII of its Administrative Practices. This SMPTE document was prepared by the Technology Committee W25 on Metadata and Wrappers. 1 Scope This standard defines operational patterns 1c, 2c and 3c, as defined in SMPTE 377M section 7, for

5、 the exchange of MXF files that represent the following levels of file complexity: OP1c: A choice of 2 or more alternate material packages that play out selected tracks of either a single file package or two or more synchronized file packages, OP2c: A choice of 2 or more alternate material packages

6、that play out selected tracks of either a sequence of single file packages, or a sequence of two or more synchronized file packages, OP3c: A choice of 2 or more alternate material packages that play out selected portions of tracks (edit list) from one or more file packages each of which may be refer

7、enced and synchronized at any given position along the timeline. Page 1 of 16 pages SMPTE 408M-2006 SMPTE STANDARD for Television Material Exchange Format (MXF) Operational Patterns 1c, 2c and 3c Copyright 2006 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains,

8、NY 10601 (914) 761-1100 Approved April 5, 2006 SMPTE 408M-2006 Page 2 of 16 pages In each case, a top-level file package is linked to an essence container where each essence container may comprise either a single essence element or an interleave of multiple essence elements. Furthermore, in each cas

9、e, one or more of the essence containers may be internal or external to the file. This standard defines the operating restrictions, structural metadata objects and individual attributes that shall be applied to the MXF file format specification to achieve interoperability when exchanging an MXF file

10、 with these operational patterns. These operational patterns require the use of body partitions for internal essence containers. Subdivision of each essence container by using body partitions is optional. 2 Normative references The following standards contain provisions which, through reference in t

11、his 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 to investigate the possibility of applying the most recent edition of the standards

12、indicated below. SMPTE 377M-2004, Television Material Exchange Format (MXF) File Format Specification SMPTE 378M-2004, Television Material Exchange Format (MXF) Operational Pattern 1a (Single Item, Single Package) SMPTE 391M-2004, Television Material Exchange Format (MXF) Operational Pattern 1b (Sin

13、gle Item, Ganged Packages) SMPTE 392M-2004, Television Material Exchange Format (MXF) Operational Pattern 2a (Play-List Items, Single Package) SMPTE 393M-2004, Television Material Exchange Format (MXF) Operational Pattern 2b (Play-List Items, Ganged Packages) SMPTE 407M-2009, Television Material Exc

14、hange Format (MXF) Operational Patterns 3a and 3b 3 Glossary of acronyms, terms and data types The full glossary of acronyms, terms and data types used in the MXF specification is given in the MXF file format specification. It is not repeated here to avoid any divergence of meaning. Essence element:

15、 An essence container may contain many essence elements interleaved together. An essence element in this standard corresponds to a separable part of the interleave which is described by an MXF track, such as a picture track, a sound track, or a data track. 4 Introduction This standard defines MXF op

16、erational patterns 1c, 2c and 3c. SMPTE 377M defines the properties of the generalized operational patterns, and SMPTE EG 41 describes the concepts of operational patterns and the general conditions for audio-visual material exchange and interoperability. The introductory sections of these documents

17、 are not repeated here. 4.1 Operational pattern overview Generalized MXF operational patterns are defined as a combination of the two dimensions as defined in the MXF file format specification. These two dimensions are broadly illustrated in informative figure 1. SMPTE 408M-2006 Page 3 of 16 pages I

18、temComplexityGangedPackagesSingle Item Play-list Items Edit ItemsAlternatePackagesSinglePackagePackageComplexityMPFPMPFPsMPFPsMPFPs ANDMPFPsMPFPs ANDAny MP track from any FP trackEach MP SourceClip = entire FP seq.MP1MP2ORMP1MP2OREach MP SourcelCip = entire FPOnly 1 MP SourceClip = FP durationOnly 1

19、 MP SourcelCip = FP durationMP1MP2ORAny MP track from any FP track123abcFigure 1 (informative) Item and package complexity This standard defines three generalized operational patterns as follows: OP1c: A choice of 2 or more alternate material packages that play out selected tracks of either a single

20、 file package or two or more synchronized file packages. This is illustrated in the leftmost column and bottom row. The detailed specifications of operational pattern 1c are given in normative annex A. OP2c: A choice of 2 or more alternate material packages that play out selected tracks of either a

21、sequence of single file packages, or a sequence of two or more synchronized file packages. This is illustrated in the center column and bottom row. The detailed specifications of operational pattern 2c are given in normative annex B. OP3c: A choice of 2 or more alternate material packages that play

22、out selected portions of tracks (edit list) from one or more file packages each of which may be referenced and synchronized at any given position along the timeline. This is illustrated in the rightmost column and bottom row. The detailed specifications of operational pattern 3c are given in normati

23、ve annex C. None of these operational patterns apply constraints on the placement or use of descriptive metadata. general guidance on the use of descriptive metadata is given in SMPTE EG 42, SMPTE EG 41, and in SMPTE 380M. Implementers are encouraged to ensure descriptive metadata SourceClip referen

24、ces and descriptive metadata segments are kept consistent when essence references to file packages are modified. SMPTE 408M-2006 Page 4 of 16 pages Annex A (normative) Specification of operational pattern 1c A.1 MXF application A.1.1 Material and top-level file package relationships Other operationa

25、l pattern specifications (e.g., SMPTE 378M, SMPTE 391M, SMPTE 392M, and SMPTE 393M) illustrate the relationship between the top-level file packages and lower-level source packages (as file or physical packages). This relationship is not repeated in figure A.1 . Material Package 1Sequence (Picture)Tr

26、ack (Picture)1 or moreTop-LevelFilePackages(describingEssence)SourceClip (Picture)SourcePackageIDand SourceTrackIDof the MaterialPackageSourceClip definerespectively the FilePackage and theTrack containingthe essence.DurationFileDescriptorEssence ContainerData (for each Top-level File Package)Links

27、to:Links to SourcePackages (optional)Material Package 2Output selected from2 or more MaterialPackagesStartPositionSequence (Sound)Track (Sound)SourceClip (Sound-1)Sequence (Picture)Track (Picture)SourceClip (Picture)Sequence (Sound)Track (Sound)SourceClip (Sound-2)Sequence (Picture)Track (Picture)So

28、urceClip (Picture)Sequence (Sound-1)Track (Sound-1)SourceClip (Sound-1)StartPositionSequence (Sound-2)Track (Sound-2)SourceClip (Sound-2)Links to SourcePackages (optional)Links to SourcePackages (optional)FileDescriptorFileDescriptorDurationStartPositionDuration DurationFigure A.1 (informative) Outl

29、ine of operational pattern 1c A.1.2 General description Operational pattern 1c is an extension of operational patterns 1a and 1b where the output comprises a choice of two or more synchronized playable essence containers containing the audio-visual items. Operational pattern 1c is intended to meet t

30、he requirements of multi-lingual or multi-resolution applications where the alternate audio-visual sources are contained in two or more essence containers. In order to support this operational pattern, devices may require random access to the contents of the essence containers. One or more essence c

31、ontainers may be external to the MXF file. Guidance on the use of external essence containers is given in SMPTE EG 41. For MXF files used for program exchange, the essence containers should be internal to the file. The nature of this operational pattern allows the playout of the file to be changed b

32、y selecting the desired material package from a choice of multiple material packages. SMPTE 408M-2006 Page 5 of 16 pages A.1.2.1 Essence container requirements 1. The essence containers shall contain either a single essence element or an interleave of essence elements with a duration that equals the

33、 duration of the material package tracks. 2. Any track of a material package shall only create references to file package tracks of the same type. 3. All essence containers shall provide for the continuous decoding of contiguous essence elements. A.1.2.2 Example uses (informative) This operational p

34、attern allows the file playout to be versioned, typically providing for a choice of language track playout. Other uses might include a choice of picture options where the file might contain pictures of different resolutions or different aspect ratios. A.2 Operational pattern constraints A list of ge

35、neral constraints for this operational pattern is given in table A.1. Table A.1 General constraints for operational pattern 1c File Kind MXF “Operational Pattern” 1c: (Choice of output selected from one or more Essence Containers). Role Versioning of the file playout. Essence One or more Essence Con

36、tainers, Operational Pattern Qualifiers apply (see Table A.2). Material Packages 1 Number of Material Package SourceClips for each Essence Track 1 Top-level File Packages 1 or more. Zero or more Top-level File Packages may be external to the file. Number of Essence Container Types 1 or more Lower-le

37、vel Source Packages 0 or more. Essence described by Lower-level File Packages must be external to the file. Partition limits None Body Partitions Required when 1 Top-level File Packages. Note: when there are 1 Top-level File Packages, it is recommended that each Top-level File Package is contained i

38、n at least one Body Partition. Index Tables Optional, but recommended. Editing Support None. Streaming Support Conditional according to section A.3.4.2. A.3 Header metadata specification A.3.1 General The structural metadata sets and the normative universal label used to identify this operational pa

39、ttern are defined in SMPTE 377M with specific constraints and additions detailed below. SMPTE 408M-2006 Page 6 of 16 pages A.3.2 Constraints on the MXF packages 1. All constraints in SMPTE 391M section 6.2 apply unless overridden here. 2. There shall be two or more material packages. 3. All referenc

40、es to material package in SMPTE 391M section 6.2 apply to each material package. A.3.3 Universal label for operational pattern 1c The universal label value to define this operational pattern shall be as defined in table A.2. Table A.2 Value of the MXF operational pattern identification universal lab

41、el Byte No. Description Value (hex) 1-12 Defined in the MXF File Format Specification Operational Patterns Section 13 Operational Pattern: Item Complexity 01h 14 Operational Pattern: Package Complexity 03h 15 Operational Pattern: Qualifiers (application dependent) (see SMPTE 377M) 16 Reserved for fu

42、ture use 00h The meanings of the bytes in this label are specified in the operational pattern section of SMPTE 377M. Bytes 13 and 14 uniquely identify this operational pattern specification and byte 15 contains generic qualifiers which are defined in the MXF file format specification. A.3.4 Operatio

43、nal pattern qualifiers (Byte 15) This operational pattern shall support the qualifiers as specified in byte 15 of the operational pattern universal label. Each bit of byte 15 shall be correctly set, as defined by SMPTE 377M, to reflect the status of the essence containers. A.3.4.1 Essence container

44、location (Byte 15, bit 1) This section shall comply with SMPTE 378M section 6.4.1 and SMPTE 391M section 6.4.1. A.3.4.2 Interleaving of multiple essence tracks (Byte 15, bit 2) This section shall comply with SMPTE 378M section 6.4.2 and SMPTE 391M section 6.4.2. A.3.4.3 Number of essence tracks (Byt

45、e 15, bit 3) This section shall comply with SMPTE 378M section 6.4.3 and SMPTE 391M section 6.4.3. A.3.5 Minimum implementation (informative) All constraints given in the MXF file format specification apply unless specifically overridden or extended in this standard. The minimum implementation of op

46、erational pattern 1c is recommended to have the following sets in reference to the MXF file format specification. This section is a recommendation because the exact number of sets depends on the number of material packages and top-level file packages and the number of tracks in each package. 1 prefa

47、ce set, 1 or more identification sets, 1 content storage set, and 2 or more essence container data sets. Two or more material packages each including sets for: SMPTE 408M-2006 Page 7 of 16 pages the time code track each picture track as required by the essence container each sound track as required

48、by the essence container each data track as required by the essence container. One or more top-level file packages each including sets for: each picture track as required by the essence container each sound track as required by the essence container each data track as required by the essence contain

49、er each essence descriptor required to describe each essence track. The annexes of the MXF format specification give the properties of the sets which should be implemented. All required set properties should be supported by MXF encoders that comply with this operational pattern. A.4 MXF file interchange: Essence container issues A.4.1 Essence container identification Refer to SMPTE 391M, section 7.1. A.4.2 Essence container requirements in operational pattern 1c A.4.2.1 Number of essence elements There are no constraints on the nu