You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the player throws an exception, if an audio codec is not supported:
MediaError: MANIFEST_INCOMPATIBLE_CODECS_ERROR: No supported audio adaptations
This was done in purpose in our case because we assumed that people would want at least one playable video and audio tracks when there are some of them in the MPD (if the MPD has no audio AdaptationSet, we will play).
You would prefer just playing with no audio?
I guess we could add an option but I do not see the real use for this.
I think a half cake is better than no cake :)
Making this configurable would be a plus point - maybe not directly for consumers, but for developers. Like a growth hack.
We've discussed about that today and we're OK with adding options for that.
For now we're planning for two options, one for audio the other for video, where the idea would be to continue without that type of content if either none of its codecs are supported or if none of it is decipherable.
Exact details on the implementation and the option's name will be decided on as we work on it, we should hopefully begin working on it in the next few days.
Currently, the player throws an exception, if an audio codec is not supported:
MediaError: MANIFEST_INCOMPATIBLE_CODECS_ERROR: No supported audio adaptations
But the player might still play the videotrack, if supported. For example DashJS plays the videotrack - here is an example:
https://dash.akamaized.net/dash264/TestCasesDolby/2/Living_Room_1080p_20_96k_2997fps.mpd
The text was updated successfully, but these errors were encountered: