Skip to content
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

Supplemental HDR Signaling #53

Open
technogeek00 opened this issue Aug 14, 2024 · 1 comment
Open

Supplemental HDR Signaling #53

technogeek00 opened this issue Aug 14, 2024 · 1 comment
Labels
use case consideration Use cases to consider formalizing

Comments

@technogeek00
Copy link
Collaborator

technogeek00 commented Aug 14, 2024

Use Case Description

Content providers want to signal in the manifest additional HDR metadata available within tracks

Working Notes

  • Dynamic HDR metadata typically addressing Dolby Vision and HDR10+ cases
  • HLS signaling details
    • VIDEO-RANGE attribute with values PQ and HLG provide base signaling of HDR
    • SUPPLEMENTAL-CODECS property provides enhancement layer specific codec strings
    • Example data available in documentation guide (repeated below in case of change)
Codec CODECS attribute SUPPLEMENTAL-CODECS attribute VIDEO-RANGE attribute
Dolby Vision 8.4 hvc1.2.4.L153.b0 dvh1.08.07/db4h HLG
Dolby Vision 8.1 hvc1.2.4.L150 dvh1.08.06/db1p PQ
Dolby Vision 10.4 av01.0.13M.10.0.112 dav1.10.09/db4h HLG
HDR10+ hvc1.2.20000000.L123.B0 hvc1.2.20000000.L123.B0/cdm4 PQ
AV1 w/ HDR10+ av01.0.05M.10.0.112 av01.0.05M.10.0.112/cdm4 PQ
  • DASH signaling details
    • Usages of SupplementalProperty within a referenced AdaptationSet or Representation
    • @schemeIdUri="http://dashif.org/metadata/hdr"
    • @value one of SMPTE2094-10, SMPTE2094-40, TS103433

Open Questions

  • Is there codec signaling in the DASH variation?

Scoring

To be filled out still

Question Answer
Does the feature relate to an industry streaming use-case? Yes
- What is the commonality of this case? Common
- Is this an established or emerging practice? Emerging
Does this feature have related mechanisms in both DASH and HLS? Yes
- What is the maturity of support in both specifications? HLS - Mature, DASH - Immature
- What is the maturity of implementation support for both specifications? HLS - Immature/Mature, DASH - Immature
- Are there known interoperability issues between specs? Potentially, but DASH signaling being updated to include supplemental codecs
- Has anyone implemented this interoperably? No
- Are there features missing in a specification with open proposals for it? HSL - No, DASH - Yes
Has the industry defined defacto mechanisms not present in both DASH and/or HLS? N/A
- Why was functionality defined outside of the main specifications? N/A
- Has the functionality been standardized elsewhere (DASH-IF, CTA, SVA)? No
- Is the functionality proprietary or openly developed? N/A
- Could the functionality be incorporated into specifications with evangelism? N/A
@technogeek00 technogeek00 added the use case consideration Use cases to consider formalizing label Aug 14, 2024
@technogeek00
Copy link
Collaborator Author

2024/08/14

  • Existing SCTE 214-1 Constraints document providing supplemental codec binding based on missing need
  • Additionally MPEG-DASH 6th Edition introducing formal supplemental codec signaling, may conflict with SCTE
  • DASH-IF signaling likely obsoleted by the 6th edition work, will not use

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
use case consideration Use cases to consider formalizing
Projects
None yet
Development

No branches or pull requests

1 participant