W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2014

Re: What is missing for building "real" services?

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Thu, 9 Jan 2014 09:15:41 +0000
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Randell Jesup <randell-ietf@jesup.org>
CC: public-webrtc <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1C4364B6@ESESSMB209.ericsson.se>
On 2014-01-09 01:56, Silvia Pfeiffer wrote:
> On Thu, Jan 9, 2014 at 10:10 AM, Randell Jesup <randell-ietf@jesup.org> wrote:
>> On 1/7/2014 8:50 PM, Alexandre GOUAILLARD wrote:
>>
>>
>>
>>
>> - call controls like mute / hold
>> Right now, you can mute a local stream, but it does not seem to be possible
>> to let the remote peers know about the stream being muted. We ended up
>> implementing a specific off band message for that, but we believe that the
>> stream/track could carry this information. This is more important for video
>> than audio, as a muted video stream is displayed as a black square, while a
>> muted audio as no audible consequence. We believe that this mute / hold
>> scenario will be frequent enough, that we should have a standardized way of
>> doing it, or interop will be very difficult.
>>
>>
>> There is no underlying standard in IETF for communicating this; it's
>> typically at the application level.  And while we don't have good ways in
>> MediaStream to do this yet, I strongly prefer to send an fixed image when
>> video-muted/holding.  Black is a bad choice....
> It would be nice if browsers sent an image, such as "video on hold" -
> just like they provide default 404 page renderings. This is a quality
> of implementation issue then. Maybe worth registering a bug on
> browsers. But also might be worth a note in the spec.

My understanding was always that the video element's poster could be
used for this purpose. But reading the algorithm specified for when the
poster is displayed, I'm not so sure any more.

Stefan
Received on Thursday, 9 January 2014 09:16:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:37 UTC