[Bug 26032] New: Initialization segment received algorithm should explicitly set 'need random access point flag' true for all track buffers

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26032

            Bug ID: 26032
           Summary: Initialization segment received algorithm should
                    explicitly set 'need random access point flag' true
                    for all track buffers
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
          Assignee: adrianba@microsoft.com
          Reporter: wolenetz@google.com
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

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."

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Tuesday, 10 June 2014 23:48:01 UTC