- From: <bugzilla@jessica.w3.org>
- Date: Tue, 31 Mar 2015 15:16:50 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28379
Aaron Colwell <acolwell@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |acolwell@google.com
Target Milestone|--- |LC
--- Comment #1 from Aaron Colwell <acolwell@google.com> ---
This sounds like a quality of implementation issue to me. If the web
application has allowed the media element to run out of data, why would it
expect playback not to stop? How long of an underflow should the UA endure
before actually stopping playback?
You are right that MSE is biased more towards providing smooth playback instead
of low latency. The main reasons for that come from the ways the SourceBuffers
can be manipulated and because of constraints imposed by media decode
pipelines. It seems to me that if you are interested in low latency non-mutable
presentations you should be looking more towards WebRTC instead of MSE.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 31 March 2015 15:16:51 UTC