ustreamer VS mediamtx

FYI until recently this was known as 'rtsp-simple-server', but it outgrew simply being a RTSP server so it was rebranded. It is commonly used in the 3D printing community for serving webcams attached to printers along with ustreamer (https://github.com/pikvm/ustreamer).

uStreamer is far superior to the mjpgstreamer utility that nearly everyone uses. It supports the Pi's OMX media encoder, so you can get reasonable quality with low CPU usage.

I've been in the same situation as you and have been looking into https://github.com/pikvm/ustreamer as an alternative to mpjg-streamer under Raspian Bullseye with the unicam driver and the Media Controller API framework.

Maybe look at https://github.com/pikvm/ustreamer

...the documentation includes an example for the rPi camera as well as simple steps for making it a service.

I've done work before where we stream USB cameras via mjpg using https://github.com/pikvm/ustreamer

Granted this project looks like a lot more streamlined.

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.