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.

Sign up for GitHub

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

Jump to bottom

Add new vp09 codec string to WebM Byte Stream Format - and update associated TR Note #180

Open
chcunningham opened this issue May 24, 2017 · 4 comments
Open

Add new vp09 codec string to WebM Byte Stream Format - and update associated TR Note #180

chcunningham opened this issue May 24, 2017 · 4 comments
Assignees
@plehegar
Milestone
V3

Comments

@chcunningham
Copy link

chcunningham commented May 24, 2017 •
edited
Loading

VP9 has a new codec string that adds details about the codec (profile, level, bit depth, color and eotf details, etc...). With these extra details, MediaSource.isTypeSupported(....) can be more accurate in assessing whether the UA can play the specific vp9 encoding. This is especially useful to know whether WCG and HDR content can be supported.

Find details for new codec string here. (Skip past the ISOBMFF boxes. The codec string is expected to be used with both mp4 and webm and its definition does not take a dependency on ISOBMFF.)

The WebM byte stream format explicitly supports the legacy "vp9" string in the "MIME-type parameters" table. This table can be updated to include support for the new string. Stand by for pull request from me or @wolenetz
@chcunningham
Copy link
Author

@kqyang, FYI, we probably need a similar issue for MP4. Will leave that to you.

The MP4 registry currently reads:

"MIME-types for this specification must conform to the rules outlined for "audio/mp4" and "video/mp4" in RFC 6381."

chcunningham added a commit to chcunningham/web-platform-tests that referenced this issue May 24, 2017
@chcunningham
Add MSE test for new vp09 codec string
10b3e02 
VP9 has a new codec string that adds details about the codec (profile,
level, bit depth, color and eotf details, etc...). With these extra
details, MediaSource.isTypeSupported(....) can be more accurate in
assessing whether the UA can play the specific vp9 encoding. This is
especially useful to know whether WCG and HDR content can be supported.

See "Codecs Parameter String" section here.
This codec string will be common to both webm and mp4. Its definition
does not take any container-specific dependencies.
http://www.webmproject.org/vp9/mp4/#codecs-parameter-string

Issue to update MSE WebM bytstream registry here
w3c/media-source#180

Relevant chromium anouncement and changes
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/a6rgcleYwzg
https://bugs.chromium.org/p/chromium/issues/detail?id=687627
@wolenetz
Copy link
Member

wolenetz commented Jun 2, 2017

@jdsmith3000 FYI I'll produce a PR shortly.

@wolenetz wolenetz mentioned this issue Jun 2, 2017
Closed
wolenetz added a commit that referenced this issue May 22, 2018
@wolenetz
Fix #180-timestamp: Regenerated webm bytestream html to update date (#…
50e4936 
…213)

PR#182 contained a date from last year, though it finally landed today.
This change updates that date using a regenerated-from-respec html.
@wolenetz
Copy link
Member

I'm reopening this to track getting the updated editor's draft (#182 + #213) webm-byte-stream-spec.html updated in the Note.
@plehegar please update the Note. Please also double-check the copyright date+text and SOTD references that the respec regeneration also updated in that specific html file.

@wolenetz wolenetz reopened this May 22, 2018
@wolenetz wolenetz changed the title Add new vp09 codec string to WebM Byte Stream Format Add new vp09 codec string to WebM Byte Stream Format - and update associated TR Note May 22, 2018
@wolenetz wolenetz mentioned this issue Sep 11, 2020
Open
@wolenetz wolenetz added the agenda Topic should be discussed in a group call label Sep 21, 2020
@wolenetz wolenetz added this to the V2 milestone Sep 21, 2020
@wolenetz
Copy link
Member

In scope of V2 to ensure this is/has been done.

@mwatson2 mwatson2 removed the agenda Topic should be discussed in a group call label Sep 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@plehegar plehegar

Labels
None yet
Projects
None yet
Milestone
V3
Development

No branches or pull requests
4 participants
@plehegar @mwatson2 @wolenetz @chcunningham