[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

--- Comment #2 from Matt Wolenetz <wolenetz@google.com> ---
In addition to remove() and coded frame eviction potentially removing frames
and causing discontinuity, the duration change algorithm (when it truncates
duration) may also introduce discontinuity by removing coded frames near the
end of the current coded frame group.

Also, a more general (I think equivalent), condition to trigger the
discontinuity logic (instead of "track buffer's last decode timestamp == DTS of
frame being removed") would be: "track buffer's last decode timestamp is within
the (inclusive) range [lowest DTS of a removed frame from that track buffer,
highest DTS of a removed frame from that track buffer]" in the coded frame
removal algorithm. In practice, this might make implementations that manage
continuous (in DTS sequence) track buffer coded frame ranges more efficient at
detecting discontinuities introduced by range removal algorithm.

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

Received on Friday, 24 April 2015 21:00:32 UTC