Max Rumpf

Sorry for the late reply, it seems the higher bitrate is also transcoding. 62 fps transcoding framerate should normally be enough, but it could still be a server issue. Does...

I see, it's possible the server cannot keep up with transcoding, or it's a server bug. You should check the ffmpeg transcoding logs on the server, those could give a...

@nielsvanvelzen do we want to ignore this for now? I think it'd make sense to keep compatibility with 10.7 until at least the next release (whenever that'll be).

The problem with this is that Xvid seems to have the same codec string as mpeg4, thus we can't filter it out from the device profile. However, there's hope we'll...

Yeah, that's an issue with playing media in WebView. I couldn't reproduce it on my device, but it's definitely a thing. Long-term, we want to switch to a media player...

+1 for Gelli. The comment I made [here](https://github.com/jellyfin/jellyfin-android/issues/222#issuecomment-726865105) applies to this issue as well, that's why I marked it as `wontfix`.

I did some more digging, and it seems to be [an issue in chromium](https://bugs.chromium.org/p/chromium/issues/detail?id=1014614), which powers the Android WebView. We can possibly work around this if I understand some of...

The bug is very device and situation specific. I can still reproduce it on my Pixel 5, Android 11. The [upstream issue](https://bugs.chromium.org/p/chromium/issues/detail?id=1014614) also hasn't changed since I last commented.

I don't think it'll add new entries to the history when using Android Auto. It may simply show content played on other devices.

If you install [this](https://aur.archlinux.org/packages/mpv-mpris/) and softlink `mpris.so` to `/usr/share/mpv/scripts/mpris.so` in `~/.local/share/jellyfinmediaplayer/scripts`, play/pause and metadata works perfectly, both for music and video.