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
The tracks API is not aware of the differences in each rendition besides resolution & bandwidth. A track is not aware of the language, which would break quality selection (you'll end up selecting a different language all of sudden when manually scaling down / up an adaptive stream format).
This proposal would be about exposing languages and resolutions.
languages: [language: string] - Contains a list of languages as defined in the manifest.
resolutions: [resolution: IResolution] - Contains a list of resolutions, with the IResolution interface containing the following properties: width, height, bitrate. This list is kept in sync with the selected language.
Both language and resolution should be added to the extension responsible for state management.
Notes
Yet to figure out how to handle manifests with no multiple language tracks.
The text was updated successfully, but these errors were encountered:
#59 (comment) explains this a bit more in depth.
The
tracks
API is not aware of the differences in each rendition besides resolution & bandwidth. A track is not aware of the language, which would break quality selection (you'll end up selecting a different language all of sudden when manually scaling down / up an adaptive stream format).This proposal would be about exposing
languages
andresolutions
.languages
: [language: string] - Contains a list of languages as defined in the manifest.resolutions
: [resolution: IResolution] - Contains a list of resolutions, with theIResolution
interface containing the following properties:width
,height
,bitrate
. This list is kept in sync with the selected language.Both
language
andresolution
should be added to the extension responsible for state management.Notes
Yet to figure out how to handle manifests with no multiple language tracks.
The text was updated successfully, but these errors were encountered: