W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

Re: Resolution to republish MSP as a note

From: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Date: Wed, 8 Aug 2012 19:35:57 +0300
Message-ID: <CAJhzemW6iXB7yM6ygJVc6WD9wEMA8d0X+SGd1jbHXO-ps6sShg@mail.gmail.com>
To: Chris Wilson <cwilso@google.com>
Cc: Srikumar Karaikudi Subramanian <srikumarks@gmail.com>, public-audio@w3.org
On Wed, Aug 8, 2012 at 7:31 PM, Chris Wilson <cwilso@google.com> wrote:

> On Wed, Aug 8, 2012 at 5:56 AM, Jussi Kalliokoski <
> jussi.kalliokoski@gmail.com> wrote:
>> But we already have intertwined audio/video on the web, both with media
>> elements and WebRTC, so in my opinion we should design extending APIs
>> accordingly.
> I think we have a need for synchronized-source media elements, but I don't
> think the video and audio are intertwined in terms of effects/pipeline.
>> I share your concerns. But on the other hand I think we might even get
>> where we're going faster if we just let go of the need for native nodes and
>> the rest of the complexity that comes with them.
> I don't understand the use of the word "complexity" here.  I think a
> MSP+DSP-based architecture would be much MORE complex to use.

I was referring to "complexity in design/implementation/maintainability" as
I said earlier. Ease of use is fixable with a library that might just
operate exactly as the Web Audio API or not.

> -Chris

Received on Wednesday, 8 August 2012 16:36:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:01 UTC