pyrite
Signal-Calling-Service
Our great sponsors
pyrite | Signal-Calling-Service | |
---|---|---|
14 | 4 | |
258 | 410 | |
- | 0.5% | |
0.0 | 8.6 | |
6 months ago | about 1 month ago | |
Vue | Rust | |
MIT License | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pyrite
-
Ask HN: Why is there no enterprise grade open-source zoom alternative?
For more interesting related projects, you may also want to checkout https://github.com/pion/awesome-pion
I'm fiddling now and then on an alternative conferencing frontend(Pyrite - https://github.com/garage44/pyrite) for Galene(https://galene.org), which is a SFU that uses Pion.
- Pyrite: Open source video conferencing
-
Pyrite – open-source video conferencing
It would really help if the author had a list of "features" on the github project. It is a bit difficult to figure out what exact functionality the project supports.
* https://github.com/garage44/pyrite/
- Pyrite – open-source self-hoested video conferencing
-
Ask HN: Is it ok to reject a job because I don’t like their software?
Teams only show 4 streams at a time on Linux, the video/audio quality is mediocre and the video quality in the webclient is worse than the one using an Electron container, probably to force the app. Screensharing always tends to get stuck after a while, and they ignore any requests to start supporting Wayland, even while it takes minimal changes(update Electron).
Nowadays it's easy to setup your own conference server, and use webbased clients that don't require yet another Electron container. For instance, Galene(https://github.com/jech/galene) is an excellent resource-friendly SFU built on top of Pion(Golang).
Shameless plug: I'm the author of Pyrite(https://github.com/garage44/pyrite), an alternative WebRTC frontend for Galene
- Show HN: Pyrite – FOSS Video Conferencing
- Pyrite - Vue 3 WebRTC client for the Galène SFU
- Show HN: Pyrite – a WebRTC client for the Galène videoconference server
Signal-Calling-Service
-
Is async runtime (Tokio) overhead significant for a "real-time" video stream server?
I am npt sure if this is related but Signal built Signal Calling Service and according to them it worked great.
-
Pyrite – open-source video conferencing
I was curious and looked through the code of Galene briefly and found the following, which may answer your question. For context, I am familiar with the Jitsi code and have written my own calling server (and written about it: https://signal.org/blog/how-to-build-encrypted-group-calls/).
Galene appears to be less mature than Jitsi. For example, it uses REMB feedback messages from the client to calculate allowable bitrates rather than calculating the bitrates itself (as Jitsi and Signal's SFU do). Worse, it appears that what it does with that information is erroneous. I could be wrong, but it looks like the bitrate allocation code (see https://github.com/jech/galene/blob/e8fbfcb9ba532f733405b1c5...) only allocates the bitrate for one of the video streams, not all of them. Perhaps the author did not realize that there is one REMB sent back for all the video streams by WebRTC rather than one per stream (see, for example, here: https://source.chromium.org/chromium/chromium/src/+/main:thi...). Further, I find the spatial layer switching code to be strange. For examples, it doesn't go down a layer unless it's 150% over the estimated allowable bitrate, which gives a lot of opportunity for inducing latency.
In short, I think Galene has a ways to go before it works as well as Jitsi (Videobridge), and thus Pyrite group calls are unlikely to work as well as Jitsi group calls (for 1:1 calls, I don't know; I didn't look into that).
Oh, and just a reminder, the SFU we use for Signal group calls is also open source: https://github.com/signalapp/Signal-Calling-Service.
-
How to build large-scale end-to-end encrypted group video calls
And yeah, it uses Signal-Calling-Service written on Rust.
-
An Introduction to WebRTC Simulcast
That's a well written article covering the basics of simulcast.
If you're interested in seeing an implementation of an SFU doing simulcast forwarding written in Rust, we (at Signal) recently open sourced our SFU:
https://github.com/signalapp/Signal-Calling-Service/blob/mai...
What are some alternatives?
mediasoup - Cutting Edge WebRTC Video Conferencing
galene - The Galène videoconference server
Jitsi Meet - Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
rtp - A Go implementation of RTP
Jitsi Video Bridge - Jitsi Videobridge is a WebRTC compatible video router or SFU that lets build highly scalable video conferencing infrastructure (i.e., up to hundreds of conferences per server).
awesome-pion - A curated list of awesome things related to Pion
azure-ubuntu-jitsi - A private Jitsi videoconferencing set up on Azure
clip-beam-client - Easily share text and files between devices. Local P2P.
ion-sfu - Pure Go WebRTC SFU