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:10 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/113/24244696@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415#65) by Marcus Geelnard (Opera) on W3C Bugzilla. Fri, 27 Jul 2012 14:02:51 GMT

(In reply to [comment #65](#issuecomment-24244688))
> (In reply to [comment #64](#issuecomment-24244681))
> > > (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.
> 
> I might have misunderstood Marcus' point then. 
> 
> Marcus, was your conclusion that it should be done in workers (and only there,
> hence a MUST) or that it should be done in workers (and could be done in mail
> thread at your own risks)?

Sorry for the vague language. What I meant was that JavaScript processing MUST be done in workers, and only in workers, never in the main thread.

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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC