[Bug 28557] Coded frame removal algorithm may introduce discontinuity at end of current coded frame group

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

Matt Wolenetz <wolenetz@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Matt Wolenetz <wolenetz@google.com> ---
I'm thinking the most conservative/safest approach would be to inspect each
track buffer's "last decode timestamp" and "highest end timestamp", and if the
range removal algorithm removes any coded frames from a track buffer with
decode timestamp == that track's last decode timestamp, then run similar steps
as the coded frame processing algorithm does upon detecting an append
discontinuity:
1) If mode equals "segments": Set group end timestamp to presentation
timestamp.
2) If mode equals "sequence": Set group start timestamp equal to the group end
timestamp.
3) Unset the last decode timestamp on all track buffers.
4) Unset the last frame duration on all track buffers.
5) Unset the highest end timestamp on all track buffers.
6) Set the need random access point flag on all track buffers to true.

I'll try similar in a Chromium CL to see if this solves the immediate known
problem (as part of http://crbug.com/229412) and put together a spec pull
request containing updates once prototyped in Chromium.

In the meantime, I'm open, of course, to any discussion of alternatives.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 24 April 2015 19:58:12 UTC