Skip to content

Recommend BlockGroup over SimpleBlock in WebM bytestream spec #1

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
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Recommend BlockGroup over SimpleBlock in WebM bytestream spec #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
621afcb
Recommend BlockGroup over SimpleBlock in WebM bytestream spec
tidoust Nov 24, 2020
56e0b22
Merge branch 'main' into note-simpleblock
chrisn Jul 22, 2024
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
19 changes: 19 additions & 0 deletions index.html
View file
Open in desktop
Copy link

Choose a reason for hiding this comment

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

Great 👍 work

Original file line number Diff line number Diff line change
Expand Up @@ -188,7 +188,26 @@ <h2>Media Segments</h2>
of a WebM [=initialization segment=] is encountered.</li>
</ol>

<div class="note">
Implementations MAY guess the coded frame presentation duration for
SimpleBlocks at the end of a <a def-id="webm-cluster"></a>.
Content providers are recommended to use BlockGroups with explicit
BlockDurations, instead of SimpleBlocks, for the last block for each
track in a <a def-id="webm-cluster"></a> to avoid variance in
buffering behavior across implementations.
</div>

<div class="note">
Implementations MAY introduce buffering latency for each SimpleBlock
encountered in a <a def-id="webm-cluster"></a>, since such a block's
coded frame presentation duration may not be determinable until the
next block is parsed. To avoid such latency, content providers are
recommended to use BlockGroups with explicit BlockDuration instead
of SimpleBlocks within a <a def-id="webm-cluster"></a>.
</div>

<p>The user agent MUST run the [=append error=] algorithm if any of the following conditions are not met:</p>

<ol>
<li>The Timecode element MUST appear before any Block &amp; SimpleBlock elements in a <a data-cite="WEBM#cluster">Cluster</a>.</li>
<li>Block &amp; SimpleBlock elements are in time increasing order consistent with [[WEBM]].</li>
Expand Down