clarification about Dolby Atmos support in exoplayer DASH playout

[He12345678901]

Unfortunately we can't answer all questions. Unclear questions or questions with insufficient information may not get attention.

Before filing a question:

• Ask general Android development questions on Stack Overflow
• Search existing issues, including issues that are closed https://github.com/google/ExoPlayer/issues?q=is%3Aissue
• Consult our developer website (https://exoplayer.dev/) and Javadoc (https://exoplayer.dev/doc/reference/)

When filing a question:

Describe your question in detail.

In case your question refers to a problem you are seeing in your app:

• Output of running $ adb bugreport in the console

In case your question is related to a piece of media:

• URI to test content
• For protected content:
  • DRM scheme and license server URL
  • Authentication HTTP headers

Don't forget to check supported formats and devices (https://exoplayer.dev/supported-formats.html).

If there's something you don't want to post publicly, please submit the issue, then email the link/bug report to [email protected] using a subject in the format "Issue #1234", where #1234 is your issue number (we don't reply to emails).

[He12345678901]

Hi, I'd like to clarify please whether ExoPlayer (version 2.13.2) requires some specific Tags in the mpd manifest in order to play an asset/content with Dolby Atmos Audio (5.1) ? I have content encoded with the Atmos Identification Verified: EAC3 ATSC descriptor (tag 0xCC) and its mpd manifest containing the following adaptation set, tag value and codec - please review : </AdaptationSet> <AdaptationSet id="3" group="2" bitstreamSwitching="true" segmentAlignment="true" contentType="audio" mimeType="audio/mp4" lang="und"> <AudioChannelConfiguration schemeIdUri="tag:dolby.com,2014:dash:audio_channel_configuration:2011" value="f801"/> <ContentProtection schemeIdUri="urn:mpeg:dash:mp4protection:2011" value="cenc"/> </SegmentTemplate> <Representation id="dyHiAZ8." bandwidth="448000" codecs="ec-3" audioSamplingRate="48000"/>

are those manifest parameters sufficient for exoplayer to play and support Dolby Atmos (5.1) in DASH ? or there're any missing identifications in the manifest ? it'd be great to have a quick clarification on that - waiting yours update Thanks.

[He12345678901]

those are the manifest parameters to be reviewed:

[He12345678901]

Dolby_Atmos_Manifest_parameters.txt

please find in attached are those manifest parameters sufficient for exoplayer to play and support Dolby Atmos (5.1) in DASH ? or there're any missing identifications in the manifest ?

[He12345678901]

UHD_Dolby_Atmos_MPD.txt

and here's with the full manifest file please update thanks

[He12345678901]

Hi Any update please ?

[He12345678901]

Hi Any update please ?

[He12345678901]

hi any update please ? thanks

[christosts]

ExoPlayer 2.13.2 can load the DASH manifest shared. Whether the audio is played depends on the device. You can test the manifest parsing with the demo app on your own, just make sure to checkout version 2.13.1 from the github repo, or whatever version your app is using. We always recommend using the latest version if possible.

When it comes to actual playback, if for some reason, Dolby Atmos playback does not work, feel free to raise a new issue.

[He12345678901]

ok, fine But just to make sure, from your side the ExoPlayer 2.13.2 (regardless the device playing that audio) should support playing the Dolby Atmos signalized within this DASH manifest shared ? ExoPlayer needs some more specific identifiers in the manifest in order to play Dolby Atmos ? or what we have with this manifest is sufficient and OK ? thanks

[He12345678901]

Hi important to understand whether ExoPlayer 2.13.2 supports and needs this additional tag in manifest of "JOC" (Joint Object Coding) in order to decode the necessary meta data of Dolby Atmos ?

    <SupplementalProperty schemeIdUri="tag:dolby.com,2018:dash:EC3_ExtensionType:2018" value="JOC"/>
    <SupplementalProperty schemeIdUri="tag:dolby.com,2018:dash:EC3_ExtensionComplexityIndex:2018" value="16"/>

please update thanks

[christosts]

I can confirm that ExoPlayer 2.13.1 will parse the tag tag:dolby.com,2018:dash:EC3_ExtensionType:2018 and will detect that this stream is an Atmos stream (MIME type audio/eac3-joc) and not a Dolby Digital+ stream (MIME type audio/eac3).

Please see #6636.

The manifest that was attached above does not contain those tags, therefore it was detected as audio/eac3, but if the manifest has the tag tag:dolby.com,2018:dash:EC3_ExtensionType:2018 as pasted above, the track will be detected as eac3-joc. You can look at the Dolby DASH samples here.

As mentioned above, it will be faster if you verify yourself with the demo app at your desired version.

[He12345678901]

thanks for your response,

1. I guess that ExoPlayer 2.13.2 will also know how to parse this tag for Atmos stream "tag:dolby.com,2018:dash:EC3_ExtensionType:2018" , correct ?
2. about MIME Type - is it mandatory that dash manifest contains mimeType="audio/eac3-joc" ? or to have manifest with mimeType="audio/mp4" , codecs="ec-3" and those tag "tag:dolby.com,2018:dash:EC3_ExtensionType:2018" should be enough to parse an Atmos stream ? thanks

[He12345678901]

hi indication that I have now is that MIME type in manifest should Not change, but remain "audio/mp4", with codecs="ec-3" and those tag contained, "tag:dolby.com,2018💨EC3_ExtensionType:2018" would it be OK for ExoPlayer to parse the Atmos stream ? thanks

[christosts]

I guess that ExoPlayer 2.13.2 will also know how to parse this tag for Atmos stream "tag:dolby.com,2018_EC3_ExtensionType:2018" , correct ?

yes

about MIME Type - is it mandatory that dash manifest contains mimeType="audio/eac3-joc" ? or to have manifest with mimeType="audio/mp4" , codecs="ec-3" and those tag "tag:dolby.com,2018_EC3_ExtensionType:2018" should be enough to parse an Atmos stream ?

The second option