3 ms·

This website could be a lot more useful if it answered these questions: * How good is this compared to other alternatives? (Or why choose this instead of somet

by AnonC 7y ago

This website could be a lot more useful if it answered these questions: * How good is this compared to other alternatives? (Or why choose this instead of something else?) * Where are the client apps for this, more importantly on mobile?

ofrzeta 7y ago
Sure, the website could be better. Here's a demo https://v3demo.mediasoup.org/ https://v3demo.mediasoup.org/ And here's the source code for the demo: https://github.com/versatica/mediasoup-demo/ https://github.com/versatica/mediasoup-demo/ Libs for native apps: https://github.com/haiyangwu/mediasoup-client-android https://github.com/haiyangwu/mediasoup-client-android https://github.com/ethand91/mediasoup-ios-client https://github.com/ethand91/mediasoup-ios-client
- anovikov 7y ago
  Libs for native apps suck. But, it is compatible with React Native and works fine there. In general, i recommend it. Only media server that i saw working (slightly) better is Jitsi, but it is 10x more cumbersome and time-consuming to learn.
  - deepinder10 7y ago
    making a single customisation in jitsi is a cumbersome task. You have to accept it how it is.
- jmillan 7y ago
  I'm a core mediasoup developer. Those libs for native apps are not official mediasoup components. We deliver libmediasoupclient[1] which is a native C++ implementation of the JS mediadiasoup-client[2] and uses libwebrtc[3] C++ native code directly. Those two libs for native apps make use of libmediasoupclient, but they are not written nor maintained by us. Having said that, to the moment there is no official Android or IOS native client but there is libmediasoupclient which will be the core for both. [1]: https://github.com/versatica/libmediasoupclient https://github.com/versatica/libmediasoupclient [2]: https://github.com/versatica/mediasoup-client https://github.com/versatica/mediasoup-client [3]: http://webrtc.github.io/webrtc-org/native-code/ http://webrtc.github.io/webrtc-org/native-code/
kabes 7y ago
This is more of a low level API. Not some ready to use thing like Jitsi. That is already a big difference with alternatives. Performance seems good: https://webrtchacks.com/sfu-load-testing/ https://webrtchacks.com/sfu-load-testing/ And it is very actively developed, which is arguably the most important metric in the current webRTC environment. Since the spec and browser implementations are a fast moving target right now and for the years to come.
ibc 7y ago
Hi, mediasoup co-author here. Comparing Jitsi with mediasoup is like comparing Netflix (backend + apps) with Express.js + libcurl. Jitsi developers may replace their RTC core internals (including the SFU) with mediasoup + mediasoup-client and you wouldn't even realize of it. Hope this helps.

by AnonC 7y ago

ofrzeta 7y ago

Sure, the website could be better. Here's a demo https://v3demo.mediasoup.org/ https://v3demo.mediasoup.org/ And here's the source code for the demo: https://github.com/versatica/mediasoup-demo/ https://github.com/versatica/mediasoup-demo/ Libs for native apps: https://github.com/haiyangwu/mediasoup-client-android https://github.com/haiyangwu/mediasoup-client-android https://github.com/ethand91/mediasoup-ios-client https://github.com/ethand91/mediasoup-ios-client

anovikov 7y ago
Libs for native apps suck. But, it is compatible with React Native and works fine there. In general, i recommend it. Only media server that i saw working (slightly) better is Jitsi, but it is 10x more cumbersome and time-consuming to learn.
- deepinder10 7y ago
  making a single customisation in jitsi is a cumbersome task. You have to accept it how it is.
jmillan 7y ago
I'm a core mediasoup developer. Those libs for native apps are not official mediasoup components. We deliver libmediasoupclient[1] which is a native C++ implementation of the JS mediadiasoup-client[2] and uses libwebrtc[3] C++ native code directly. Those two libs for native apps make use of libmediasoupclient, but they are not written nor maintained by us. Having said that, to the moment there is no official Android or IOS native client but there is libmediasoupclient which will be the core for both. [1]: https://github.com/versatica/libmediasoupclient https://github.com/versatica/libmediasoupclient [2]: https://github.com/versatica/mediasoup-client https://github.com/versatica/mediasoup-client [3]: http://webrtc.github.io/webrtc-org/native-code/ http://webrtc.github.io/webrtc-org/native-code/

kabes 7y ago

This is more of a low level API. Not some ready to use thing like Jitsi. That is already a big difference with alternatives. Performance seems good: https://webrtchacks.com/sfu-load-testing/ https://webrtchacks.com/sfu-load-testing/ And it is very actively developed, which is arguably the most important metric in the current webRTC environment. Since the spec and browser implementations are a fast moving target right now and for the years to come.

ibc 7y ago

Hi, mediasoup co-author here. Comparing Jitsi with mediasoup is like comparing Netflix (backend + apps) with Express.js + libcurl. Jitsi developers may replace their RTC core internals (including the SFU) with mediasoup + mediasoup-client and you wouldn't even realize of it. Hope this helps.