DASH: parse transferCharacteristics
property to better detect hdr
#1212
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.
This PR allows to signal HDR AdaptationSets through the API - thanks to the
hdrInfo
property added in v3.26.0 (june 2021) - when anEssentialProperty
orSupplementalProperty
element with itsschemeIdUri
attribute is set to"urn:mpeg:mpegB:cicp:TransferCharacteristics"
.This is as specified in both the
6.2.5.1
and10.2.3.4
chapters of the DASH-IF IOP v4.3 the way that transfer function differences between AdaptationSets should be signaled when you have an MPD with both HDR and SDR Adaptation Sets.For now, only the "eotf" (the transfer function) is parsed (though we could also technically parse the
ColourPrimary
andMatrixCoefficients
parts of those chapters later).The goal is to allow an application to detect when multiple AdaptationSets are present which corresponds to HDR and which corresponds to SDR video content.