W3C home > Mailing lists > Public > public-media-capture@w3.org > December 2011

Re: Comment to issues in MediaStream Capture Scenarios: Preview a stream

From: Randell Jesup <randell-ietf@jesup.org>
Date: Thu, 15 Dec 2011 15:22:57 -0500
Message-ID: <4EEA5721.400@jesup.org>
To: public-media-capture@w3.org
On 12/15/2011 1:10 PM, Travis Leithead wrote:
>> -----Original Message-----
>> From: Timothy B. Terriberry [mailto:tterriberry@mozilla.com]
>>
>>> [bryan] I agree, I cannot think of a typical use case that would
>>> require 1:N association.
>>
>> I can think of several. Suppose you want to take a local capture stream
>> and a) send it to a remote PeerConnection, while b) recording it locally
>> and/or c) showing a local preview. To say nothing of wanting to send it
>> simultaneously to two or more remote PeerConnections (for small
>> conferences that don't want to use a dedicated mixer).
>
> Presumably you don't need to call "createObjectURL" in order to send the MediaStream out via a PeerConnection, right? Depending on what we spec, we might not need to createObjectURL in order to record either.
>
> Can you think of a scenario that would require multiple "previews"? In other words, for createObjectURL, should the resultant URL be one-time-use for a video/audio tag, or multi-use? If multi-use, then why?

Mildly (or maybe seriously) contrived, but displaying the preview in 
multiple windows, each displayed on a different monitor (especially for 
the case of someone who has a local self-image and a remote self-image 
on a projection screen, where the presenter doesn't want to have his 
notes shown on the projection screen as well).

There may be others.  A balance needs to be struck with supporting every 
possible use versus complexity and how often those uses occur.

-- 
Randell Jesup
randell-ietf@jesup.org
Received on Thursday, 15 December 2011 20:25:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:14:58 GMT