RE: Why does media capture require a browser? from Jim Barnett on 2013-02-19 (public-media-capture@w3.org from February 2013)

From: Jim Barnett <Jim.Barnett@genesyslab.com>
Date: Tue, 19 Feb 2013 23:43:02 +0000
To: Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <57A15FAF9E58F841B2B1651FFE16D2810220A0@GENSJZMBX03.msg.int.genesyslab.com>

That's why all the secondary and tertiary destinations of MediaStream are going into separate documents....

- Jim

-----Original Message-----
From: Harald Alvestrand [mailto:harald@alvestrand.no] 
Sent: Tuesday, February 19, 2013 6:36 PM
To: public-media-capture@w3.org
Subject: Re: Why does media capture require a browser?

I have never thought that pushing bits into <video> / <audio> was the only thing we would do.

PeerConnection is the second destination of a MediaStream.

Recording is the third.

The Audio Processing API is the fourth.

But I strongly (urgently, desperately, pleadingly) want to have the core MediaStream functionality specified, frozen, implemented and useful without having to wait for the fifth, sixth, seventh and eight destinations to be fully baked.

                   Harald

Received on Tuesday, 19 February 2013 23:43:26 UTC