- From: <bugzilla@jessica.w3.org>
- Date: Mon, 30 Jul 2012 23:45:02 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415 --- Comment #85 from Chris Rogers <crogers@google.com> 2012-07-30 23:45:01 UTC --- I think there's been a misunderstanding that somehow the JavaScript code rendering audio in a JavaScriptAudioNode callback will block the audio thread! This is not the case. An implementation should use buffering (producer/consumer model) where the JS thread produces and the audio thread consumes (with no blocking). This is how it's implemented in WebKit. Additionally, the JS callbacks should all be clocked/scheduled from the audio system (in the implementation), and not rely on setTimeout() or require client polling/querying of a timestamp from javascript (which is a much less ideal approach). -- 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, 30 July 2012 23:45:03 UTC