You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The prototype implementation of this feature in Chromium informed the initial draft spec. One of these considerations may need adjusting:
If a SourceBuffer was configured to expect appendBuffer (by addSourceBuffer or changeType), but appendEncodedChunks occurs instead (or vice-versa), the synchronous portions of the respective appendBuffer or appendEncodedChunks call do not detect this. Instead, the respective asynchronous "Buffer Append" or "Chunks Append" algorithms detect this and produce an append error, which produces a decode error.
Since this situation is rapidly detectable in the synchronous portion, and the consequence of delayed detection could cause the need to tear down the MSE attachment and restart it due to decode error, this issue tracks possibly updating the specification to do this rapid detection and non-fatal exception throwing or promise rejection, respectively, instead.
I've filed this to track likely upcoming work while this feature spec and implementation is stabilizing. Comments are most certainly welcome.
The text was updated successfully, but these errors were encountered:
wolenetz
changed the title
MSE-for-WebCodecs: disagreement of append format (WC vs BSF) is deferred and could produce decode err
MSE-for-WebCodecs: detection of mismatch of append format (WC vs BSF) is deferred and could produce decode err
Oct 1, 2021
wolenetz
added a commit
to wolenetz/media-source
that referenced
this issue
Oct 1, 2021
Fixes reference to the sourceBuffer in removeSourceBuffer()'s promise
abort step.
Updates the coded frame eviction algorithm's definition of |new data| to
possibly be EncodedChunks being appended.
Adds top-level steps for appendEncodedChunks().
Updates abort() and removeSourceBuffer() handling to conditionally
reject promise vs abort / updateend firing.
Updates reset parser state algorithm to clear any EncodedChunks from the
input configs and chunks slot, but leave any WebCodecs config there.
References w3c#301 for discussion from each of appendBuffer() and
appendEncodedChunks().
MSE-for-WebCodecs feature issue is #184.
The prototype implementation of this feature in Chromium informed the initial draft spec. One of these considerations may need adjusting:
If a SourceBuffer was configured to expect appendBuffer (by addSourceBuffer or changeType), but appendEncodedChunks occurs instead (or vice-versa), the synchronous portions of the respective appendBuffer or appendEncodedChunks call do not detect this. Instead, the respective asynchronous "Buffer Append" or "Chunks Append" algorithms detect this and produce an append error, which produces a decode error.
Since this situation is rapidly detectable in the synchronous portion, and the consequence of delayed detection could cause the need to tear down the MSE attachment and restart it due to decode error, this issue tracks possibly updating the specification to do this rapid detection and non-fatal exception throwing or promise rejection, respectively, instead.
I've filed this to track likely upcoming work while this feature spec and implementation is stabilizing. Comments are most certainly welcome.
The text was updated successfully, but these errors were encountered: