SMPTE RDD 41-2016 MDA D-Cinema Application.pdf

《SMPTE RDD 41-2016 MDA D-Cinema Application.pdf》由会员分享，可在线阅读，更多相关《SMPTE RDD 41-2016 MDA D-Cinema Application.pdf（6页珍藏版）》请在麦多课文档分享上搜索。

1、 Copyright 2016 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 3 Barker Avenue, White Plains, NY 10601 (914) 761-1100 Approved August 23, 2016 The attached document is a Registered Disclosure Document prepared by the proponent identified below. It has been examined by the appropriate SMPT

2、E Technology Committee and is believed to contain adequate information to satisfy the objectives defined in the Scope, and to be technically consistent. This document is NOT a Standard, Recommended Practice or Engineering Guideline, and does NOT imply a finding or representation of the Society. Ever

3、y attempt has been made to ensure that the information contained in this document is accurate. Errors in this document should be reported to the proponent identified below, with a copy to engsmpte.org. All other inquiries in respect of this document, including inquiries as to intellectual property r

4、equirements that may be attached to use of the disclosed technology, should be addressed to the proponent identified below. Proponent contact information: Scott Smyers DTS, Inc. 130 Knowles Drive, Suite B Los Gatos, CA 95032 Email: Page 1 of 6 pages SMPTE REGISTERED DISCLOSURE DOCUMENT MDA D-Cinema

5、 Application SMPTE RDD 41:2016 SMPTE RDD 41:2016 Page 2 of 6 pages Table of Contents Page 1 Scope 3 2 Normative Reference . 3 3 MDA Program Constraints 3 4 Bitstream Constraints . 4 5 MDA Reference Renderer Constraints . 4 6 Cinema Extensions . 5 SMPTE RDD 41:2016 Page 3 of 6 pages 1 Scope This docu

6、ment specifies an application of the MDA Program specification 1.03 and MDA Bitstream specification 1.03 for D-Cinema applications. 2 Normative Reference The following standard contains provisions which, through reference in this text, constitute provisions of this RDD. At the time of publication, t

7、he edition indicated was valid. All standards are subject to revision, and parties to agreements based on this RDD are encouraged to investigate the possibility of applying the most recent edition of the standard indicated below. SMPTE ST 428-12:2013, D-Cinema Distribution Master Common Audio Channe

8、ls and Soundfield Groups 3 MDA Program Constraints 3.1 Header.sampleRate The value of the Header.sampleRate property shall be as specified in MDA Program Specification. 3.2 RenderingException.targetConfiguration RenderingException.targetConfiguration MAY be a Soundfield Group as specified in SMPTE S

9、T 428-12 (see Table 1). 3.3 RenderingException.ChannelGain.channel RenderingException.ChannelGain.channel MAY be an Audio Channel as specified in SMPTE ST 428-12. RenderingException.ChannelGain.channel SHALL NOT be an LFE channel. 3.4 LFEFragment There SHALL be only one LFE object, i.e. only one ent

10、ity ID associated with LFEFragment instances. 3.5 Group An MDA Group SHALL only appears at top level (i.e. no recursion). 3.6 Switch Switch instance(s) SHALL NOT be present. 3.7 Object Fragment Position If present, ObjectFragment.position.radius SHALL be equal to 1. All other values SHALL be reserve

11、d. SMPTE RDD 41:2016 Page 4 of 6 pages 3.8 Object Fragment Coherent If present, ObjectFragment.coherent SHALL be equal to 1. 4 Bitstream Constraints 4.1 Frames Frames SHALL contain at least one Slice. 4.2 MonoSourceFragmentPacket.assetURI The format for MonoSourceFragmentPacket.assetURI for external

12、 assets (i.e. mainsound channels) SHALL be “urn:x-mda:mainsound-label:” + channelLabel, where channelLabel is a channel name as defined in SMPTE ST 428-12 (see also Table 2). 4.3 MonoSourceFragmentPacket.offset A mainsound channel is interpreted as a PCM wave file starting at the beginning of the MD

13、A Program. For external assets the MonoSourceFragmentPacket.assetOffset property SHALL be relative to the beginning of aforementioned wave file, and therefore relative to the beginning of the MDA Program. 5 MDA Reference Renderer Constraints 5.1 Configuration.soundFieldName A Configuration.soundname

14、Field field MAY be a Soundfield Group as specified in SMPTE ST 428-12 (see also Table 1). Local labels are not used in this version of the MDA Bitstream Specification. Table 1 Allowed soundfieldName Values URI Symbol Local Label urn:smpte:ul:060E2B34.0401010D.03020201.00000000 51 0, 0x01 urn:smpte:u

15、l:060E2B34.0401010D.03020202.00000000 71 0, 0x02 5.2 Configuration.speakers Configuration.speakersn MAY be an Audio Channel as specified in SMPTE ST 428-12 (see first column in Table 2). The second column in Table 2 lists the more commonly short names for the speakers. Local labels are not used for

16、this version of the specification. SMPTE RDD 41:2016 Page 5 of 6 pages Table 2 Allowed Speaker Names URI Symbol Local Label urn:smpte:ul:060E2B34.0401010D.03020101.00000000 L 0, 0x01 urn:smpte:ul:060E2B34.0401010D.03020102.00000000 R 0, 0x02 urn:smpte:ul:060E2B34.0401010D.03020103.00000000 C 0, 0x03

17、 urn:smpte:ul:060E2B34.0401010D.03020104.00000000 LFE 0, 0x04 urn:smpte:ul:060E2B34.0401010D.03020105.00000000 Ls 0, 0x05 urn:smpte:ul:060E2B34.0401010D.03020106.00000000 Rs 0, 0x06 urn:smpte:ul:060E2B34.0401010D.03020107.00000000 Lss 0, 0x07 urn:smpte:ul:060E2B34.0401010D.03020108.00000000 Rss 0, 0

18、x08 urn:smpte:ul:060E2B34.0401010D.03020109.00000000 Lrs 0, 0x09 urn:smpte:ul:060E2B34.0401010D.0302010A.00000000 Rrs 0, 0x0A 6 Cinema Extensions 6.1 BedTags A BedTagsExtension is attached to an Entity and signals to qualified asset extraction tools that the audio essence associated with this Entity

19、 is available for extraction to main sound. After extraction, the assetURI within the bitstream SHALL conform to Section 4.2. Note that Objects may be rendering excepted, without having an associated BedTags extension. Table 3 BedTags Extension struct mdaBedTagsExtension : Extension fName = kBedTags

20、ExtensionName; FixedArray) soundFields; The following constraints apply: 1. BedTags Extensions only apply to Object Fragments and LFE Fragments and are ignored for other Entities. 2. BedTags Extensions are static for the duration of the MDA Program: for every Entity with the same ID, a BedTags Exten

21、sion is either applied to all Entities with that ID or to none at all. SMPTE RDD 41:2016 Page 6 of 6 pages 3. The soundfields within a BedTags extension SHALL be one of as listed in SMPTE ST 428-12 (see Table 1. 4. An Object with a BedTags Extension for soundField=X, shall have a Channel Rendering E

22、xception for that same sound field X, and shall be addressing a single channel C only, static for the duration of the MDA Program. 5. BedTags Extension shall be complete and unique within an MDA Program: if a BedTags Extension for soundField=X is present in an MDA Program, then there exists precisely one Object Fragment / LFE Fragment ID for every channel within the sound field. Table 4 BedTags Extension Name Constant URI kBedTagsExtensionName /1.0/extension/bed-tags