Interoperable Master Format – Application #2 · 6 Essence 6.1 Image Essence 6.1.1 Characteristics Image essence consists of image frames and each image frame consist of a rectangular

Copyright © 2007 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS3 Barker Avenue., White Plains, NY 10601(914) 761-1100

SMPTE 2067-20-201x

WD SMPTE STANDARD

Interoperable Master Format – Application #2

Page 1 of 24 pages

Version 0.5 (6/14/2012 20:09:00 a6/p6 :: application-2-20120305-v2(clean)-meeting ideas 6-14-12.doc)

Warning

This document is not a SMPTE Standard. It is distributed for review and comment. It is subject to change without notice and shall not be referred to as a SMPTE Standard. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. Distribution does not constitute publication.

Table of Contents

1 Introduction 2

2 Scope 2

3 Conformance Notation 3

4 Normative References 3

5 Overall 4

6 Essence 5

7 Track Files 10

8 Composition 16

9 IMF Master Package (IMP) 19

Annex A Bibliography 21

Annex B Sequence Elements 22

Annex C StereoImageTrackFileResourceType 23

Annex D Sparse Data Essence 24

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, SMPTE has members in over 80 countries on six continents. SMPTE’s Engineering Documents, including Standards,

Approved <TBD>

PROPOSED STRAWMAN – NOT A COMMITTEE DRAFT SMPTE 2067-20-201x

Recommended Practices, and Engineering Guidelines, are prepared by SMPTE’s 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 Documents are drafted in accordance with the rules given in Part XIII of its Administrative Practices. This SMPTE Engineering Document was prepared by Technology Committee 35PM-50.

EDITOR'S NOTE: Sections highlighted in fuchsia are candidate for inclusion in IMF Core Constraints.

EDITOR'S NOTE: URI values defined herein, e.g. http://www.smpte-ra.org/schemas/2065-20/xxxx, are temporary and will be replaced by their final values prior to publication, at which point this note will be removed.

1 Introduction

A single TV or movie title is transformed into multiple content versions (airline edits, special edition, languages…) These versions, which share common assets sourced from high-quality source masters, are ultimately made available to multiple distribution channels (Internet, optical media, broadcast...) across multiple territories and over the span of many months to over a year.

The IMF is a file-based framework that allows these high-quality versions, called Compositions, to be efficiently represented, managed, played back, processed and transformed on file-based systems. For example, it facilitates the generation of multiple outputs of the same Composition (through instructions contained in an Output Profile List define in other documents) to accommodate the specific needs of distribution channels. Since management and processing of Compositions are performed across multiple devices and service providers, interoperability is desirable.

Figure 1. The IMF framework allows the management and processing of multiple high-quality versions, called Compositions, of a finished content.

2 Scope

This document specifies Compositions for IMF Application #2. It is a specialization of the IMF Framework.

Application #2 is meant for studio applications where a TV or movie title is transformed into multiple content versions (airline edits, special edition, languages…) that are made available to multiple consumer distribution channels (Internet, optical media, broadcast...) across multiple territories and over the span of many months

Page 2 of 24 pages


to over a year. It uses HD image essence coded as a JPEG 2000 codestream and audio essence coded as linear PCM.

The transformation of Application #2 Compositions to the output formats appropriate for each distribution channel is specified in other documents.

3 Conformance Notation

Normative text is text that describes elements of the design that are indispensable or contains the conformance language keywords: "shall", "should", or "may". Informative text is text that is potentially helpful to the user, but not indispensable, and can be removed, changed, or added editorially without affecting interoperability. Informative text does not contain any conformance keywords.

All text in this document is, by default, normative, except: the Introduction, any section explicitly labeled as "Informative" or individual paragraphs that start with "Note:”

The keywords "shall" and "shall not" indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted.

The keywords, "should" and "should not" indicate that, among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is 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 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 mandatory 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 information 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.

4 Normative References

The following standards contain provisions which, through reference in this text, constitute provisions of this recommended practice. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this recommended practice are encouraged to investigate the possibility of applying the most recent edition of the standards indicated below.

[ST422] SMPTE 422M-2006, Material Exchange Format — Mapping JPEG 2000 Codestreams into the MXF Generic Container

[IMF CPL] ST2067-3:2012, Interoperable Master Format – Composition Playlist

Page 3 of 24 pages


[IMF Data Essence] ST2067-5:2012, Interoperable Master Format – Data Essence Specification

[IMF LPCM Audio] ST2067-YY:2012, Interoperable Master Format – LPCM Audio Essence

[IMF Digital Certificate] ST2067-ZZ:2012, Interoperable Master Format – Digital Certificates

[ISO/IEC 15444-1], 15444-1:2004/Amd 3:2010, Information Technology – JPEG 2000 Image Coding System. ISO/IEC (2010).

[ITU BT.601] ITU-R BT.601-5, Studio Encoding Parameters of Digital Television for Standard 4:3 and Wide-Screen 16:9 Aspect Ratios

[ITU-R BT.709] ITU-R BT.709-5 (04/02), Parameter Values for the HDTV Standards for Production and International Programme Exchange

[XML Schema] World Wide Web Consortium (W3C) (2004, October 28). XML Schema Part 1: Structures (Second Edition).

[XML] World Wide Web Consortium (W3C) (2004, February 4). Extensible Markup Language (XML) 1.0 (Third Edition).

[ST429-8] SMPTE ST429-8:2007 D-Cinema Packaging — Packing List

[ST429-5] SMPTE ST429-5:2009 D-Cinema Packaging — Timed Text Track File

[ST429-6] SMPTE ST429-6:2012 D-Cinema Packaging — MXF Track File Essence Encryption

[ST330] SMPTE 330M-2004, Television — Unique Material Identifier (UMID)

[ST377] SMPTE ST 377-1:2011 Material Exchange Format (MXF) - File Format Specification

[RP224] SMPTE RP 224, SMPTE Labels Registry

Internet Engineering Task Force (IETF) (July 2005). [RFC 4122] A Universally Unique Identifier (UUID) URN Namespace.

5 Overall

5.1 XML Schema and Namespace

This Application defines XML elements using the XML Schema language specified in [XML Schema]. Table 1 specifies the XML schema root element and target namespace.

Table 1. XML Schema root element definition.

<xs:schema targetNamespace="http://www.smpte-ra.org/schemas/2067-20/XXXX" xmlns:cpl="http://www.smpte-ra.org/schemas/2067-3/XXXX" xmlns:atwo="http://www.smpte-ra.org/schemas/2067-20/XXXX"

xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace=" http://www.smpte-ra.org/schemas/2067-3/XXXX" />

Page 4 of 24 pages


</xs:schema>

5.2 UUID Generation

UUID values used by this Application shall be generated as specified in [RFC 4122].

UUID values that identify assets or cryptographic information shall be generated using a truly-random or pseudo-random number source, and shall have a Version field value of ‘4’ (or 0100b) [RFC 4122].

NOTE: The ‘b’ suffix on this value indicates a binary encoding, most significant bit (MSB) first.

5.3 XML Character Encoding

XML documents shall be encoded using UTF-8, as specified in [XML].

6 Essence

6.1 Image Essence

6.1.1 Characteristics

Image essence consists of image frames and each image frame consist of a rectangular lattice of pixel elements.

As illustrated in Figure 1, the width and height of the frame are defined as the number of horizontal and vertical pixel elements, respectively.

Figure 2. Image Frame and Active Area.

6.1.1.1 Active Area

As illustrated in Figure 2, the active area shall consist of a subset of the pixels of the image frame contained within a rectangular lattice. The active area shall contain active picture content only but may contain letterboxing or side mattes as desired.

Page 5 of 24 pages


The width and height of the active area specify the integer number of horizontal and vertical pixel elements in the active area, respectively.

The horizontal and vertical offsets of the active area specify the offset of the active area from the left and top side, respectively, of the frame in number of pixel elements.

6.1.1.2 Image Frame Structure

Each image frame shall have either a progressive or interlaced structure.

6.1.1.2.1 Progressive Structure

An image frame with progressive structure shall consist of a complete image frame, scanned progressively left to right and from top to bottom.

6.1.1.2.2 Interlaced Structure

An image frame with interlaced structure shall consist of a pair of fields, a first field then a second field. The lines of each field shall have twice the vertical spatial sampling pitch of the frame. Lines in the second field shall be displaced vertically by the vertical sampling pitch and the line timing shall be delayed temporally by half the frame time from the lines in the first field.

The temporal order and relative line positions of the two fields are indicated by the Field Dominance and DisplayF2Offset items described in Section 7.2.2.1.

6.1.1.3 Frame Size

The height and width of the image frame may be any integer number within the limits specified in Table 2.

Image frames with interlaced structure shall have an even number of vertical pixels.

Table 2. Frame Size.

0 ≤ image frame width < 1920

0 ≤ image frame height < 1080

6.1.1.4 Frame Rate

The image frame rate for progressive and interlaced frame structures shall be one of the values listed in Table3.

The field rate, i.e. the number of image fields per second, shall be twice the frame rate.

Table 3. Frame Sampling Rates.

Page 6 of 24 pages


Progressive Structure Interlaced Structure

24 25

24000/1001 30

25 30000/1001

30

30000/1001

50

60

60000/1001

6.1.1.5 Color Components

Each image frame shall be sampled using either R’G’B’ or Y’C’BC’R color component triplets as specified below.

6.1.1.5.1 Bit Depth

Each component shall be represented by an integer in the set {0..2n – 1}, with n being one of the values of Table 4

Table 4. Component Bit Depth.

8

10

6.1.1.5.2 Colorimetry

Values of the R’G’B’ or Y’C’BC’R components shall be mapped to red, green and blue tristimulus values according to one of the colorimetry systems of Table 5.

Table 5. Colorimetry.

Page 7 of 24 pages


Colorimetry System

Applicable Component Triplets

Description

BT601.625 R’G’B’

Y’C’BC’R

Mapped as specified for 625-line systems in ITU BT.601

BT601.525 R’G’B’

Y’C’BC’R

Mapped as specified for 525-line systems in ITU BT.601

BT709.ST R’G’B’

Y’C’BC’R

Mapped as specified in ITU BT.709

RGBFS R’G’B’ Mapped as specified in ITU BT.709 with the equations governing the quantization of R'G'B' signals replaced by

D'R=INT( E'R · ( 2n - 1 ) )

D'G=INT( E'G · ( 2n - 1 ) )

D'B=INT( E'B · ( 2n - 1 ) )

where n is the bit depth.

NOTE: The mapping of images using the RGBFS system onto interfaces such as HD-SDI is defined in other specifications.

NOTE: In ITU BT.601 and ITU BT.709, the signals R', G', B', Y’, C’B and C’R are referred to as signals E'R, E'G, E'B, E'Y, E'CB and E'CR respectively, i.e. they correspond to gamma pre-corrected signals.

6.1.1.5.3 Sampling

In 4:4:4 R'G'B' or 4:4:4 Y’C’BC’R sampling, each component shall be sampled once at each image frame pixel.

In 4:2:2 Y’C’BC’R sampling, the Y' component shall be sampled at each pixel, but the CR and CB components shall be horizontally subsampled by a factor of two with respect to the Y component, co-sited with even-numbered Y’ samples.

Progressive and interlaced frame structures shall be sampled according to Table 6.

Table 6. Component Sampling.

Progressive Structure Interlaced Structure

4:4:4 R'G'B'

4:2:2 Y’C’BC’R

4:4:4 Y’C’BC’R

4:2:2 Y’C’BC’R

6.1.1.6 Stereoscopic and Monoscopic Image Essence

Monoscopic essence consists of a single sequence of image frames.

Stereoscopic essence consists of a sequence of pairs of image frames, a left eye frame and a right eye frame, for stereoscopic viewing. The two images of a pair shall be coincident in time.

Page 8 of 24 pages


Stereoscopic essence shall be used only with progressive frame structure.

6.1.2 Encoding

6.1.2.1 Profile

Each frame, in the case of progressive structure, or field, in the case of interlaced structure, shall be encoded as a single ISO-IEC 15444-1 Annex A codestream using one of the profiles of ISO/IEC 15444-1 Amendment 3 listed in Table 7.

Table 7. JPEG 2000 Profiles.

Broadcast Contribution Single Tile Profile Level 1





Broadcast Contribution Multi-tile Reversible Profile Level 6

Broadcast Contribution Multi-tile Reversible Profile Level 7

6.1.2.2 Component Ordering

In a codestream, color components shall be ordered as specified in Table 8.

Table 8. JPEG 2000 Color Component Ordering.

Component Index R'G'B' Y’C’BC’R

0 R' Y’

1 G' C’B

2 B' C’R

6.2 Audio Essence

The audio essence characteristics shall conform to [IMF LPCM Audio], with the following constraints applied.

6.2.1 Bits per Sample

The number of bits per audio essence sample shall be one of the values listed in Table 9.

Table 9. Audio Essence Bits Per Samples.

24

6.2.2 Sampling Rates

The audio essence shall be sampled at one of the rates listed in Table 9.

Table 10. Audio Sampling Rates.

Page 9 of 24 pages


48,000

96,000

6.3 Data Essence

The data essence shall conform to [IMF Data Essence].

7 Track Files

7.1 Overall

7.1.1 Format

Track Files shall conform to [IMF Essence Component].

7.1.2 Identification

The Package UID of a given Track File shall be a basic UMID per SMPTE 330M-2003, having a UUID value in the material number part and a material number generation method of UUID/UL. The Package UID value shall be further constrained as follows:

Byte 11 of the UL portion of the UMID shall be 0Fh (unidentified material type).

Byte 12 of the UL portion of the UMID shall be 20h (UUID/UL material number generation method and undefined instance number generation method).

The three bytes of the instance number shall be 0 (zero).

Package UID values generated in accordance with the normative provisions of this subsection will thus have the following contents in the first 16 bytes: 060a2b34h 01010105h 01010f20h 13000000h.

7.1.3 MIME Type

Track File shall use the MIME type application/mxf.

7.1.4 Encryption

Encrypted Track Files shall conform to the normative provisions of [ST429-6].

An encrypted Track File shall be encrypted with exactly one cryptographic key. The management, of cryptographic keys, including creation, distribution and storage, is outside the scope of this document.

7.2 Image Track Files

7.2.1 Essence

Image Track Files shall contain image essence conforming to Section 6.

7.2.2 Wrapping

Image Track Files shall conform to [ST422] and the following constraints shall apply:

the Essence Element Key and Essence Container UL shall indicate frame-wrapped essence;

the Edit Rate and Sample Rate shall be equal to the image frame rate; and

Page 10 of 24 pages


indexing shall be image frame-based.

In the case of progressive frame structure the codestream of each encoded image frame shall be wrapped in a single KLV contained in a single Content Package.

In the case of interlaced frame structure, the two codestreams of each of the encoded image fields shall be wrapped in temporal order in a single KLV contained in a single Content Package.

The Top-Level File Package of Image Track File shall reference

a CDCI Picture Essence Descriptor [ST377-1] if the image uses Y’C’BC’R color components; or

an RGBA Picture Essence Descriptor [ST377-1] if the image essence uses R'G'B' color components.

7.2.2.1 Generic Picture Essence Descriptor

The Generic Picture Essence Descriptor items shall be constrained as specified in Table 11.

Table 11. Generic Picture Essence Descriptor Items.

Generic Picture Essence Descriptor

Item

Constraints

Signal Standard Not used

Frame Layout Shall be present. See Section 7.2.2.1.2.

Stored Width See Section 7.2.2.1.1.

Stored Height See Section 7.2.2.1.1.

StoredF2Offset Shall not be present

Sampled Width Shall not be present

Sampled Height Shall not be present

SampledXOffset Shall not be present

SampledYOffset Shall not be present

DisplayHeight Shall be present and shall be equal to the image active area height

DisplayWidth Shall be present and shall be equal to the image active area width

DisplayXOffset Shall be present and shall be equal to the image active area horizontal offset

DisplayYOffset Shall be present and shall be equal to the image active area vertical offset

DisplayF2Offset Shall be present

Aspect Ratio Shall be present

Active Format Descriptor Shall not be present

Video Line Map Shall be present if interlaced structure is used and shall not be present if progressive structure is used

Alpha Transparency Shall not be present

Page 11 of 24 pages


Transfer Characteristic Shall be present. See Section 7.2.2.1.3.

Image Alignment Offset Shall not be present

Image Start Offset Shall not be present

Image End Offset Shall not be present

FieldDominance Shall be present.

Picture Essence Coding Shall be present. See Section 7.2.2.1.6.

Coding Equations Shall be present. See Section 7.2.2.1.4.

Color Primaries Shall be present. See Section 7.2.2.1.5.

7.2.2.1.1 Stored Width and Stored Height

The values of the Stored Width and Stored Height items shall be set according to the image frame structure, as specified in Table 12.

Table 12. Stored Width and Stored Height values.

Frame Structure

Progressive

Interlaced

Stored Width

Image Frame Width

Image Frame Width

Stored Height

Image Frame Height

Image Frame Height / 2

7.2.2.1.2 Frame Layout

The value of the Frame Layout item shall be equal to

00h (FULL_FRAME) if the image structure is progressive

01h (SEPARATE_FIELDS) if the image structure is interlaced.

7.2.2.1.3 Transfer Characteristic

The value of the Transfer Characteristic item shall be equal to 06.0E.2B.34.04.01.01.01.04.01.01.01.01.02.00.00 ["Identifies ITU-R BT.709 transfer characteristic (also used in SMPTE 170M, 274M and 296M)" in RP 224]

7.2.2.1.4 Coding EquationsThe value of the Coding Equations item shall be equal to

06.0E.2B.34.04.01.01.01.04.01.01.01.02.01.00.00 ["Identifies ITU BT-601 Coding Equations" in RP 224] if the BT601.625 or BT601.525 colorimetry systems are used, as defined in Section 6.1.1.5.2.

06.0E.2B.34.04.01.01.01.04.01.01.01.02.02.00.00 ["Identifies ITU BT-709 Coding Equations" in RP 224] if the BT709.ST or RGBFS colorimetry systems are used, as defined in Section 6.1.1.5.2.

Page 12 of 24 pages


7.2.2.1.5 Color PrimariesThe value of the Color Primaries item shall be equal to

06.0E.2B.34.04.01.01.06.04.01.01.01.03.01.00.00 ["Identifies SMPTE 170M color primaries and white point" in RP 224] if the BT601.525 colorimetry system is used as defined in Section 6.1.1.5.2.

06.0E.2B.34.04.01.01.06.04.01.01.01.03.02.00.00 ["Identifies ITU-R BT.470 PAL color primaries and white point (note: used in B, D, G, H, I, N/PAL and B, D, G, H, K, K1, L/SECAM systems)" in RP 224] if the BT601.625 colorimetry system is used as defined in Section 6.1.1.5.2.

06.0E.2B.34.04.01.01.06.04.01.01.01.03.03.00.00 ["Identifies ITU-R BT.709 color primaries and white point" in RP 224] if the BT709.ST or RGBFS colorimetry systems are used, as defined in Section 6.1.1.5.2.

7.2.2.1.6 Picture Essence Coding

The value of Picture Essence Coding item shall reflect JPEG 2000 profile used to encode the image essence (see Section 6) and shall be set to one of the Picture Essence Compression ULs [ST422] of Table 13.

Table 13. Specification of the Picture Essence Compression UL.

Byte No.

Description Value (hex)

Meaning

1-15 See SMPTE ST422

16 JPEG 2000 Codestream Restrictions

11h Broadcast Contribution Single Tile Profile Level 1 as specified in [ISO/IEC 15444-1]





16h Broadcast Contribution Multi-tile Reversible Profile Level 6 as specified in [ISO/IEC 15444-1]

17h Broadcast Contribution Multi-tile Reversible Profile Level 7 as specified in [ISO/IEC 15444-1]

7.2.2.2 RGBA Picture Essence Descriptor

The RGBA Picture Essence Descriptor items shall be constrained as specified in Table 14.

Table 14. RGBA Essence Descriptor items

Page 13 of 24 pages


RGBA Picture Essence Descriptor Item

Constraints

Component Max Ref Shall be present. See Section 7.2.2.2.1.

Component Min Ref Shall be present. See Section 7.2.2.2.1.

Alpha Max Ref Shall not be present.

Alpha Min Ref Shall not be present.

ScanningDirection Shall be present and shall be equal to 00h.

PixelLayout Shall not be present.

Palette Shall not be present.

PaletteLayout Shall not be present.

7.2.2.2.1 Component Max Ref and Component Min Ref

The values of the Component Max Ref and Component Min Ref items shall be set according to the component bit depth and colorimetry system used, as specified in Table 15.

Table 15. Component Max Ref and Component Min Ref values.

Colorimetry Systems

BT709.ST

BT601.625

BT601.525

RGBFS

Component Bit Depth

8 10 8 10

Component Min Ref

16 64 0 0

Component Max Ref

235 940 255 1023

7.2.2.3 CDCI Picture Essence Descriptor

The CDCI Picture Essence Descriptor items shall be constrained as specified in Table 16.

Table 16. CDCI Essence Descriptor items

Page 14 of 24 pages


CDCI Picture Essence Descriptor Item

Constraints

Component Depth Shall be present and shall be equal to the Component Bit Depth used (see Section 6.1.1.5.1)

Horizontal Subsampling Shall be present. See Section 7.2.2.3.1.

Vertical Subsampling Shall be present and shall be 01h

Color Siting Shall be 00h

ReversedByteOrder Shall not be present

PaddingBits Shall not be present

Alpha Sample Depth Shall not be present

Black Ref Level Shall be present. See Section 7.2.2.3.2.

White Ref level Shall be present. See Section 7.2.2.3.2.

Color Range Shall be present. See Section 7.2.2.3.2.

7.2.2.3.1 Horizontal Subsampling

The value of Horizontal Subsampling item shall be equal to

01h if 4:4:4 sampling is used per Section 6.1.1.5.3.

02h if 4:2:2 sampling is used per Section 6.1.1.5.3.

7.2.2.3.2 Black Ref Level, White Ref level and Color Range

The values of the Black Ref Level, White Ref level and Color Range items shall be set according to the component bit depth used, as specified in Table 17.

Table 17. Black Ref Level, White Ref level and Color Range values.

Component Bit Depth

8 10

Black Ref Level

16 64

White Ref level

235 940

Color Range

225 897

NOTE: The White Ref level item applies only to the Y' component and the Color Range item to the C’B and C’R components.

7.2.2.4 JPEG 2000 Picture Sub Descriptor

The Top-Level File Package of the Image Track File shall reference a JPEG 2000 Picture Sub Descriptor [ST422] as constrained by Table 16.

Page 15 of 24 pages


Table 18. JPEG 2000 Picture Subdescriptor items

JPEG 2000 Picture Subdescriptor Item

Constraints

Coding Style Shall be present

J2CLayout Shall be present. See Section 7.2.2.4.1.

7.2.2.4.1 J2CLayout

The value of the PixelLayout item shall be equal to

{ ‘R’, x, ‘G’, x, ‘B’, x, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 } if RGB sampling is used, where x is equal to 8 or 10 if 8-bit or 10-bit color components; or

{ ‘Y’, x, ‘U’, x, ‘V’, x, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 } if Y’C’BC’R sampling is used where x is equal to 8 or 10 if 8-bit or 10-bit color components are used per Section 6.1.1.5.1, respectively.

7.3 Audio Track Files

Audio Track File shall conform to [IMF LPCM Audio].

7.4 Data Essence Track Files

7.4.1.1 Essence

Data Essence Track Files shall contain essence conforming to Section 6.3.

7.4.1.2 Wrapping

Data Essence Track Files shall conform to ST 429-5.

8 Composition

8.1 Homogenous Essence

8.1.1 Image

Within a given a composition, the following shall remain constant:

all image essence characteristics specified in Section 6.1.1.

the codestream profile specified in Section 6.1.2.

8.1.2 Audio

Within a given a composition, the audio essence characteristics listed in Table 19 shall remain constant.

Table 19. Homogeneous Image Essence Characteristics.

Characteristic Definition

Bits per Sample See [IMF LPCM Audio]

Sampling Rate See [IMF LPCM Audio]

Page 16 of 24 pages


8.2 Virtual Tracks

The following specifies constraints on virtual tracks (see [IMF CPL]) present in a Composition.

8.2.1 Main Image Virtual Track

A Composition shall contain exactly one Main Image Virtual Track.

The Main Image Virtual Track shall consist of one or more MainImageSequence elements, as specified in Annex B.1.

If the underlying image essence is stereoscopic, as defined in Section 6.1.1.6, each MainImageSequence element shall contain Resource elements of type StereoImageTrackFileResourceType, as defined in Annex C, that reference two Track Files that conform to Section 7.2. .

If the underlying image essence is monoscopic, as defined in Section 6.1.1.6, all MainImageSequence elements shall contain Resource elements of type TrackFileResourceType that reference Track File that conform to Section 7.2.

The Edit Rate of the Resource elements shall be equal to the image frame rate of the underlying essence.

8.2.2 Audio Virtual Tracks

A Composition shall contain one or more Audio Virtual Tracks.

Each Audio Virtual Track shall consist of one or more MainAudioSequence elements, as specified in Annex B.2.

All Audio Essence Track Files referenced by a given Virtual Track shall have identical

audio channels

soundfield configurations, and

language.

Each MainAudioSequence element shall contain Resource elements of type TrackFileResourceType that reference Track File conforming to Section 7.3.

The Edit Rate of the Resource elements shall be equal to the audio sample rate of the underlying essence.

8.2.3 Data Essence Virtual Tracks

A Composition shall contain zero or more Data Essence Virtual Tracks.

Each Data Essence Virtual Track shall consist of one or more instances of one of the element specified in Annex B.3. The element shall match the sub-type of the data essence (see IMF Data Essence) contained in the Data Essence Virtual Track according to Table 20.

Page 17 of 24 pages


Table 20. Data Essence Sequence to Data Essence Sub-type mapping.

Sequence Element Data Essence Sub-type

SubtitlesSequence Subtitle

HearingImpairedCaptionsSequence Caption for Hearing Impaired

VisuallyImpairedTextSequence Text for Visual Impaired

CommentarySequence Commentary

KaraokeSequence Karaoke

The following characteristics shall be identical across all Data Essence Track Files referenced by a given Virtual Track

Standard

3D

Each Resource elements within Data Essence Virtual Track shall be of type TrackFileResourceType and shall reference a Track File that conform to Section 7.4.

Annex D provides guidance in the situation where there is no data essence associated with a particular Segment of the Composition.

8.3 Composition Edit Rate

The Composition Edit Rate shall be equal to the edit rate of the image essence frame sample rate referenced by the Main Image Virtual Track.

NOTE: The Composition Edit Rate does not constrain the rate at which implementations can reproduce a Composition. For instance, a Composition with an Edit Rate of 24/1 can be reproduced at 24,000/1,001 frames per second.

8.4 Track File Identification

The TrackFileId element of TrackFileResourceType shall be equal to the Package UID value of the Top-level File Package.

8.5 Segment Duration

The duration of a Segment shall be greater than or equal to the duration of one image essence frame referenced by the Main Image Virtual Track.

If the average number of audio samples per Composition Edit Unit is not an integer, the duration of each Segment shall be an integer multiples of 5/Composition Edit Rate.

8.6 Content Version

A Composition Playlist instance shall contain at least one ContentVersion element.

The Id element within each ContentVersion element may contain any valid URI. A few schemes are listed in Table 21 for illustration.

Page 18 of 24 pages


Table 21. Illustrative Content Version Id URI schemes (informative).

Basic UMID [SMPTE 2029]

ISAN [RFC 4246]

UUID [RFC 4122]

Info [RFC 4452]

8.7 EssenceDescriptor

