W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2011

Re: TPAC F2F and Spec Proposals

From: Joseph Berkovitz <joe@noteflight.com>
Date: Tue, 18 Oct 2011 08:34:43 -0400
Cc: Anthony Bowyer-Lowe <anthony@lowbroweye.com>, public-audio@w3.org
Message-Id: <CD02594F-1885-465A-A491-DAD457BE5F8D@noteflight.com>
To: Olli@pettay.fi
[snipping many vertical kilometers of dialogue]

> If we take effects out from Web Audio API, what are the main differences between MediaStream API and Web Audio API, and
> are there reasons to have two separate APIs to process
> audio?

This is the primary question worth answering.

I think the answer is not to be found in the API definitions themselves per se, which can inevitably be massaged to minimize differences. It is to be found in the nature of the concrete implementations that must be created, and the pressures on the implementers to optimize for one set of use cases vs. another.

For example, consider the differences between filesystems and scalable storage systems (like Amazon S3). They are conceptually very similar but they answer to different needs. The API differences between them are modest, but it is hard to get rid of the remaining 10-20% of dissimilarity.  This is because the underlying architectures that serve these APIs are fundamentally different.

Received on Tuesday, 18 October 2011 12:35:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:57 UTC