Skip HDR10+ metadata processing when Dolby Vision Profile 8 is detected#3085
Open
cgarst wants to merge 1 commit intoandroidx:releasefrom
Open
Skip HDR10+ metadata processing when Dolby Vision Profile 8 is detected#3085cgarst wants to merge 1 commit intoandroidx:releasefrom
cgarst wants to merge 1 commit intoandroidx:releasefrom
Conversation
1 task
|
OMG, @cgarst you are an absolute legend! |
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.
Fix Dolby Vision Profile 8 + HDR10+ playback issues
Summary
Fixes black-screen playback issues that occur when content contains both Dolby Vision Profile 8 and HDR10+ metadata.
Related Issues
Fixes #1895
Problem
MKV files containing Dolby Vision Profile 8.1 (dvhe.08) combined with HDR10+ metadata cause black-screen playback issues on many Android TV devices.
Affected Devices:
This issue has persisted for over two years and affects users across multiple streaming platforms that rely on ExoPlayer such as Kodi, Stremio, Plex, and Jellyfin.
Root Cause
The issue stems from conflicting HDR metadata being sent to the decoder:
Solution
Skip HDR10+ metadata processing when Dolby Vision Profile 8 is detected. This approach: