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

Recommend BlockGroup over SimpleBlock in WebM bytestream spec #234

Closed
wants to merge 1 commit into from

Conversation

wolenetz
Copy link
Member

Problems with determining coded frame duration of SimpleBlock frames in WebM have not been alleviated by WebM muxer guidelines (e.g. to use BlockGroups with BlockDurations for the last block in each track in each cluster, to avoid having to guess the duration). Furthermore, low-latency buffering+decoding of webm motivates an additional note to use BlockGroups with explicit BlockDurations instead of SimpleGroups for all blocks in a cluster (so as to not have to wait until the next block for each track to compute the timestamp delta and use it as the duration).

This change adds a couple non-normative notes to the current editors draft of the MSE WebM byte stream format spec. Updating these bytestream specs can be done out-of-band relative to the main normative MSE spec, since these bytestream formats are non-normatively referenced from the bytestream format registry (and per previous repeated confirmations with W3C).

A helpful w3c-diff of this change versus the current editor's draft is available via https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fw3c.github.io%2Fmedia-source%2Fwebm-byte-stream-format.html&doc2=https%3A%2F%2Frawgit.com%2Fwolenetz%2Fmedia-source%2Fnote_simpleblock_webm%2Fwebm-byte-stream-format.html (while my branch is alive until after this PR lands in main w3c repo).

@plehegar Please confirm my understanding. Also, the WebM bytestream spec's editors draft was already updated since the most recent TR publishing of it. This will further update it. What is the process for getting the published (not just editor's draft) versions of these various bytestream format specs updated?

@jyavenard, @johnsim, @mwatson2, @jernoble, @chcunningham - I would appreciate your review of this pull request.

@tidoust
Copy link
Member

tidoust commented Aug 21, 2019

@plehegar Please confirm my understanding. Also, the WebM bytestream spec's editors draft was already updated since the most recent TR publishing of it. This will further update it. What is the process for getting the published (not just editor's draft) versions of these various bytestream format specs updated?

The Media WG is now responsible for the maintenance of these specs. To publish a new version, we need a group resolution. Per charter, that means we first need to issue a call for consensus.

(Note that we will also need to update the boilerplate in the Status of This Document section to point to the Media WG instead of the HTML Media Extensions WG)

@tidoust
Copy link
Member

tidoust commented Nov 24, 2020

The WebM Byte Stream Format spec has moved to a dedicated repo. I re-created that PR there, see w3c/mse-byte-stream-format-webm#1

Closing this PR without merging accordingly.

@tidoust tidoust closed this Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants