- From: Travis Leithead <travis.leithead@microsoft.com>
- Date: Wed, 30 Nov 2011 19:57:54 +0000
- To: Randell Jesup <randell-ietf@jesup.org>, "public-media-capture@w3.org" <public-media-capture@w3.org>
>-----Original Message----- >From: Randell Jesup [mailto:randell-ietf@jesup.org] >Sent: Wednesday, November 30, 2011 11:52 AM >To: public-media-capture@w3.org >Subject: Re: use cases not covered by media capture under DAP > >On 11/30/2011 2:21 PM, Travis Leithead wrote: >>> -----Original Message----- >>> From: brian.leroux@gmail.com [mailto:brian.leroux@gmail.com] On Behalf >Of >>> Brian LeRoux > >>> Perhaps these real world cases can be of use. >>> >>> In particular things we see all the time: >>> >>> - image source (many camera sensors common now, select from photo >>> lib/gallary VERY common) >> >> Can you clarify this? Are you saying that the camera loads an image from > > the local file system? For what purpose? > >Sending a video or image instead of current live camera output. I >believe the example shown by Anant at TPAC covered this ability (via a >'Browse' button I guess - I wasn't there). Ah, that makes sense. I can imagine a scenario where I'm sending my local media stream out via a PeerConnection in a live-chat, and I want to flip my local stream over to a screenshot/picture. I may want to be able to push that image "stream" up through the connection for some time interval before switching back. Of course, I could always just send the file too through other mechanisms :)
Received on Wednesday, 30 November 2011 19:58:33 UTC