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: Tue, 31 Jul 2012 09:05:13 +0000
Message-Id: <E1Sw8O9-0000Wh-9l@jessica.w3.org>
To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415

--- Comment #90 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2012-07-31 09:05:12 UTC ---
Having the audio thread never make blocking calls is good, but it leaves open
the spec/API question of how a node should behave when one of its inputs can't
produce data in a timely manner. It is possible to have the node pause while
the input catches up, and it's possible to fill the input with silence as
necessary. I think there are valid use-cases for both, especially when you
throw media element and MediaStreams into the mix.

Either way, it needs to be spelled out in the spec.

-- 
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 Tuesday, 31 July 2012 09:05:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 31 July 2012 09:05:14 GMT