Show HN: Lightspeed – subsecond, open source, self hosted stream from OBS

Post by GRVYDEV » Mon, Jan 04, 2021, 7:19 AM UTC

rlyshw wrote: post #21

GRVYDEV wrote: post #18

Earlier quoted context omitted.

Also, you’re not “hacking” obs. oBS is compiled with the FTL sdk you just have to tell it to use it.

Got it. I’m fresh on FTL, first I’ve really dug into it so apologies for the ignorance. I’m in the industry of stream transport and mostly work with SRT. Looking forward to tinkering with this!

Post by rapsey » Mon, Jan 04, 2021, 7:36 AM UTC

rlyshw wrote: post #13

GRVYDEV wrote: post #2

Welcome to Project Lightspeed. This is a project that allows anyone to easily deploy their own sub-second latency live-streaming server. In its current state you can stream from OBS [1] and watch that stream back from any desktop browser. This has been a super fun project which has taught me more than any other project I have done. It uses Rust, Go and React and can be deployed fairly easily on a very lightweight ser…

This project is pretty cool, I’ll tinker around with it tomorrow. As an aside, I’ve noticed you’re building out your own stream protocol stack (FTL/LightSpeed). What’s the reasoning there? Seems slightly inconvenient to have to “hack” OBS to make the output stream work. Will FTL support be merged into OBS in the future? If you’re just trying to avoid the latency of RTMP then I might suggest considering the existing S…

Post by imtringued » Mon, Jan 04, 2021, 7:42 AM UTC

12things wrote: post #4

GRVYDEV wrote: post #2

Welcome to Project Lightspeed. This is a project that allows anyone to easily deploy their own sub-second latency live-streaming server. In its current state you can stream from OBS [1] and watch that stream back from any desktop browser. This has been a super fun project which has taught me more than any other project I have done. It uses Rust, Go and React and can be deployed fairly easily on a very lightweight ser…

A very interesting project, can you elaborate more on how it is getting sub second latency and why youtube/twitch seem to have more than a few seconds of delay.

Post by GRVYDEV » Mon, Jan 04, 2021, 7:47 AM UTC

matsemann wrote: post #23

Very cool! If you want casual people to use this, I would look into simplifying the setup. Either by providing compiled binaries instead of having to set up go, rust etc oneself. Or by containerizing something.

Post by GRVYDEV » Mon, Jan 04, 2021, 7:50 AM UTC

samstave wrote: post #29

GRVYDEV wrote: post #8

Earlier quoted context omitted.

YouTube and twitch use RTMP which operates over TCP. This means that each time we send a packet we need to ensure that it’s been received which adds latency overhead. Lightspeed uses the FTL protocol which operates over udp thus reducing the latency overhead

So assuming you have packet loss - you just get a paused/blank stream until the flow continues? How does it handle any network issues. Would it ever be possible to route two stream via different paths to the client and let the client just accept the first packet from either and drop the other in order to add some redundancy to delivery?