- From: <bugzilla@jessica.w3.org>
- Date: Tue, 04 Jun 2013 19:54:47 +0000
- To: public-media-capture@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22263
Martin Thomson <martin.thomson@skype.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |martin.thomson@skype.net
--- Comment #1 from Martin Thomson <martin.thomson@skype.net> ---
This is a difficult problem to address with strong normative language. For
local playback, it's a no-brainer, but once the tracks traverse a network it's
less clear-cut.
In some cases it's better to let audio/video desync rather than suffer
glitches, which tend to be more noticeable. Furthermore, some tests have
indicated that synchronization imposes delays that have a negative affect on
user perception. That is, the delays are worse than a little synchronization
drift.
Of course, applications that don't want synchronization could put
MediaStreamTracks in separate MediaStreams, but that allows for unconstrained
drift.
That leaves me with the conclusion that it should be up to browsers to
determine how they want to synchronize tracks.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
Received on Tuesday, 4 June 2013 19:54:48 UTC