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: Mon, 09 Jul 2012 09:25:04 +0000
Message-Id: <E1SoADI-00005y-Pk@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #39 from Marcus Geelnard (Opera) <mage@opera.com> 2012-07-09 09:25:04 UTC ---
(In reply to comment #38)
> To sum up my argument: We are currently not provided all the resources inside a
> webworker to attain full independence from the main thread yet, and dependence
> on the main thread kills us with i/o lag.

A possible solution for emulators like the JS GBC emulator (which I really
like!): move the audio emulation part to a Web worker (making it independent
from the main thread), and post time-stamped audio HW register writes from the
main thread to the audio Web worker (should be quite compact data?). That way
you would be glitch free even in cases of i/o lag. This assumes that you can do
the audio HW emulation independently from the rest of the machine, but for
simple "8-bit" sound HW, I think it can easily be done.

-- 
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 Monday, 9 July 2012 09:25:10 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 July 2012 09:25:10 GMT