[Bug 19676] timestampOffset accuracy

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

--- Comment #6 from Aaron Colwell <acolwell@chromium.org> ---
(In reply to comment #5)
> > Please provide concrete examples where rounding
> > to the nearest microsecond would not be sufficient
> > for the common use cases on the web.
> 
> Splices between media streams do not occur on millisecond boundaries, but on
> editable unit boundaries (frame, sample, GOP, etc...), so the specification
> needs to specify which frame boundary the splice will happen.

My point is that I believe microsecond precision is sufficient to unambiguously
indicate which "editable unit boundary" is intended. Do you agree? If not can
you provide a concrete example where using microseconds would be problematic?

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

Received on Tuesday, 8 January 2013 16:51:58 UTC