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
We propose to add functionality to have dash.js select the default audio AdaptationSet according to dash-if IOP v4.3, evaluating language/accessibility preferences. The feature is important for media delivery in open specification-based ecosystems and broadcasted content, e.g. ATSC-3 scenarios. HbbTV applications would also benefit from this functionality.
In these cases, one manifest file would be used to provide all the available combinations of language and accessibility (such as audio description), and dash.js be called upon to make the selection.
To keep backwards compatibility, this behavior would only be triggered if preferences are explicitly provided to dash.js.
This would mirror functionality already present on most deployed TV sets, and supply DASH-IF specification defined behavior.
The alternative is to leave the selection logic to be implemented in every application. This has the downside of getting incompatible behavior when matching languages or interpreting accessibility features.
The text was updated successfully, but these errors were encountered:
We propose to add functionality to have dash.js select the default audio AdaptationSet according to dash-if IOP v4.3, evaluating language/accessibility preferences. The feature is important for media delivery in open specification-based ecosystems and broadcasted content, e.g. ATSC-3 scenarios. HbbTV applications would also benefit from this functionality.
In these cases, one manifest file would be used to provide all the available combinations of language and accessibility (such as audio description), and dash.js be called upon to make the selection.
To keep backwards compatibility, this behavior would only be triggered if preferences are explicitly provided to dash.js.
This would mirror functionality already present on most deployed TV sets, and supply DASH-IF specification defined behavior.
The alternative is to leave the selection logic to be implemented in every application. This has the downside of getting incompatible behavior when matching languages or interpreting accessibility features.
The text was updated successfully, but these errors were encountered: