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

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

From: <bugzilla@jessica.w3.org>
Date: Sun, 08 Jul 2012 06:47:00 +0000
Message-Id: <E1SnlGm-000414-6z@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #34 from Grant Galitz <grantgalitz@gmail.com> 2012-07-08 06:46:59 UTC ---
> For use-cases such as "run an emulator producing sound and graphics", the best
> solution is to provide Worker access to canvas as well as audio. Then you can
> have reliable audio and a reliable frame rate as well.


What about lack of hardware acceleration? That'll block audio as long as gfx is
on the same thread as audio, which in my case is a must for low lag sync.

-- 
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 Sunday, 8 July 2012 06:47:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 8 July 2012 06:47:59 GMT