W3C home > Mailing lists > Public > public-html@w3.org > March 2012

Re: Call for Review: Web Audio API

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 21 Mar 2012 11:41:52 +1100
Message-ID: <CAHp8n2n4Bxk=epv70hz2dQzwcD5V4V1eL8-h1+BnCLLmso5vVQ@mail.gmail.com>
To: Doug Schepers <schepers@w3.org>
Cc: public-html <public-html@w3.org>
What interests me most here is the position of non-WebKit browsers
towards this API and towards implementing it, considering that there
are alternative proposals in development. Not so much about whether
they'd implement it, but rather whether they think it's implementable
and the right approach. Anyone from Mozilla, Opera, IE able to


On Tue, Mar 20, 2012 at 5:49 AM, Doug Schepers <schepers@w3.org> wrote:
> Hi, folks-
> The Audio Working Group published an updated Working Draft of Web Audio API
> [1] on 15 March 2012. From the introduction:
> [[
> This specification describes a high-level JavaScript API for processing and
> synthesizing audio in web applications. The primary paradigm is of an audio
> routing graph, where a number of AudioNode objects are connected together to
> define the overall audio rendering. The actual processing will primarily
> take place in the underlying implementation (typically optimized Assembly /
> C / C++ code), but direct JavaScript processing and synthesis is also
> supported.
> ]]
> We would appreciate review and feedback on the spec [1] and the use cases
> and requirements [2] from the participants in the WebRTC, WebApps, and HTML
> groups and the Media Capture task force.
> [1] http://www.w3.org/TR/2012/WD-webaudio-20120315/
> [2] http://www.w3.org/2011/audio/wiki/Use_Cases_and_Requirements
> Regards-
> -Doug Schepers
> On behalf of the Audio WG
Received on Wednesday, 21 March 2012 00:42:41 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:22 UTC