- From: aboba via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Dec 2016 06:37:40 +0000
- To: public-webrtc-logs@w3.org
@pthatcherg Does the following make sense? setParameters cannot set the negotiation-needed flag and therefore must operate within the envelope negotiated by Offer/Answer. Once setLocalDescription has been called, the envelope is set and the number of simulcast encodings cannot be changed. If a transceiver is constructed with sendEncodings specifying N simulcast encodings, and setLocalDescription has been called, setParameters cannot be used to increase or decrease the number of simulcast encodings. However, if setLocalDescription has not yet been called, setParameters can be used to change the number of encodings and the parameters set will be reflected in the SDP produced by createOffer/createAnswer. setParameters can be used to activate or inactivate a simulcast encoding at any time by setting encodings[].active. If the desire is to stop sending one or more simulcast encodings, this can be accomplished by setting encodings[].active to "false". If the desire is to re-enable a simulcast encoding that is inactive, this can be accomplished by setting encodings[].active back to "true". -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/945#issuecomment-265664930 using your GitHub account
Received on Thursday, 8 December 2016 06:37:47 UTC