This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26032 - Initialization segment received algorithm should explicitly set 'need random access point flag' true for all track buffers
Summary: Initialization segment received algorithm should explicitly set 'need random ...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: CR
Assignee: Aaron Colwell
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-10 23:47 UTC by Matt Wolenetz
Modified: 2014-06-20 15:53 UTC (History)
4 users (show)

See Also:

Attachments

Description Matt Wolenetz 2014-06-10 23:47:59 UTC 
Appending an init segment conceptually breaks the decode dependency chain, so coded frame processing should drop any non-random-access-point frames for a track buffer that may arrive after init segment received, unless a random access point buffer has been successfully processed for the track buffer since the last init segment was received.

This should be made explicit in the spec to improve interoperability.
Proposed text:
Add to 3.5.7 (Initialization Segment Received) Step 3 (If the first initialization segment flag is true...) a new substep 3.5.7.3.3.:
"Set the need random access point flag on all track buffers to true."
Comment 1 Aaron Colwell 2014-06-20 15:53:10 UTC 
Change committed.
https://dvcs.w3.org/hg/html-media/rev/f72c3041b7a0