-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dolby <AudioChannelConfiguration value="F800"> results in an exception #688
Comments
I am experiencing the same problem. In which files do I need to make code changes? |
However, I still think Exoplayer sets very stiff boundaries for audio channels in its current implementation. |
Hi @dimitar71, Thanks for reporting! Could you please provide the full details of the sample media which will help me to test the change? The pasted one is an encrypted stream, and I think we'd need a drm license uri to test it. If you're unable to share test content publicly, please send them to dev.exoplayer@gmail.com using a subject in the format "Issue #688". Please also update this issue to indicate you’ve done this. |
Correction to the email, the one above is a legacy one: please send the test content to android-media-github@google.com using a subject in the format "Issue #688". |
issues/688 I sent an email no. On most phones, ac3 and eac3 do not produce sound. Video plays but no sound |
Hi @radyoof, Not sure if I understood your last comment correctly. So you said you sent an email? But I didn't find anything related in our email box. |
@tianyif @radyoof |
@tianyif -- please use this URL for testing the issue with Dolby Audio configuration representing the F800 scenario: --Update - on second thought not going to share that publicly as it's in the clear. Will send to suggested email with desired subject line. |
Issue: #688 PiperOrigin-RevId: 581908905
Issue: androidx/media#688 PiperOrigin-RevId: 581908905
Thanks @lsalvalaggio for the test media. The change is pushed :) |
Version
Media3 1.1.1
More version details
All Exoplayer 2.18.7+ versions have this problem.
Devices that reproduce the issue
Devices that do not reproduce the issue
Reproducible in the demo app?
Not tested
Reproduction steps
Find a
schemeIdUri="tag:dolby.com,2014:dash:audio_channel_configuration:2011"
manifest whichvalue
is not one of the supported ones inDashManifestParser.parseDolbyChannelConfiguration()
:"4000"
- 1 audio channel"a000"
- 2 audio channels"f801"
- 6 audio channels"fa01"
- 8 audio channelsFor example
value="F800"
in:<AudioChannelConfiguration schemeIdUri="tag:dolby.com,2014:dash:audio_channel_configuration:2011" value="F800"></AudioChannelConfiguration>
Expected result
A good approach would be parsing and returning a valid number, not
Format.NO_VALUE
.Actual result
This results in a 100% reproducible IllegalArgumentException from within Exoplayer.
This may need to be parsed properly, and return a safe audio channels value by default, e.g.
2
.Also, it is a good idea to be properly documented in the Exoplayer documentation/references.
For us,
F800
defines 5-channel audio.Based on https://ott.dolby.com/OnDelKits/DDP/Dolby_Digital_Plus_Online_Delivery_Kit_v1.5/Documentation/Content_Creation/SDM/help_files/topics/ddp_mpeg_dash_c_mpd_auchlconfig.html,
Alternative AudioChannelConfiguration scheme
section:This means any value, not just above 4 would be valid.
Also, in
DashManifestParser.parseDolbyChannelConfiguration()
, the coverage is 1, 2, 6 and 8 audio channels.It does not cover 5 and 7 audio channels for example.
One option would be checking range of values rather one value per channel configuration.
Media
Bug Report
adb bugreport
to android-media-github@google.com after filing this issue.The text was updated successfully, but these errors were encountered: