RE: video track "black" vs. "frozen frame"

With respect to an encoding, we have 

This can be manipulated as shown in Example 2: 

var params = sender.getParameters();
// ... make changes to RTCRtpParameters
params.encodings[0].active = false;

There is also transceiver.setDirection(), but that sets the negotiation-needed flag.

From: Stefan Håkansson LK []
Sent: Tuesday, September 27, 2016 3:59 AM
Subject: video track "black" vs. "frozen frame"

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.



Received on Tuesday, 27 September 2016 16:41:36 UTC