Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mediasoup – WebRTC video conferencing

github.com

Post reply on HN
Print view View original

1–10 of 49 posts

Re: Mediasoup – WebRTC video conferencing

#5

Post by kabes »

Recursing wrote: post #4
monkeydust wrote: post #2

What kind of hardware would I need to setup this to run a private video chat server for say 10 users?

What advantages would this offer over jitsi meet?

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.

Re: Mediasoup – WebRTC video conferencing

#6

Post by ibc »

Recursing wrote: post #4
monkeydust wrote: post #2

What kind of hardware would I need to setup this to run a private video chat server for say 10 users?

What advantages would this offer over jitsi meet?

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.

Re: Mediasoup – WebRTC video conferencing

#7

Post by ibc »

kabes wrote: post #5
Recursing wrote: post #4

Earlier quoted context omitted.

What advantages would this offer over jitsi meet?

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,…

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.

Re: Mediasoup – WebRTC video conferencing

#9

Post by mandaputtra »

telesilla wrote: post #8

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.

It is more like building block than one off video mettings solution.

Kurento still the easiest to deploy I think. Used in OpenVidu.

Re: Mediasoup – WebRTC video conferencing

#10

Post by ibc »

telesilla wrote: post #8

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.

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/

Post reply on HN