Reference WebCodecs registry for codec names. #299
Merged
Conversation
This file contains 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
tidoust
approved these changes
Sep 12, 2022
chrisn
approved these changes
Sep 12, 2022
|
This was discussed at TPAC 2022 [1] and there weren't any specific objections to going this route to name codecs. An issue was raised about how agents can use capabilities to request a lower-resolution stream, because they are not capable of displaying the stream at original/higher resolution. I'll file a separate issue for that; I don't think the exact details of how codecs are named in capabilities is directly related, since display and stream resolution are conveyed through separate, additional fields in the protocol. [1] https://www.w3.org/2022/09/16-webscreens-minutes.html#t07 |
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.
Addresses Issue #233: Use the same codec names as the media APIs.
Per the discussion in https://www.w3.org/2022/06/08-webscreens-minutes.html#t08, this updates the spec to refer explicitly to the WebCodecs registry to define codec strings for codecs in that registry.
It adds fallback language for additional codecs not defined in that registry, but if it is not sufficient to define the strings for additional codecs I would prefer to just remove the fallback language from this PR and address that separately.
Preview | Diff