W3C home > Mailing lists > Public > public-webrtc@w3.org > April 2013

Re: Improving disconnection handling

From: cowwoc <cowwoc@bbs.darktech.org>
Date: Thu, 11 Apr 2013 15:21:04 -0400
Message-ID: <51670D20.20402@bbs.darktech.org>
To: public-webrtc@w3.org
On 11/04/2013 6:48 AM, Harald Alvestrand wrote:
> On 04/11/2013 06:09 AM, Martin Thomson wrote:
>> On 10 April 2013 18:48, cowwoc<cowwoc@bbs.darktech.org>  wrote:
>>>      I don't like users staring at a "frozen" image for five seconds. If I
>>> had a way of finding out when the last video frame was received, I would
>>> fade out the video immediate after it begins hanging and fade it back in
>>> when it reconnects. What do you think?
>> I think that you need to work on a precise definition of "begins
>> hanging" such that it could be detected.  You might also find that a
>> fadeout over such a short lapse is more annoying to your users than
>> you think.  There may be a way of getting the time of the last
>> rendered update, but keep in mind that the time for the video will
>> probably be based on the sender clock, which can drift in relation to
>> the local clock.  You really don't want false positives.
>>
> The spec says that the time of the <video> tag advances during playback.
>
> (See 
> http://dev.w3.org/2011/webrtc/editor/getusermedia.html#mediastreams-as-media-elements 
> - item about "currentTime").
>
> Does it advance when the video freezes?
>

     That did it! Thank you very much :)

     Is it safe to assume that all implementations will behave this way?

Gili
Received on Thursday, 11 April 2013 19:21:55 UTC

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