Add HEVC level 6.2 (186) device capability check #6376
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: imtsuki <[email protected]>
Cloudflare Pages deployment
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Add HEVC level 6.2 (186) device capability check in
browserDeviceProfile.js.Issues
Currently jellyfin-web tests device capabilities up to HEVC level 6.1. The author of #5586 mentioned that "6.2" is an "incorrect" level, but at least according to my research, 6.2 is a defined level in the standard itself (https://www.loc.gov/preservation/digital/formats/fdd/fdd000530.shtml):
Also, I encontered a HEVC video file recently that failed to do direct playing in the browser, due to its encoding level of 6.2.