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

Re: [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:43 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/113/24244300@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#2) by Chris Rogers on W3C Bugzilla. Fri, 08 Jun 2012 19:19:15 GMT

I completely agree that workers are a better approach for lower-latency, smaller buffer sizes.  But there is a cost to the developer to being required to use a web worker because the JavaScript state is completely isolated from the main JS thread.  Thus it will require more complex code, and some applications might not even be practical.

Some developers have expressed concerns that JavaScriptAudioNode *only* happens in workers.

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

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