[HN Gopher] Mediasoup - WebRTC video conferencing
___________________________________________________________________
Mediasoup - WebRTC video conferencing
Author : simonpure
Score : 45 points
Date : 2020-05-18 18:43 UTC (4 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| monkeydust wrote:
| What kind of hardware would I need to setup this to run a private
| video chat server for say 10 users?
| ibc wrote:
| 10 users? the cheapest one.
| Recursing wrote:
| What advantages would this offer over jitsi meet?
| kabes wrote:
| Jitsi meet is a conferencing app. You likely mean jitsi
| videobridge. That's the SFU part and comparable to mediasoup.
|
| Mediasoup has a bit more modern codebase and offers a rather
| low-level framework to build your own SFU. Whereas Jitsi
| videobridge is more of a ready-to-go SFU, but less flexible.
|
| Mediasoup has very good node bindings, which may or may not
| be an advantage to you.
|
| They offer similar (good) performance, although Mediasoup has
| a slight edge here. They're both very actively being kept up
| to date with the latest standards (in contrast with Kurento
| which is now as good as dead after Twilio bought the team).
| This is very important since both the spec and browser
| implementations are a fast moving target.
|
| Disadvantage of mediasoup is that it is mainly maintained by
| just 1 or 2 persons and not yet used as much as Jitsi, so
| it's a bit of a gamble to start building your product on top
| of that.
| ibc wrote:
| Yep, two active developers but being just a set of
| libraries it's good enough. We also get nice contributions
| (C++ fixes and optimizations) via PR in GitHub. And we use
| mediasoup in different commercial products.
| ibc wrote:
| Jitsi is a full application (web app, backend servers) with a
| specific use case: meetings (similar to Zoom or Google Meet).
|
| mediasouop is not an application but a set of server and
| client low level libraries to build whichever kind of
| audio/video applications (not just meetings). You don't
| "install mediasoup and configure it". You create your Node
| app and integrate mediasoup as you do with any other NPM
| dependency. Same in client side. More here:
|
| https://mediasoup.org/documentation/overview/
|
| Of course, this means that you must build your application,
| including UI, client-server signaling, etc etc.
| ignoramous wrote:
| > _...build whichever kind of audio /video applications..._
|
| Is live streaming a use-case that's under scope? If so, can
| the client P2P or requires a relay server for all traffic?
| ibc wrote:
| PornHub uses mediasoup for live cams.
| toomuchtodo wrote:
| That's quite the endorsement.
| microcolonel wrote:
| I think there's nothing stopping you from attempting
| that, but you would need some pretty complex client
| software to get a good experience with P2P live
| streaming.
| telesilla wrote:
| The demo is nice and clean. How does this compare to Kurento, or
| Janus?
|
| Edit : I see Kurento is now assumed dead thanks to Twilio buying
| them, and I understand Janus doesn't provide any client
| libraries.
| ibc wrote:
| mediasoup (in server side) is a Node.js library or a NPM
| dependency that you integrate into your Node.js app. Of course
| it comes with tons of C++ lines but, from the point of view of
| the user, it's just yet another NPM dependency into your
| Node.js project.
|
| mediasoup overview here:
| https://mediasoup.org/documentation/overview/
| detaro wrote:
| So no documented c++ library to bind other languages through?
| server side needs to be node.js?
| ibc wrote:
| It's a Node library, yes.
| microcolonel wrote:
| If you want that, probably Janus is something worth looking
| at.
| mandaputtra wrote:
| It is more like building block than one off video mettings
| solution.
|
| Kurento still the easiest to deploy I think. Used in OpenVidu.
___________________________________________________________________
(page generated 2020-05-18 23:00 UTC)