> what is the rationale for making this controllable via the track and not the rtpReceiver? (other than the receiver not having a setParameters) Mostly, because the latency parameter we want to change is quite similar to the one which has been already described by MediaStreamTrack applyConstraints algorithm. On the rtpReceiver even getParameters are not having anything similar. -- GitHub Notification of comment by kuddai Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2109#issuecomment-471456805 using your GitHub accountReceived on Monday, 11 March 2019 09:03:10 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:46 UTC