Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
werift-webrtc
WebRTC Implementation for TypeScript (Node.js), includes ICE/DTLS/SCTP/RTP/SRTP/WEBM/MP4
-
-
amazon-kinesis-video-streams-webrtc-sdk-c
Amazon Kinesis Video Streams Webrtc SDK is for developers to install and customize realtime communication between devices and enable secure streaming of video, audio to Kinesis Video Streams.
-
-
SIPSorcery
A WebRTC, SIP and VoIP library for C# and .NET. Designed for real-time communications apps.
-
libdatachannel
C/C++ WebRTC network library featuring Data Channels, Media Transport, and WebSockets
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
If you want to do servers or embedded you shouldn’t. It makes sense to use in the places it was designed for though!
What features of libwebrtc in particular would you like to see in other implementations. I am very excited to see a future with [0] on the client side.
[0] https://github.com/algesten/str0m
Pion (https://github.com/pion/webrtc) works well and offers a good set of features.
I set up a simple website to stream two webcams in my chicken coop using Janus / WebRTC: https://github.com/dbrgn/chicken-coop/tree/main/rpi-image See README for a quick overview.
Another interesting SFU library is MediaSoup: https://mediasoup.org/
> despite WebRTC mostly being about client/client communication
This is actually kind of a misconception, though it’s an understandable one given that WebRTC is almost always pitched as a peer-to-peer protocol.
In practice, most people using WebRTC for video are sending their video to a server, not directly to another client. It’s pretty safe to assume that most people who use your app are going to need TURN, and at that point, you’re not really doing peer-to-peer at all, so you might as well just have your browser-based app talk to a server that’s pretending to be another browser.
These servers (called Selective Forwarding Units or SFUs) can operate like a TURN server in the case of a one-on-one call, but they can also multiplex everyone’s feeds in the case of a larger conference (peer-to-peer 5 person calls would require each participant to send 4 copies of their video) and often have extra features like the ability to record calls, transcode streams or convert to other protocols.
The one I’ve used a lot is called Janus[0], it’s open source and has good docs, I recommend people check it out if they’re interested in getting deeper into WebRTC or other video streaming tech.
[0] https://janus.conf.meetecho.com
I set up a simple website to stream two webcams in my chicken coop using Janus / WebRTC: https://github.com/dbrgn/chicken-coop/tree/main/rpi-image See README for a quick overview.
Another interesting SFU library is MediaSoup: https://mediasoup.org/
