4 ms·
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://g
by 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 agoLibs 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 agomaking a single customisation in jitsi is a cumbersome task. You have to accept it how it is.
- jmillan 7y agoI'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/