- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 05 Dec 2017 08:50:53 +0000
- To: public-webrtc-logs@w3.org
I might be ignorant here, but why would changing a track require renegotiation? Isn't it just a different stream of images, and resolution, bitrate, etc, all handled by RTP packets and whatnot, not negotiated through SDP? setParameters() on the other hand allows you to make changes to the encoder settings. I imagine getting capabilities of HW or SW to require thread/process jumps, and encoders could fail at any time. Still isn't what the encoder is capable of a problem for createOffer() etc, when checking if negotiation is needed wouldn't you just look at the state of the current local description? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1677#issuecomment-349236698 using your GitHub account
Received on Tuesday, 5 December 2017 08:50:55 UTC