@aboba the demultiplexing approach on the receiver side is a theoretically merely more complicated as, lacking ssrc in RTCRtpEncodingParameters on the sender side (to stay on-topic) the only way to retreive them is getStats on the receiver side (sender side stats for simulcast are busted in Chrome) followed by renegotiation to pull those tracks out of the peerconnection. In practice I seem to manage to confuse the decoder enough to lock up my machine and spec-stats do not seem to return those ssrcs :joy: -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1174#issuecomment-468595593 using your GitHub accountReceived on Friday, 1 March 2019 09:07:42 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:46 UTC