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

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #95 from Grant Galitz <grantgalitz@gmail.com> ---
I remember writing code for my js audio lib to support the mediastream api and
being required to output audio in a different thread:
https://github.com/grantgalitz/XAudioJS/blob/master/XAudioServerMediaStreamWorker.js

It worked with an experimental firefox build that was published. Problem is,
that there's up to a quarter second latency that kills. The end user of a
browser will notice a giant time delay between an in-game event and the audio
for it.

I have no problems with having a spec that has off thread audio, just don't
cripple stuff by removing the on-thread audio. It's been mentioned many times
that there is work on canvas support in-workers, so that it can be done
alongside the audio out of the UI thread. The problem I have with that is it
complicates keeping the audio libraries separate from the code that uses it. I
want to support legacy audio APIs that use the main UI thread, and this will
complicate that greatly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Friday, 29 March 2013 04:15:56 UTC