mediamtx VS firmware

I believe mediamtx can ingest the RTMP and present to a browser, via HLS or WebRTC.

https://github.com/bluenviron/mediamtx

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.

Contains closed source binary blobs. It’s commercial with open source components.

https://github.com/OpenIPC/firmware/issues/230#issuecomment-...

https://github.com/OpenIPC/firmware

You can get onvif-compliant firmware for some of those, but battery-powered operation cannot be expected to remain practical, given what onvif focuses on.

> Majestic code while is not open, provides unprecedented performance and capabilities for a wide range of hardware. The author of Majestic streamer is looking into possibilities to open-source the codebase after he secures enough funds to support further open development. You can help to make it happen sooner.

Source: https://openipc.org/

Crazy wide amount of chips supported. My main barrier would be that my current camera has nice hardware h.265 encoding. I haven't dug deep but whether I can keep that or not would be a potential deal breaker.

Github: https://github.com/OpenIPC/firmware

The OpenIPC project has more recent code for these chips (though even that seems to be 4.9) https://openipc.org/

Check out OpenIPC for custom opensource firmware on a variety of devices