Skip to content

Update VP9 EncodedVideoChunk data and type definitions #967

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

Open
Djuffin wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update VP9 EncodedVideoChunk data and type definitions #967

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 12 additions & 5 deletions vp9_codec_registration.src.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@
<pre class='biblio'>
{
"VP9": {
"href": "https://storage.googleapis.com/downloads.webmproject.org/docs/vp9/vp9-bitstream-specification-v0.6-20160331-draft.pdf",
"href": "https://storage.googleapis.com/downloads.webmproject.org/docs/vp9/vp9-bitstream-specification-v0.7-20170222-draft.pdf",
"title": "VP9 Bitstream & Decoding Process Specification",
"publisher": "The WebM Project"
},
Expand All @@ -59,7 +59,14 @@
================================================

{{EncodedVideoChunk}} {{EncodedVideoChunk/[[internal data]]}} is expected to be
a frame as described in Section 6 of [[VP9]].
a single frame as described in Section 6 of [[VP9]], or a superframe as

@dalecurtis dalecurtis Oct 7, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd test if this works in Safari. I suspect it is expecting super-frames since we have to repack for VideoToolbox.

Chromium and Firefox probably accept both though. If we change this we should add a vp9 specific wpt to exercise both of these (if we don't already have one).

@youennf as FYI.

described in Annex B of [[VP9]].

Each {{EncodedVideoChunk}} is expected to contain exactly one shown frame (a

@marpan-max marpan-max Oct 7, 2026 •
edited
Loading

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"exactly one shown frame" -- are multiple spatial layers meant to be covered, which would have multiple show frames (sl0, sl1, sl2) in one chunk/superframe?

frame where `show_frame` is `1` or `show_existing_frame` is `1`, as defined in
Section 7.2 of [[VP9]]). Unshown frames (such as alternate reference frames,
where both `show_frame` and `show_existing_frame` are `0`) are expected to be
bundled together with a shown frame into a superframe.

VideoDecoderConfig description {#videodecoderconfig-description}
================================================================
Expand All @@ -70,9 +77,9 @@
================================================

If an {{EncodedVideoChunk}}'s {{EncodedVideoChunk/[[type]]}} is
{{EncodedVideoChunkType/key}}, then the {{EncodedVideoChunk}} is expected to
contain a frame with a `frame_type` of `KEY_FRAME` as defined in Section
7.2 of [[VP9]].
{{EncodedVideoChunkType/key}}, then the first frame in the
{{EncodedVideoChunk}} is expected to have `show_existing_frame` equal to `0` and
`frame_type` equal to `KEY_FRAME`, as defined in Section 7.2 of [[VP9]].

VideoEncoderEncodeOptions extensions {#videoencoderencodeoptions-extensions}
==============================================================
Expand Down
Loading