Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SFU implementation vs mesh Mirotalk #14

Closed
pragmatech opened this issue Oct 1, 2021 · 3 comments
Closed

SFU implementation vs mesh Mirotalk #14

pragmatech opened this issue Oct 1, 2021 · 3 comments
Labels
question Further information is requested

Comments

@pragmatech
Copy link

Hi. As ever, thanks for sharing your impressive work. I hope you take a breather sometime too heh.
In addition to your different hosting environments for the two (Railway won't suffice for mediasoup SFU?), I'm curious as to your experience with tangible differences in the two implementations. Specifically, if one has aspirations for clubhouse like audio-centric use, might that sans-video approach work upon the mesh version? Other comparisons, based on your experience would also be interesting to learn. Thanks!

@miroslavpejic85 miroslavpejic85 added the question Further information is requested label Oct 2, 2021
@miroslavpejic85
Copy link
Owner

miroslavpejic85 commented Oct 2, 2021

MiroTalk P2P

Repo: https://github.com/miroslavpejic85/mirotalk

Architecture: WebRTC Mesh (peer to peer between browsers)

image

Can handle unlimited rooms without limit of time, each having around 5-8 users (audio-video streams ON) To have a good video-audio quality. The quality of the call is inversely proportional to the number of people on the call. Not need an intermediate media server for audio & video communication.

Required: Client PC (peers) must have a good Bandwith and CPU.
The current Live Demo is deployed on Hetzner - Ubuntu 20.04 (LTS) x64 for demonstration purposes.

Deploy: Any host that support Node.js like: Railway, Heroku, Hetzner, DigitalOcean (paid service) or Self-Hosting.

Bonus: There is an option to use it directly from your LOCAL PC and thanks to Ngrok you will be able to have conference and will be reached outside your local network, no matter where you are!


MiroTalk SFU

Repo: https://github.com/miroslavpejic85/mirotalksfu

Architecture: WebRTC SFU (Server with Selective Forwarding Unit) using mediasoup

image

Unlimited rooms, no limit of time, and many users. Routing is a multiparty topology, where each participant sends its media to the MiroTalk integrated server mediasoup, and receives all other's media from it.

Required: Server must have a very good Bandwidth, RAM and CPU.
The current Live Demo is deployed on Hetzner - Ubuntu 20.04 (LTS) x64 for demonstration purposes.

Deploy: VM that support Node.js and other stuff like: Hetzner, DigitalOcean, Amazon-Aws (paid service) or Self-Hosting.

Bonus: There is an Option to use it directly from your LOCAL PC by these settings and thanks to Ngrok you will be able to have conference and will be reached outside your local network, no matter where you are!


Choose

Based on the amount of users you have, you can choose the right solution for you :)

I hope I have clarified your doubts about the difference of the two versions?

Thanks and have a nice day.

Regards

@miroslavpejic85
Copy link
Owner

miroslavpejic85 commented Jul 19, 2022

For discussions, questions, help and support, please don't post here, but join with us on:

👉 DISCORD 👈 - help-and-support channel.

Thank you!

Repository owner deleted a comment from VladimirGorin Nov 20, 2022
Repository owner deleted a comment from nitad54448 Nov 20, 2022
@umair-me
Copy link

umair-me commented Mar 7, 2023

Good to have this in wiki.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants