Skip to content
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

Deprecate the tracks API in favor of explicitly exposing languages and resolutions. #62

Open
matvp91 opened this issue Mar 27, 2020 · 0 comments

Comments

@matvp91
Copy link
Owner

matvp91 commented Mar 27, 2020

#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 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant