D-BOX in SMPTE/DCI DCP

Size: px

Start display at page:

Download "D-BOX in SMPTE/DCI DCP"

Dina Holland
6 years ago
Views:

1 Page 1/7 A05 27/07/ Introduction To maintain phase-accurate synchronization with the motion picture sound track, the D-BOX Motion Code signal is carried within the main Sound Track File alongside other audio channels. This document specifies the carriage of a Motion Code signal in Compositions that conform to SMPTE ST 429-2, commonly referred to as SMPTE/DCI Compositions. It also includes guidelines for the output of the D-BOX Motion Code stream on the AES3 interface. 2 General 2.1 Composition The Composition shall conform to the recommendations at ISDCF Doc4. NOTE 1: Other methods of carrying Motion Code signal in SMPTE/DCI Compositions, such as those specified in Annex A.2 of SMPTE ST and in Section 5 of this document are not used in practice. NOTE 2: Due to current authoring tool limitations, MCA Sub-Descriptors can be absent from a Main Sound Track File that includes the Dolby ATMOS sync track. NOTE 3: ISDCF Doc4, which used to cover only Interop DCPs, now covers SMPTE/DCI DCPs. 2.2 Composition Playlist If the Composition Playlist includes the CompositionMetadataAsset element specified in SMPTE ST , D-BOX Technical Note applies. 2.3 Main Sound Track File The Main Sound Track File audio sampling rate shall be 48 khz. The D-BOX Motion Code signal shall be stored without modification in audio channel 13 of the Main Sound Track File. Unless used for other purposes, e.g. sync signal, audio channel 14 should contain audio silence or an identical copy of the samples found in audio channel 13. Any unused audio channels that are present in the Main Sound Track File should contain audio silence. Only the D-BOX Motion Code signal is currently used. If the Main Sound Track File includes MCA Sub-Descriptors, Section 3 applies. NOTE: The D-BOX MFX Controller is connected to the media block using both audio channels 13 and 14 (AES pair 7). The signal present on audio channel 14 is therefore not necessarily accessible to other devices in D-BOX-equipped screens.

2 Page 2/7 A05 27/07/ MXF Multichannel Audio (MCA) Framework If present, the items of the Audio Channel Label Subdescriptor associated with the D-BOX Motion Code Primary and signals shall be set according to Table 1. Table 1. MCA Framework Parameters. MCA Label Dictionary ID MCA Tag Name MCA Tag Symbol RFC 5646 Spoken Language 06.0E.2B D.0E E.2B D.0E D-BOX Motion Code D-BOX Motion Code DBOX DBOX2 Same as in Soundfield Group Label Sub Descriptor NOTE: The D-BOX Motion Code Primary and signals do not belong to a soundfield and therefore do not reference a Soundfield Group Label Subdescriptor. 4 Routing on an AES3 Interface The following recommends routing practice over the widely used AES3 interface (see EBU Tech 3250-E). It does not preclude use of the Motion Code signal over other interfaces. For maximum flexibility, implementations should allow users to route the Primary and Secondary Motion Code streams to arbitrary output AES3 audio channels. For continued compatibility with recommended Interop practice, D-BOX requires that the MFX Controller be connected to AES3 output channels 13 and 14 of the media block. As a result, the Motion Code streams A and B will generally be routed to AES3 output channels 13 and 14 respectively. To indicate the presence of a signal not suitable for conversion to an analogue audio signal, implementations may set, on AES3 output channels carrying D-BOX Motion Code streams, both (a) the Validity bit and (b) bit 1 of byte 0 of the Status word to the value 1. 5 Static Container D-BOX Channel Configurations This Section applies if the Main Sound Track File conforms to Annex A.1 of SMPTE ST but does not use Channel Configuration 4. NOTE: The mechanism specified in this Section is not in wide use and not recommended for new Compositions. The D-BOX Motion Code signal shall be stored without modification in the Main Sound Track File using one of the channel configurations defined in the following sections. These configurations are defined according to Section of SMPTE ST

3 Page 3/7 A05 27/07/2017 The Universal Label 1 (UL) associated with each configuration shall be used in the ChannelAssignment property of the WaveAudioEssence Descriptor of a Sound Track File to indicate the presence of the associated configuration. The Sound Track File shall carry the exact number of channels specified by each configuration. As specified in SMPTE ST Annex A.1, the container channels are numbered in sample packing order. The first sample shall be carried in container channel 1, the second in container channel 2 and so on. When the Motion Code is sufficient to carry the D-BOX Motion Code signal, both the Motion Code Primary and shall contain an identical copy of the D-BOX Motion Code signal. Implementations shall use the ChannelAssignment property to identify the sound channels present in the Sound Track File. 5.1 Configuration D1 Configuration D1 is defined in Table 2 and shall be associated with the UL defined in Table 3. It extends Configuration 1 Table 2. Channel Configuration D1. Container Channel 7 HI (per SMPTE 428-3) 8 VI-N (per SMPTE 428-3) 9 D-BOX Motion Code 10 D-BOX Motion Code Table 3. Channel Configuration D1 UL. 06.0E.2B D.0E The ULs used herein belong to a Class 13 register assigned to D-BOX. See

4 Page 4/7 A05 27/07/ Configuration D2 Configuration D2 is defined in Table 4 and shall be associated with the UL defined in Table 5. It extends Configuration 2 Table 4. Channel Configuration D2. Container Channel 7 Cs (per SMPTE 428-3) 8 Not used 9 HI (per SMPTE 428-3) 10 VI-N (per SMPTE 428-3) 11 D-BOX Motion Code 12 D-BOX Motion Code Table 5. Channel Configuration D2 UL. 06.0E.2B D.0E

5 Page 5/7 A05 27/07/ Configuration D3 Configuration D3 is defined in Table 6 and be associated with the UL defined in Table 7. It extends Configuration 3 Table 6. Channel Configuration D3. Container Channel 7 Lc (per SMPTE 428-3) 8 Rc (per SMPTE 428-3) 9 HI (per SMPTE 428-3) 10 VI-N (per SMPTE 428-3) 11 D-BOX Motion Code 12 D-BOX Motion Code Table 7. Channel Configuration D3 UL. 06.0E.2B D.0E

6 Page 6/7 A05 27/07/ Configuration D5 2 Configuration D5 is defined in Table 8 and shall be associated with the UL defined in Table 9. It extends Configuration 5 Table 8. Channel Configuration D5 (Digital Surround). Container Channel 7 Rls (per SMPTE 428-3) 8 Rrs (per SMPTE 428-3) 9 HI (per SMPTE 428-3) 10 VI-N (per SMPTE 428-3) 11 D-BOX Motion Code 12 D-BOX Motion Code Table 9. Channel Configuration D5 (Digital Surround) UL. 06.0E.2B D.0E No configuration D4 is defined at this time.

7 Page 7/7 A05 27/07/ References SMPTE ST 429-2:2013, D-Cinema Packaging DCP Operational Constraints SMPTE ST :2014, D-Cinema Packaging Additional Composition Metadata and Guidelines D-BOX Technical Note ( ISDCF Doc4, 16 Channel Audio Packaging Guide ( EBU Tech 3250-E, Specification of the Digital Audio Interface (The AES/EBU interface) ( 7 Change History Version A01 A02 Initial publication Corrected ULs per SMPTE ST400:2004 Highlights A03 Use "Lrs" instead of "Rls" in Configuration D5 for consistency with SMPTE ST and ST A04 A05 Added support for Configuration 4 DCPs and MXF Multichannel Audio Framework Deprecated support for Annex A.1 (other than Configuration 4) and A.2 of SMPTE ST Reflects update to ISDCF Doc4. This technical note is for informational purposes only. D-BOX Technologies, Inc. makes no representations or warranties, express or implied, regarding the information contained herein. D-BOX and the D-BOX logo are registered trademarks of D-BOX Technologies, Inc. All other trademarks remain the property of their respective owners D-BOX Technologies, Inc. All rights reserved.

Configuration. -- Rrs Right rear surround. 13 Motion Data Synchronous signal (currently used. 14 Sync Signal Used for external sync (e.g.

Configuration. -- Rrs Right rear surround. 13 Motion Data Synchronous signal (currently used. 14 Sync Signal Used for external sync (e.g. ISDCF Doc4-16 Channel Audio Packaging Guide 20170629 General The audio channel ordering shown in the Table below is recommended for use in all Compositions, whether Interop or SMPTE. Since routing is not