- From: <bugzilla@jessica.w3.org>
- Date: Mon, 04 Mar 2013 22:40:05 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20764
Robert O'Callahan (Mozilla) <roc@ocallahan.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |roc@ocallahan.org
--- Comment #7 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> ---
(In reply to comment #6)
> Exposing buffer size is also useful. The script node currently shares CPU
> with the main thread. Given this architecture, the amount of time available
> for audio can be different for different kinds of applications. A graphics
> rich application may not be able to guarantee enough callbacks just in time,
> in which case longer buffers would be desirable. An application that spends
> most of its time doing audio or being idle can use smaller buffer sizes to
> get lower latency. It is unnecessary to mandate an implementation to
> automatically determine the required buffering.
The problem with the author choosing the buffer size is that they almost
certainly won't be able to choose a size that will work on all kinds of
platforms and devices. The UA is best placed to do that. Anyway, there has been
discussion about this on the list, and further discussion should take place
there, definitely not in this bug :-)
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 4 March 2013 22:40:06 UTC