JBOPS VS Exoplayer

Maybe not with stock Plex, but Tautulli with the JBOPS scripts should be able to do it.

I've been running the killscript to stop 4K transcodes for years, and I've just noticed that it doesn't work any longer. When it's triggered, I get the following error in Tautulli logs:

I am attempting to limit stream auto play at night and I found this limiterr python script was the only option that seems to be available running on tautuilli.(https://github.com/blacktwin/JBOPS/blob/master/killstream/limiterr.py).

I recommend using Tautulli and this https://github.com/blacktwin/JBOPS/tree/master/killstream to automatically kill streams. Also configure it to reference https://mediaclients.wiki whenever it kills the stream so users know how to fix it.

What about this script https://github.com/blacktwin/JBOPS/blob/master/utility/merge_multiepisodes.py

Tautulli for monitoring and notifications, plus some scripts for "maintenance," such as killing 4K transcodes and stopping remote streams after they've been paused for X minutes. These are from the JBOPS repository.

Script: https://github.com/blacktwin/JBOPS/blob/master/reporting/streaming_service_availability.py

Unless someone has already created what you're looking for (JBOPS/reporting is a good initial place to look), you'll probably have to write something yourself that makes calls to Tautulli's API.

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.

If one day https://github.com/google/ExoPlayer/issues/3438 is done then yes. Until then no I can't.