W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

Re: Web Audio API spec review

From: Chris Wilson <cwilso@google.com>
Date: Tue, 15 May 2012 09:55:19 -0700
Message-ID: <CAJK2wqUDRiZu1xGfjD0wigUwM-Py+WKBF1xRv0n7vVqormEhHQ@mail.gmail.com>
To: olli@pettay.fi
Cc: Alistair MacDonald <al@signedon.com>, Olivier Thereaux <olivier.thereaux@bbc.co.uk>, Philip Jägenstedt <philipj@opera.com>, public-audio@w3.org
Several of these reviews were sent directly to this list.

On Tue, May 15, 2012 at 9:40 AM, Olli Pettay <Olli.Pettay@helsinki.fi>wrote:

> On 05/15/2012 07:00 PM, Alistair MacDonald wrote:
>
>> Is the reason that the Web Audio API has been implemented for longer time?
>>>
>>
>> I would say no. The reviews from companies I saw were after a
>> MediaStreams build and documentation were available.
>>
>>
>>  This is the part I'm not really aware of. What industry and why?
>>>
>>
>> Primarily game and music companies. Only games companies, to my
>> knowledge, made an effort to review the specs.
>>
> So some important feedback is clearly missing.
>
>
>
>
>> The Web Audio API's features were closer to the needs of the industry
>> members that contacted the group. When companies contacted me about
>> the work, I asked them to review both specs;
>>
> Are the reviews available somewhere?
>
>
>
>  however they chose not to
>> review the MediaStreams API because it was not a good fit for the
>> kinds of projects they work on.
>>
>> One of the most desired features/complaints was real streaming support
>> from the Web Audio API, so that developers do not have to download
>> content up-front, especially important in low-bandwidth situations.
>>
>>
>> Hope that helps
>>
>> --
>> Al
>>
>>
>
>
>
Received on Tuesday, 15 May 2012 16:55:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 15 May 2012 16:55:53 GMT