[Bug 19676] timestampOffset accuracy

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

--- Comment #3 from Pierre Lemieux <pal@sandflow.com> ---
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?

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

Received on Tuesday, 8 January 2013 08:14:24 UTC