EAC3-JOC MIME type should not be taken as EAC3 on Pixel Device#3257
EAC3-JOC MIME type should not be taken as EAC3 on Pixel Device#3257ybai001 wants to merge 1 commit into
Conversation
Pixel devices integrate an EAC3 decoder, but it does not support EAC3-JOC stream decoding.
|
Thank you for reporting this issue! I think a better solution would be to isolate this "disabling" to the specific EAC3 decoder rather than the device? Would you be able to provide the decoder information? |
Hi, microkatz, Thanks for your reply. The point is the EAC3 decoder name is SAME for both Google and other OEMs (“c2.dolby.eac3.decoder”). For Google release, we have But for other OEMs, So I'm afraid that we cannot isolate this "disabling" to the specific EAC3 decoder. |
|
Thank you for the quick response and noted! I see the understanding of the product decision and I will work to submit your suggestion. |
Some Google Pixel devices integrate an EAC3 decoder that does not support EAC3-JOC stream decoding. Playing EAC3-JOC streams on these devices fails with a decoder error because ExoPlayer falls back to the alternative EAC3 MIME type. This change disables the fallback to standard EAC3 for EAC3-JOC streams on Google Pixel devices specifically, ensuring the player can select a supported audio track (such as AAC) instead. Issue: #3257 #cherrypick PiperOrigin-RevId: 941107127
2 participants
Pixel devices integrate an EAC3 decoder, but it does not support EAC3-JOC stream decoding. If there is a manifest file includes one AAC 2.0 track and one EAC3-JOC track.
Note: Pixel devices integrate EAC3 decoder but cannot handle EAC3-JOC stream. -- This is a product decision rather than technical limitation.