4 ms·
Can someone explain how mediasoup differs from the RTCPeerConnection object (and related events) discussed in this Mozilla webrtc tutorial [0]? Given that it us
by webel0 6y ago
Can someone explain how mediasoup differs from the RTCPeerConnection object (and related events) discussed in this Mozilla webrtc tutorial [0]? Given that it uses c++ I figure that mediasoup is more than just a wrapper around this? Any usability or reliability benefits of either?
[0] https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Signaling_and_video_calling https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/...
- ibc 6y agomediasoup (server side, so the Node + C++ component you mean) does not implement "RTCPeerConnection". That's just needed for browsers. In mediasoup we don't use SDP but specific RTP parameters as defined here: https://mediasoup.org/documentation/v3/mediasoup/rtp-parameters-and-capabilities/ https://mediasoup.org/documentation/v3/mediasoup/rtp-paramet... If you want to know why we don't use SDP (as communication means between client and server) here a good reading: https://webrtchacks.com/webrtc-sdp-inaki-baz-castillo/ https://webrtchacks.com/webrtc-sdp-inaki-baz-castillo/
- webel0 6y agoAh, okay, whenever I think webrtc I assume p2p with no server but I am now actually reading into what SFU is, etc. Makes sense. Thanks for pointer to these resources.