W3C home > Mailing lists > Public > public-xg-audio@w3.org > July 2010

Re: Web Audio API Proposal

From: Mark <mark.boas@gmail.com>
Date: Wed, 14 Jul 2010 16:42:21 +0200
Message-ID: <AANLkTinPh5khfH4I0kb-1one1O5VBiM-dqPSDLaO5bLV@mail.gmail.com>
To: schepers@w3.org, public-xg-audio@w3.org
I've reconfigured my profile and am resending this from my gmail account as
it didn't get through when sending from my happyworm.com address. Apologies
if it breaks the thread.

Hi

Regarding Doug's point about collecting "use cases and requirements
from beyond the browser implementer community". We have created a
jQuery plugin (jPlayer) that takes advantage of the latest HTML5 audio
implementation, as a result we have a lively community of 400 or so
web audio developers. I'm hoping that this community will act as a
useful input to this group. No doubt there are other groups out there
that we can tap for ideas and requirements, and am happy to look into
this.

I'm not an audio expert by any means but as far as an API is concerned
I believe that many functions should be implemented within the browser
itself where possible. As long as the developer has access to the raw
audio data, can they not then write their own functions using
JavaScript when the need arises?

Regards

Mark Boas

Happyworm Ltd


On 18/06/2010 02:33, Doug Schepers wrote:

Hi, Folks-

Robert O'Callahan wrote (on 6/16/10 1:21 AM):

On Wed, Jun 16, 2010 at 12:10 PM, Chris Marrin wrote:

On Jun 15, 2010, at 4:38 PM, Robert O'Callahan wrote:


OK, but is there any evidence that they're complete? What fraction
of use cases would be forced to resort to JS-based sample processing?


    We can't know that.


We can at least collect use cases, starting with existing demos that get
direct access to samples, and see how many of them fit.


This is precisely why I set the goal of this XG to bring in musicians, audio
engineers, and others who will be the ultimate stakeholders in this
functionality... to collect use cases.

I'm really glad that so early in the process, we have concrete API
approaches to compare and contrast, but I hope we will take a little time to
build up the audio community participation in this forum before we go too
far down an irrevocable path (i.e. shipping implementation).

What strategies can people suggest to collect use cases and requirements
from beyond the browser implementer community?

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Wednesday, 14 July 2010 23:05:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 September 2010 18:33:55 GMT