ISSUE-107: (Bugzilla 17415) JavaScriptAudioNode processing in workers

JSWorkers

(Bugzilla 17415) JavaScriptAudioNode processing in workers

State:

CLOSED

Product:

Web Audio API

Raised by:

Marcus Geelnard

Opened on:

2012-06-04

Description:

https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#JavaScriptAudioNode

It has been discussed before (see [1] and [2], for instance), but I could not find an issue for it, so here goes:

The JavaScriptAudioNode should do its processing in a separate context (e.g. a worker) rather than in the main thread/context. It could potentially mean very low overhead for JavaScript-based audio processing, and seems to be a fundamental requirement for making the JavaScriptAudioNode really useful.

[1] http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0225.html
[2] http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0245.html

Related Actions Items:

No related actions

Related emails:

1. [web-audio-api] (JSWorkers): ScriptProcessorNode processing in workers (#113) (from notifications@github.com on 2013-09-11)
2. Re: Audio-ISSUE-107 (JSWorkers): JavaScriptAudioNode processing in workers [Web Audio API] (from olivier.thereaux@bbc.co.uk on 2012-06-06)
3. Re: Next teleconference : 6th June (from Olivier.Thereaux@bbc.co.uk on 2012-06-04)
4. Re: Next teleconference : 6th June (from mage@opera.com on 2012-06-04)
5. Audio-ISSUE-107 (JSWorkers): JavaScriptAudioNode processing in workers [Web Audio API] (from sysbot+tracker@w3.org on 2012-06-04)

Related notes:

Display change log