The File Descriptor structure (including Sub Descriptors) referenced by the top-level File Package of the Track Files referenced by the Composition Playlist shall be mapped to an EssenceDescriptor element using SMPTE ST 434:2006 [or https://www.smpte.org/apps/org/workgroup/31fs-ahg-reg_xml/]. In particular, instances of the following Descriptors and Sub Descriptors shall be mapped if present:

CDCI Picture Essence Descriptor [ST377-1],

RGBA Picture Essence Descriptor [ST377-1],

JPEG 2000 Picture Essence Sub Descriptor [ST 422].

Wave Audio Essence Descriptor [ST 382].

MCA Label Descriptors [ST 377-4]

Timed Text Descriptor [ST 429-5], and

Timed Text Resource Descriptor [ST 429-5].

8.8 Digital Certificates

If the Signature element is present in a CPL instance, the digital certificate used shall conform to [IMF Digital Certificates].

9 IMF Master Package (IMP)

An Interoperable Master Package (IMP) shall consist of one Packing List, as specified in [ST429-8], and all the assets referenced therein.

A Packing List may reference assets which are referenced by other Packing Lists.

9.1 Asset Identification

The value of the Id element within each Asset element shall uniquely identify the asset and shall be unique in the Packing List instance.

The value of the Id element shall be extracted from the asset as specified in Table 22 for the asset defined therein.

Page 19 of 24 pages

https://www.smpte.org/apps/org/workgroup/31fs-ahg-reg_xml/


Table 22. Asset Identification.

Asset Identifier

Composition Playlist CompositionPlaylist/Id element value

Track File Package UID value of the Top-level File Package.

The Packing List may reference assets not listed in Table 22.

9.2 Digital Signature and Certs

When the Signature element is present, digital certificates in the signer’s certificate chain shall conform to the provisions of [IMF Digital Certificates].

9.3 Group ID

9.3.1 Complete IMP

A Complete IMP is an IMP containing only the complete set of assets comprising one or more compositions. The GroupId element shall not be present in the Packing List of a Complete IMP.

9.3.2 Partial IMP

A Partial IMP is an IMP containing one or more incomplete compositions (i.e., some assets needed to complete the composition are not present in the package.) Partial IMP shall be identified by the presence of the GroupId element in the Packing List. A Partial IMP should contain only related assets (i.e., partial sets of assets from two unrelated compositions should be listed in separate Packing Lists using different GroupId values.) When two or more Partial IMP contain related assets, the Packing Lists should have the same GroupId value.

Page 20 of 24 pages


Annex A Bibliography

[SMPTE ST 2029:2009] Uniform Resource Names for SMPTE Resources

Internet Engineering Task Force (IETF) (February 2006). [RFC 4246] International Standard Audiovisual Number (ISAN) URN Definition

Internet Engineering Task Force (IETF) (April 2006). [RFC 4452] The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces

Page 21 of 24 pages


Annex B Sequence Elements

B.1 Image

Table 23. MainImageSequence element schema definition,

<xs:element name="MainImageSequence" type="cpl:SequenceType"/>

B.2 Audio

Table 24. MainAudioSequence element schema definition,

<xs:element name="MainAudioSequence" type="cpl:SequenceType"/>

B.3 Data Essence

Table 25. Data Essence Sequence schema definition,

<xs:element name="SubtitlesSequence" type="cpl:SequenceType"/><xs:element name="HearingImpairedCaptionsSequence" type="cpl:SequenceType"/><xs:element name="VisuallyImpairedTextSequence" type="cpl:SequenceType"/><xs:element name="CommentarySequence" type="cpl:SequenceType"/><xs:element name="KaraokeSequence" type="cpl:SequenceType"/>

Page 22 of 24 pages


Annex C StereoImageTrackFileResourceType

The StereoImageTrackFileResourceType shall represent stereoscopic content consisting of two Track Files, each consisting of monoscopic essence. The Track Files referenced by the Left Eye and Right Eye elements shall contain views associated with the left and right eyes of the viewer.

<xs:complexType name="StereoImageTrackFileResourceType"> <xs:complexContent> <xs:extension base="cpl:BaseResourceType"> <xs:sequence> <xs:element name="LeftEye" type="cpl:TrackFileResourceType" /> <xs:element name="RightEye" type="cpl:TrackFileResourceType" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

The SourceDuration of an instance of StereoImageTrackFileResourceType shall be equal to the corresponding parameters contained in its LeftEye and RightEye elements.

Page 23 of 24 pages


Annex D Sparse Data Essence

In some situations, the data essence underlying a virtual track may be altogether absent from a given Segment, e.g. a Sequence within a Composition may not have any captions associated with it. In these situations, the Sequence associated with the virtual track within such a Segment should contain a single Resource and this Resource should be associated with an otherwise valid asset conveying the absence of essence for a duration equal to that of the Segment.

Figure 3 depicts an example where no captions are associated with two Segments of a Composition. Each of these two Segments contains a single Sequence that itself contains a single Resource. These two Resources reference the same Track File ID=AF..12, which is a valid Data Essence Track File (an MXF File that wraps an XML representation of the caption timeline) that does contains no actual caption (the timeline is empty).

Figure 3. Sparse Data Essence Essence.

Page 24 of 24 pages