Exoplayer VS mediamtx

According to some people on the Internet [0][1], it is. Apparently, Java's (Android's?) Locale.getLanguage() is broken for Russian locale and instead of returning "ru" as the docs promise [2], it returns "русский".

[0] https://stackoverflow.com/questions/46916210/cannot-get-writ...

[1] https://github.com/google/ExoPlayer/issues/8251

[2] https://docs.oracle.com/javase/8/docs/api/java/util/Locale.h...

I tried using the Fire TV but it has huge problems with some 4K HDR video formats that goes black screen. It is an issue reported by multiple users for Plex but it's the same for all applications on FireTV. This is the issue on github for Exoplayer: https://github.com/google/ExoPlayer/issues/11096

Media3 is the new home for APIs that enable you to create rich audio and video experiences. If you’ve used libraries like ExoPlayer, MediaCompat, or Media2, you’ll find Media3 to be familiar. However, instead of using these separate libraries, Media3 provides a unified API for playback use-cases and also expands to cover new use-cases like video editing and transcoding. The APIs are simple to use yet powerful, customizable to meet your needs, and reliable and optimized so you can build for the diverse Android device ecosystem. (https://android-developers.googleblog.com/2023/03/media3-is-ready-to-play.html)

Haven't done video work in years, but checkout the DefaultTrackSelector and start following around in the source code. Android Studio should allow you to do this all in the IDE. It's really the only way to learn/understand this stuff.

Also in regards to having to tell PC rtspt:// and Quest rtsp:// and waiting for ExoPlayer to fail over to TCP (8 seconds delay) https://github.com/google/ExoPlayer/issues/11069

I wonder if it's an ExoPlayer bug?

See the full changelog of ExoPlayer 2.18.2. Some notable changes are:

This started happening on Android when they enabled DRM on the streams. Assuming you use a device with Android 12 or later, you can just use Race Control TV to fix the issue. With Android 11 or earlier, Race Control TV also stutters due to this issue, which can be fixed by a custom build of the the app and force-enabling the fix mentioned in the issue.

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.