W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2012

[Bug 19784] timestampOffset with multiplexed Media Segments

From: <bugzilla@jessica.w3.org>
Date: Tue, 30 Oct 2012 18:52:54 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-19784-2486-lzNbPkpJlq@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19784

--- Comment #2 from Pierre Lemieux <pal@sandflow.com> ---
Couple more data points in preparation for the discussion on Thursday.

> too optimistic about current-generation media pipelines ;)

I believe the suggested audio-video synchronization accuracy is supported in at
least Blu Ray and Ultraviolet, e.g. Section 2.4 of CFF Media Format at
http://www.uvvu.com/techspec-archive.php.

> In other words, I think that the extra control you're requesting wouldn't
> result in user-visible improvements to quality outside of a lab.

I believe that accurate synchronization (and hence splicing) is important for
video editing applications and branching scenarios, e.g. director's cut vs
theatrical cut versions. For one thing, the creative community at large has in
the past expressed strong interest in making sure that content is presented as
authored, no more no less. Furthermore, active content may be present at the
splice in these scenarios, and so an inaccurate splice may cause artifacts.

Perhaps more fundamentally, unless the API exposes the necessary information,
authoring and playback implementations do not even have the option to
consistently achieve accurate audio-video sync, and interoperate.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 30 October 2012 18:53:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 30 October 2012 18:53:00 GMT