Fix 4K, HDR, and Dolby Vision playback + refactor DeviceProfileManager#67
Merged
Fix 4K, HDR, and Dolby Vision playback + refactor DeviceProfileManager#67
Conversation
This file contains hidden or 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
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.
The device profile sent to the Jellyfin server had issues preventing 4K, HDR, and Dolby Vision content from playing correctly on Xbox. Max video width was hardcoded to 1920, HEVC was limited to "main" profile at level 4.0 (missing Main 10 for HDR10, and too low for 4K), H.264 was capped at level 4.2, AV1 and audio codecs were hardcoded as always-supported rather than queried, and Dolby Vision was never actually attempted for dual-layer formats.
Notable changes: