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:30:14 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/113/24244732@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#73) by Grant Galitz on W3C Bugzilla. Fri, 27 Jul 2012 16:56:18 GMT

(In reply to [comment #64](#issuecomment-24244681))
> (In reply to [comment #62](#issuecomment-24244667))
> > (In reply to [comment #59](#issuecomment-24244648))
> > > Would the following be a correct conclusion?:
> > > 
> > > - Audio processing in JavaScript should be done in workers.
> > […]
> > 
> > I think that is a reasonable conclusion, yes - although there may be objections
> > by e.g Philip who seemed to be quite adamant about it (See Comment #2). 
> 
> Nope, I think that JavaScript processing should be done in workers, and only
> workers.

Problem lies with the web worker being restricted from accessing all the APIs the main thread has access too. If I house everything in the worker, doing so will mess up some other components not audio related.

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

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