rtsp-simple-server VS go-m3u8

If you want to stream your webcam as an H264 encoded rtsp stream, it can be done with either rtsp-simple-server or V4l2rtspserver And it is possible to stream a linux desktop (and any program that might be open, like your web browser with the gcode viewer running on it) with the V4l2Loopback device and either of the two prgrams above. It is quite an involved process, but it is do-able.

rtsp-simple-server

Download rtsp-simple-server_v0.20.2_linux_arm64v8.tar.gz from https://github.com/aler9/rtsp-simple-server/releases/download/v0.20.2/ % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 9379k 100 9379k 0 0 3497k 0 0:00:02 0:00:02 --:--:-- 6115k Finished. make[1]: Leaving directory '/home/pi/crowsnest/bin' Add User pi to group 'video' ... [OK] chown: invalid group: ‘pi:pi’e ... make: *** [Makefile:37: install] Error 1

I've tried using ffmpeg and rtsp simple server:

Ok, you need a NAS or their Cloud, a simple USB drive won't do it. The important thing is you need the receiving device to offer a transfer protocol named 'RTSP'. Modern Synology, QNAP, and MyCloud (by WD) devices support RTSP, although different methods to connect. Eufy Cloud would be the easiest method, next is Synology NAS is simple to setup with Eufy instruction, but since you have some hardware you can run things like this: https://github.com/aler9/rtsp-simple-server but obviously that will take more time and effort.

Very cool - going to try this out later. I had something similar on my todo list, but figured I would use: https://github.com/aler9/rtsp-simple-server

I had a nightmare setting this up for my streams. I ended up going with rtsp-simple-server as it seems to work a little quicker and is much better documented. There is an option to toggle between always having a stream "live" or stop when there are no viewers

Here is one example that I found (there are more). https://github.com/aler9/rtsp-simple-server

Apple is a part of AOMedia now. I think it will happen eventually. Also HLS has an IETF entry (RFC 8216).

The reference standard for ad markers in HLS manifest files is EXT-X-DATERANGE in the HLS RFC. https://tools.ietf.org/html/rfc8216#section-4.3.2.7 Unfortunately, very few systems support the EXT-X-DATERANGE markup format in the RFC as yet since vendor implementations exist.

Recommend taking a look at SUBTITLES sections 3.5 and 4.3.4.1 of https://tools.ietf.org/html/rfc8216. I can see how multi-language could get messy with the FFmpeg implementation, but it is relatively new functionality.

EDIT: they do use .ts and m3u8 but a bit fancier .m2ts (maybe mp4s as well?) and m3u8, at the very least for livestreaming. src and the standard it is based on.