W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: [web-audio-api] It makes no sense to use EventListener for onaudioprocess if ScriptProcessorNode isn't EventTarget (#116)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:45 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/116/24244321@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=20764#6) by Robert O'Callahan (Mozilla) on W3C Bugzilla. Mon, 04 Mar 2013 22:40:05 GMT

(In reply to [comment #6](#issuecomment-24244316))
> 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 :-)

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/116#issuecomment-24244321
Received on Wednesday, 11 September 2013 14:34:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC