mediamtx VS rtsp-simple-server

I started a discussion on the MediaMTX Github repo, where you can find more information on my problem: https://github.com/bluenviron/mediamtx/discussions/2787

For my apartment, I run rtsp-simple-server[1] on my home server and use Raspberry Pis with generic USB webcams running ffmpeg to stream the audio/video to the RTSP server. Then I run camera.ui[2] separately for a nicer interface on top of all the cameras, HomeKit integration, etc.

The only downside hardware-wise is I don't get any indoor IR night vision with these, which some of the nicer "smart home" account-locked ones do.

It's honestly not too bad to set up if you run [1] and [2] in Docker. I've done disaster recovery scenarios of my home infra where I straight up disconnect the modem's uplink and everything works without any issues.

[1] - https://github.com/bluenviron/mediamtx

[2] - https://github.com/seydx/camera.ui

So you want the server to make an HTTP call to an endpoint to deliver when streams change their status?

https://github.com/bluenviron/mediamtx/issues/1462

Looks like there might be a work around.

How low delay do you need? I'd recommend MediaMTX + VLC if you just want a live feed. motionEye could work too but it's very demanding on both the server and clients.

Have MediaMTX configured with a path for publishing:

so here's my next problem, to run ffmpeg from inline in mediamtx you have to build a new docker image that combines them. Aler9 gave instructions for the Dockerfile here: https://github.com/aler9/mediamtx/discussions/278

The one Docteh brought up is a good one https://github.com/aler9/mediamtx, I just set it up and all I had to do was change one line in the yml config file in the rtsp section to get that to work.

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