W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

[Bug 17415] (JSWorkers): JavaScriptAudioNode processing in workers

From: <bugzilla@jessica.w3.org>
Date: Fri, 15 Jun 2012 21:49:07 +0000
To: public-audio@w3.org
Message-Id: <E1SfeOB-0007i8-CM@jessica.w3.org>

--- Comment #18 from Chris Rogers <crogers@google.com> 2012-06-15 21:49:06 UTC ---
(In reply to comment #17)
> (In reply to comment #16)
> > (In reply to comment #15)
> > > In any event, this does strike me as a show-stopper for having audio processing
> > > in workers.
> > 
> > As Philip pointed out: should read "this does NOT strike me as a show-stopper"
> > ;)
> All right, I'm running out of points to defend my case, especially since I
> don't have a horse of my own in the race. :) And if it's one or the other, I
> prefer the audio processing is done only in workers instead of the main thread
> (obviously), but I still think it'd be wise to have both.

I agree with Jussi.  Quite honestly it's a lot simpler for developers to have
access to the complete JS state while doing the processing.  If people are
willing to work with larger buffer sizes, then quite reasonable things can be
done in the main thread.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 15 June 2012 21:49:10 UTC

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