Project-Lightspeed VS Pion WebRTC

Depending on how you want to achieve this, you could use a combination of OBS + Restreamer or OBS + Project-Lightspeed. Another solution would be to use more specific solutions like neko

I also used to use Project-Lightspeed, which worked great. I abandoned it because I wanted to get off of FTL based on the OBS thread above. It otherwise worked for me.

https://github.com/GRVYDEV/Project-Lightspeed is a 'Twitch like' server that does FTL input from OBS. You can run OBS on the Ubuntu desktop and do a desktop capture. Viewers can then watch on the 'Project Lightspeed' host.

I recommend Project-Lightspeed for this. It uses the FTL protocol (similar to the now defunct Mixer) with WebRTC for great latency. I've used it many times for streaming games, etc. and it works well.

Special thanks to the Ryujinx Discord for helping me test and to the Lightspeed Project (https://github.com/GRVYDEV/Project-Lightspeed)!

jellyfin can certainly do what you are looking for, but it seems like you probably don't have enough bandwidth to reliably host the service at home, and may be overkill for your usage... you could set up project lightspeed (https://github.com/GRVYDEV/Project-Lightspeed) on a $5/month VPS and use OBS to stream video with sub 1 second latency, you can install teamspeak or mumble or something on the same VPS for voice chat.

I am really excited about https://github.com/sepfy/libpeer. It has examples ready for ESP32 etc....

When working on KVS I wasn't familiar with the embedded space at all. I saw 'heavyweight' embedded where you were running on Linux. Then you had RTOS/No OS at all. I wasn't prepared for these devices at all. If we can make WebRTC work in the embedded space I think it will really accelerate what developers are able to build!

Remotely driven cars, security cameras, robots in hospitals that bring iPads to infectious patients etc... Creative people are building amazing things. The WebRTC/video space needs to work harder and support them :)

-----

I love how diverse the WebRTC space is now. Outside of this implementation you have plenty of other options!

* https://github.com/shinyoshiaki/werift-webrtc (Typescript)

* https://github.com/pion/webrtc (Golang)

* https://github.com/webrtc-rs/webrtc (Rust)

* https://github.com/algesten/str0m (Rust)

* hhttps://github.com/sepfy/libpeer (C/Embedded)

* https://webrtc.googlesource.com/src/ (C++)

* https://github.com/sipsorcery-org/sipsorcery (C#)

* https://github.com/paullouisageneau/libdatachannel (C++)

* https://github.com/elixir-webrtc (Elixir)

* https://github.com/aiortc/aiortc (Python)

* GStreamer’s webrtcbin (C)

See https://github.com/sipsorcery/webrtc-echoes for examples of some running against each other.

I have worked four jobs related to https://github.com/pion/webrtc and one for https://webrtcforthecurious.com

Two companies used Pion. The other two were just using the protocol (WebRTC)

In my experience Go has been relatively approachable for people that are good at PHP. It has a great standard library and a pretty solid ecosystem, though frameworks aren’t as popular in Go. There are some well regarded libraries for things like WebRTC via https://github.com/pion/webrtc WebSicket via https://github.com/nhooyr/websocket

Don't try to make RTC yourself, it looks easy, but in fact, it's a really hard problem to solve. Use https://pion.ly/ it's a pretty solid package they also have a discord/slack channel with a lot of helpful people there.

Maybe you can reuse some of this code: https://github.com/pion/webrtc/blob/master/examples/data-channels/main.go