Pion WebRTC VS peerjs

You can run all your WebRTC traffic off a single port. You use the remote 3 tuple (IP, Port, Protocol) to demux traffic.

https://github.com/pion/webrtc/tree/master/examples/ice-sing... is one example of that.

I originally went the same route as you, and found that https://github.com/pion/webrtc is probably the best package out there for webrtc. I learned go just for it, and it paid off tenfold. Less memory, more connections, lower latency.

The "Mediasoup" project provides a high level JavaScript/TypeScript interface to the WebRTC APIs. The core logic of this project is implemented in C++/Rust. Consider taking a look at the project if you want an easy-to-use library instead of the low-level libWebRTC APIs. A notable project to mention is the Pion/webrtc project which has a Golang implementation of the WebRTC API. Of course, we should mention the rust port WebRTC.rs. Let’s keep all the rustaceans happy too!

What latency are you trying to do? Will the professor being communicating with the students while doing this? Will the students all have the same bandwidth, or will you want multiple renditions (low, med, high quality levels)?

If you want AV1 you will not be able to use RTMP. The protocol is orphaned/deprecated, so avoid if possible!

If I was building it this is what I would do, and my reasoning.

* For capture + encoding I would use OBS. You will want to use something that is easy for users to install configure. Professors will also have lots of custom requirements when it comes to layout etc... it will be tempting to do a ffmpeg command directly, but it will fall apart quick I believe.

* To get AV1 out of OBS I would use FFMPEG output. I would have it send RTP. RTP is used to carry video in a sub-second manner. This is the same protocol that WebRTC uses. You know have AV1 + low latency.

* Then for users to watch I would use WebRTC. That will allow them to watch in their web browser. Conceptually it will be like this https://github.com/pion/webrtc/tree/master/examples/rtp-to-w... this takes the RTP packets and puts them in the browser.

Lots of great projects exist that you could use for 'RTP -> WebRTC' like https://galene.org/ and https://livekit.io/ I would suggest checking them all out!

If you have more questions/want to talk to people in the video space always happy to chat on https://pion.ly/slack :)

For streaming video content your options would be HLS or WebRTC, maybe look into these gwuhaolin/livego and pion/webrtc.

WebRTC GitHub Forum --- Use your GitHub account to join WebRTC-related forums or start a discussion of your own.

Do you still see challenges with doing WebRTC on a server? I work on https://github.com/pion/webrtc so would love to hear what could be better :)

We've just released version 0.5.0 of the webrtccrate. This crate is a port of a Go project called Pion. It's a complete implementation of WebRTC in Rust, allowing you to build backends for media applications.

You might be able to eliminate the VPS by making it P2P using something like PeerJS [1]. PeerJS provides a free shared connection broker server.

[1]: https://peerjs.com/

We use peer.js module to create a WebRTC connection between clients

Now that we have all the required boilerplate we can start building the actual game. For the communications between peers we are going to use PeerJS a peer-to-peer library built on top of WebRTC.

I am using https://peerjs.com/. I am currently using their default brokering system (which is the default out-of-the-box). it seems (when necessary) i am able to run my own version as provided at: https://github.com/peers/peerjs-server

Without backend, you can choose WebRTC for all communication b/w players. peerjs is a good library for that. However, I would still suggest not to take this approach as it can be overwhelming.

Peerjs library for webRTC

Check out https://peerjs.com/. It's a good library, especially for one-on-one calls. It's P2P. When you start adding more users, it does tend to cause some performance issues, but it works well for smaller projects.

Fun fact about PeerJS, you'll need a server in order to use it (look into STUN/TURN/ICE for more info). The maintainer seems to be hosting one default instance that goes down from time to time. https://github.com/peers/peerjs/issues/671 https://github.com/peers/peerjs/issues/693

If you're looking to do "pure" P2P in the browser, we're not there yet as we cannot accept incoming connections without something in between right now.