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

Media Capabilities and HDR Dynamic Metadata #213

Open
pauljhearty opened this issue Feb 6, 2024 · 4 comments
Open

Media Capabilities and HDR Dynamic Metadata #213

pauljhearty opened this issue Feb 6, 2024 · 4 comments

Comments

@pauljhearty
Copy link

Please confirm that there is no assumption that only one form of HDR Dynamic Metadata can exist in media sources. It is possible, and anticipated in multiple standards, that a source may support HDR10 alone or HDR10 with one or both of ST2094-10 and ST2094-40.

@jernoble
Copy link
Contributor

Hello Paul,

The intent of the API is to query for whether the specific configuration is supported by the platform. The answers to those capabilities checks are not intended to be exclusive; in other words, a successful query for "smpteSt2094-10" does not imply that an otherwise identical query for "smpteSt2094-40" would fail.

However, that's based on an assumption that, for a piece of content with (e.g.) both "smpteSt2094-10" and "smpteSt2094-40" metadata in-band, a user agent can choose to use one metadata type or the other. If instead, these metadata types are combinatorial (i.o.w., if both sets of metadata are used during decoding and/or presentation) then the Media Capabilities API isn't expressive enough to answer a query about whether that combination of metadata are supported.

So hopefully you can help us answer this question: when multiple types of metadata are included in a stream, are those metadata types exclusive, or are they used in combination with each other?

@pauljhearty
Copy link
Author

pauljhearty commented Feb 14, 2024 via email

@jernoble
Copy link
Contributor

The expectation is that a single HDR program could have one or more independent HDR dynamic metadata types delivered in-band. A device could support 0, 1 or more dynamic metadata types. In the instance that the device supports more than one dynamic metadata type, a selection could be made by the operative application or by user preference.

Okay, by "independent HDR dynamic metadata types", then I believe that answers your original question:

Please confirm that there is no assumption that only one form of HDR Dynamic Metadata can exist in media sources.

Confirmed. Querying for one dynamic metadata type or another is fully supported, and there is no assumption that multiple independent metadata types cannot be contained within the same media source.

@chrisn
Copy link
Member

chrisn commented Feb 14, 2024

In the instance that the device supports more than one dynamic metadata type, a selection could be made by the operative application or by user preference.

In this case, the browser would select which one to use. I don't think there's a facility for a web app to request use of one metadata type over another within the same content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants