[Bug 19676] timestampOffset accuracy

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

--- Comment #4 from Aaron Colwell <acolwell@chromium.org> ---
(In reply to comment #3)
> In terms of providing an unambiguous splice point I am not sure that
> rounding is sufficient. I think the specification would also need to
> indicate where the splice will happen exactly, e.g. the closest "edit unit
> boundary/access unit boundary" in time or the next "edit unit
> boundary/access unit boundary" in time. A challenge is defining "edit unit
> boundary/access unit boundary" for each essence kind, e.g. audio sample,
> coded audio frame, video frame, GOP, etc... Makes sense?

I still don't understand why this is necessary. Please provide concrete
examples where rounding to the nearest microsecond would not be sufficient for
the common use cases on the web. It seems to me that microsecond precision is
sufficient for the typical audio sample rates, and frame rates that are
commonly used.

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

Received on Tuesday, 8 January 2013 15:53:14 UTC