W3C home > Mailing lists > Public > public-webrtc@w3.org > September 2016

video track "black" vs. "frozen frame"

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Tue, 27 Sep 2016 10:59:25 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B4B060065@ESESSMB209.ericsson.se>
We talked about this in Lisbon,

and I recall us saying something like, in a situation where we have a

MST -> RtpSender -> RtpReceiver -> MST -> <video element>

(MST == MediaStreamTrack) setup, that the video element should:

* Render black if the send side MST was disabled (or muted upstream)
* Render a frozen video frame if the RtpSender was "stopped"

Is this correct?

And if so, my question is: How to stop the sender? There is no .stop() 
method. The RtpTransceiver has a .stop() method, but that would also 
stop the local RtpReceiver, which may not be desirable, and would not 
have any action until after a negotiation.

Bernard mentions [1] "active=false", but it is a long time since we had 
"active" on RtpSenders. It seems like that would be a good fit though.

[1] https://www.w3.org/2016/09/23-webrtc-minutes#item09


Received on Tuesday, 27 September 2016 10:59:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:19 UTC