-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[Feature Request] "Humanize" quality selector #8319
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
Comments
It's actually more complicated than just highest or lowest on YouTube, my understanding is that it is still auto but with different maximum resolutions e.g. data saver will pick 360p as long as your connection is not dreadful. Considering how many people complained when YouTube originally introduced that, I really don't think it should be the default in shaka-player, you can always write your own UI components to do that. |
The UI API allows you to write your own components, in this case I think this shouldn't be part of Shaka Player, sorry. |
Hi @avelad ! |
@joeyparrish Do you have any idea? |
@MarianoFacundoArch, I'd be happy to open it up if the current API/config is too restrictive to do what you want here. Do you have any suggestions? |
Hi @joeyparrish , auto: the current auto That'd be greatly enough! |
Uh oh!
There was an error while loading. Please reload this page.
Our current quality selector looks outdated compared to the new approaches platforms like YouTube are doing for their mobile versions.
I think YouTube has found a great, understandable way for most users. Maybe we can create an option for Shaka UI that enables us to select what kind of menu we want to use.
The new menu would be like this:
Basically, Auto does what we already have; Higher would go to the highest available quality, and Data saver to the lowest (maybe we can put a configurable value in the UI config, so it will go to the nearest to that value for each configured selection). Advanced opens our current selectorwhere you can specify specifically choose the quality.
I think this can be a great improvement!
The text was updated successfully, but these errors were encountered: