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

11–20 of 49 posts

Re: Mediasoup – WebRTC video conferencing

#11

Post by detaro »

ibc wrote: post #10
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/

So no documented c++ library to bind other languages through? server side needs to be node.js?

Re: Mediasoup – WebRTC video conferencing

#12

Post by ignoramous »

ibc wrote: post #6
Recursing wrote: post #4

Earlier quoted context omitted.

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. S…

> ...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?

Re: Mediasoup – WebRTC video conferencing

#13

Post by microcolonel »

detaro wrote: post #11
ibc wrote: post #10

Earlier quoted context omitted.

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/

So no documented c++ library to bind other languages through? server side needs to be node.js?

If you want that, probably Janus is something worth looking at.

Re: Mediasoup – WebRTC video conferencing

#14

Post by microcolonel »

ignoramous wrote: post #12
ibc wrote: post #6

Earlier quoted context omitted.

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. S…

> ...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?

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.

Re: Mediasoup – WebRTC video conferencing

#15

Post by ibc »

detaro wrote: post #11
ibc wrote: post #10

Earlier quoted context omitted.

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/

So no documented c++ library to bind other languages through? server side needs to be node.js?

It's a Node library, yes.

Re: Mediasoup – WebRTC video conferencing

#16

Post by ibc »

ignoramous wrote: post #12
ibc wrote: post #6

Earlier quoted context omitted.

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. S…

> ...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?

PornHub uses mediasoup for live cams.

Re: Mediasoup – WebRTC video conferencing

#17

Post by toomuchtodo »

ibc wrote: post #16
ignoramous wrote: post #12

Earlier quoted context omitted.

> ...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?

PornHub uses mediasoup for live cams.

That’s quite the endorsement.

Re: Mediasoup – WebRTC video conferencing

#18

Post by lilolmilkjug »

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.

Janus works pretty well, the endpoints are well documented and allowed me to write a small web app in python for connecting peers through janus. It's not too complicated

Re: Mediasoup – WebRTC video conferencing

#19

Post by micaelgallego »

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.

Kurento is not dead. New releases are published from time to time. And its companion project OpenVidu provides a lot of features. Mediasoup and Janus are also really good projects.

Disclaimer: I'm OpenVidu project lead.

Re: Mediasoup – WebRTC video conferencing

#20

Post by micaelgallego »

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

Kurento is not dead. Main contributions are on OpenVidu project, that somehow is part of Kurento (but with other name)
Post reply on HN