as I just said on blink-dev I think RTCConfiguration is the wrong place for this, it belongs next to https://w3c.github.io/webrtc-pc/#dom-rtcrtpencodingparameters-ptime @rshpount one would already not need renegotiation to change the ptime via encoding parameters, no? This would simply automate the process instead of the consumer having to call getStats, decide the netwok conditions are "bad" and then change the ptime for a "better" tradeoff. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2309#issuecomment-535361723 using your GitHub accountReceived on Thursday, 26 September 2019 06:38:34 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:48 UTC