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

Re: MediaSource Extensions & MediaStream Processing API?

From: Robert O'Callahan <robert@ocallahan.org>
Date: Mon, 21 Nov 2011 16:26:12 +1300
Message-ID: <CAOp6jLYAapwp6W8OQ38D8=-bNUZeSKjmF4W0U-=1BZq-OamwgQ@mail.gmail.com>
To: "Michael[tm] Smith" <mike@w3.org>
Cc: public-audio@w3.org
On Mon, Nov 21, 2011 at 3:51 PM, Michael[tm] Smith <mike@w3.org> wrote:

> I see the abstract of Aaron Colwell's MediaSource Extensions proposal says:
>
>  This proposal extends HTMLMediaElement to allow JavaScript to generate
>  media streams for playback. Allowing JavaScript to generate streams
>  facilitates a variety of use cases like adaptive streaming and time
>  shifting live streams.
>
> http://html5-mediasource-api.googlecode.com/svn/trunk/draft-spec/mediasource-draft-spec.html
>
> It seems like it's intended for some of the same use cases as the
> MediaStream Processing API -
>
>  http://www.w3.org/2011/audio/drafts/1WD/MediaStream/
>
> So maybe this is another area where we should be working together on trying
> to converge on a common proposal?
>

It's a completely different approach. It gives JS control over what gets
fed into the demuxer/decoder, whereas MediaStream Processing gives you
control over the output.

Rob
-- 
"If we claim to be without sin, we deceive ourselves and the truth is not
in us. If we confess our sins, he is faithful and just and will forgive us
our sins and purify us from all unrighteousness. If we claim we have not
sinned, we make him out to be a liar and his word is not in us." [1 John
1:8-10]
Received on Monday, 21 November 2011 03:26:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 21 November 2011 03:26:41 GMT