Recommend BlockGroup over SimpleBlock in WebM bytestream spec #1
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.
PR copied over from w3c/media-source#234
Original author:
+@wolenetz
@wolenetz notes in the PR:
[[
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.
@jyavenard, @johnsim, @mwatson2, @jernoble, @chcunningham - I would appreciate your review of this pull request.
]]
(I removed the part in that comment on the process to update the specs, resolved in the original PR)
Preview | Diff
Preview | Diff