![]() I copy the code that I used to parse the OAMD object count from the e-ac-3 files. Unfortunately my vacation is over and so is my spare time to deal with this in detail. Quick look around in the Arlassian Sourcetree app offered only external diff and I’d need to do it manually file-by-file. PS is there an easy way to make a diff of my code changes to your git master? Eg if MI counts 11 objects, cookie has 0x0c, if 13 objects then 0x0e and if 15 objects then 0x10.Īlso tested: having byte 5 !=0, byte 6 =0 or byte 7 =0 makes tvOS think the stream is just E-AC-3 and play it in PCM either 5.1 or 7.1 (depending on dependent substream and channel location definition in dec3). The value here is always 1 larger than MI display. ![]() (See ETSI TS 102 366 for details) and determine object count from JOC payload in it (see ETSI TS 103 420).īytes 0-4 - standard meaning (TS 102 366)īyte 5 needs to be 0 - no dependent substreamsīyte 6 needs to be 1 - i have named it Atmos version (current atmos version is defined as 1.0 see the ETSI Revision to RDD 29:2014 Dolby Atmos® Bitstream Specificationīyte 7 seems to indicate object count - deductively observed from mp4 demo/test clips from Dolby Labs and comparing to MediaInfo object count display. ![]() I already can see that they indeed read the EMDF section in DD+ stream So the startingpoint is hidden here somewhere (am just studying the code) Luckily enough, they are also open source. It seems that the MediaInfo app does it best at the moment.
0 Comments
Leave a Reply. |