- From: <bugzilla@jessica.w3.org>
- Date: Sat, 09 Mar 2013 08:56:44 +0000
- To: public-html-bugzilla@w3.org
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 #14 from Pierre Lemieux <pal@sandflow.com> ---
Thanks for the updated draft. Some initial comments below based on my attempts
at implementing the algorithm.
> and presentation timestamp lies within a coded frame already
> let overlapped frame be the coded frame in track buffer that contains presentation timestamp.
What do 'lie' and 'contain' mean? Specifically, do we mean ''overlapped frame'
-= 'existing frame N' such that 'existing frame N presentation timestamp' <=
presentation timestamp < 'existing frame N+1 presentation timestamp' ?
> If track buffer contains video coded frames and presentation
> timestamp is less than 1 microsecond beyond the presentation
> timestamp of overlapped frame, then remove overlapped frame
> and any coded frames that depend on it from track buffer.
What does 'beyond' mean?
Does 'overlapped frame' mean the coded frame whose presentation timestamp is
'presentation timestamp' +/- 1 us, or something else?
The note below the paragraph states "as long as it is within 1 microsecond".
> Let overlapped frame be the coded frame in track buffer that overlaps
> with new coded frame (ie. it contains presentation timestamp).
In contrast with coded video frames, the timestampOffset for coded audio frames
does not include a rounding tolerance, so ambiguities can occur. See below an
example using AC3 frames containing 44.1 kHz audio.
(5*1536)/44100 - 5*(1536)*(1/44100) = -2.7755575615628914e-17
> Round & update presentation timestamp and decode timestamp
'round' should be defined. Do we mean floor(x + 0.5)?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 9 March 2013 08:56:49 UTC