[Bug 19676] timestampOffset accuracy

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

Pierre Lemieux <pal@sandflow.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #17 from Pierre Lemieux <pal@sandflow.com> ---
Thanks. Couple of follow-up issues:

> Let remove window timestamp equal overlapped frame presentation
> timestamp plus 1 microsecond.

This seems to apply only when there is overlap. If so, what about if the splice
is supposed to happen at the end of the existing frame buffer, i.e. the end of
the last frame of the existing frame buffer corresponds to the start of the
first frame of the added segment?

> Update presentation timestamp and decode timestamp to the nearest audio
> sample timestamp based on sample rate of the audio in overlapped frame.

Don't we need to adjust timestampOffset so that the following frames will align
as well?

>  then remove overlapped frame and any coded frames that depend on it from track buffer.

Same here, don't we need to adjust timestampOffset so that the presentation
time of following frames reflect the small offset as well?

>  There is no need for a rounding tolerance for audio.

What about if the splice is designed with no overlap, and the coded audio
frames are supposed to butt?

> that overlap presentation timestamp plus the splice duration of 5 milliseconds.

Larger than or equal?

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

Received on Monday, 18 March 2013 23:20:48 UTC