-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Bucketize resolution names in the UI #2090
Comments
This comment has been minimized.
This comment has been minimized.
|
Ah, the duplication has already been logged as a separate issue. Nice. Ignore this then |
No worries, @gregmsanderson. To see this issue in action, try playing something that doesn't have a 4:3 aspect ratio, like Sintel (which is 64:27). |
This was the duplicate of #2085 that has been fixed. |
I don't think that's what @joeyparrish meant for this issue. I think this issue was about taking videos that have similar resolutions and put them together. Instead of using the height followed by the letter 'p', we should provide pre-defined buckets to put the videos into (that is configurable). This will provide more "common" values for videos with slightly different sizes (e.g. we may not want to show an entry for |
Ah, yes, you're probably right. |
I'd actually like to see the complete list of resolutions along with their exact width/height values. Maybe shortened for common stuff (ie. 720p, 1080p.) |
Have you read the FAQ and checked for duplicate open issues?
Yes
Is your feature request related to a problem? Please describe.
The resolutions menu in the UI shows exact heights in pixels, rather than using well-known names for resolutions like 1080p and 4k.
Describe the solution you'd like
The exact width & height should be used to choose a specific name for the resolution. The mapping could be configurable if needed.
Describe alternatives you've considered
Continue using height + 'p'? Let apps override the naming entirely?
Additional context
Some of this could be done in a custom overflow menu item, but that's not very easy at the moment.
The text was updated successfully, but these errors were encountered: