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:45 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/113/24244372@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#12) by Olli Pettay on W3C Bugzilla. Wed, 13 Jun 2012 18:14:29 GMT

(In reply to [comment #12](#issuecomment-24244364))
> I agree it should, but I don't think it will. What should an emulator/VM
> developer do? Render off main-thread as well? 
Probably

> MSP API would have been a perfect
> fit for that use case, given it's ability to process video as well... Analyzing
> the byte code of those existing games and other programs and isolating the
> audio code to another thread doesn't sound very feasible.
That is a limitation in the WebAudio API which should be fixed.

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

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