Exoplayer VS MX_FFmpeg

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

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.

It seems it not yet supported by Exoplayer https://github.com/google/ExoPlayer/issues/6225

Google drive client with only one purpose that is to stream video files unlike the official app, this app streams the actual files instead of transcoded streams. This app is powered by [Google Identity SDK](https://developers.google.com/identity/sign-in/android/start-integrating) and [ExoPlayer](https://github.com/google/ExoPlayer). Source code: [GitHub](https://github.com/itsZECHS/DriveStream)

Is there somewhere it's being discussed other than in https://github.com/google/ExoPlayer/issues/8435 ? Because it seems like they're actually working on it in there.

The ExoPlayer developers are theoretically working on implementing better support, but as they don't want to just use an existing library like libass to handle it and it's evidently pretty low priority, don't hold your breath on it happening upstream any time soon.

plex 8.28 had exoplayer 2.16.1. V 2.17 had a lot of changes. https://github.com/google/ExoPlayer/releases

On Android mobile, I just use MX Player Pro as an external player, with the MX_FFmpeg codec. Its pretty good.