SOLVED: Skipping ahead broken on Android TV - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: SOLVED: Skipping ahead broken on Android TV (/t-solved-skipping-ahead-broken-on-android-tv) |
Skipping ahead broken on Android TV - Gexuma - 2024-12-11 When attempting to seek further ahead in an episode or use the resume feature, the native Jellyfin Android TV player sends me back to the beginning of the episode. This issue is consistent on the same files but inconsistent between files, with some working correctly, however all are H.264. I'm running the Jellyfin Android TV client version 0.18.2 on a Xiaomi MIBOX4, Android TV version 9. My server is running Jellyfin 10.10.3 in Docker on Ubuntu Server 24.10. I've tested the same problematic episodes on the official iOS, Android, Windows desktop and web clients with no issues. Additionally, setting the Android TV client to use an external player fixes the issue. I have a logcat file including the issue but I'm unsure how to properly and securely share it. RE: Skipping ahead broken on Android TV - TheDreadPirate - 2024-12-11 Without seeing your logs and comparing how each client plays the file, it is hard to say what is going on. Usually this issue is caused by a poorly muxed file. Which can, usually, be fixed by remuxing with ffmpeg of mkvtoolnix. If your other clients, specifically, iOS, Android, and web, are transcoding this is essentially remuxing. Jellyfin Media Player uses MPV as the playback engine, and it is likely handling the bad mux on the fly. The Jellyfin app for AndroidTV uses Exoplayer, which is built into Android, and Exoplayer generally does not handle malformed files like MPV or VLC does. You can open a bash shell into the container to use ffmpeg inside the container to remux the file. Code: sudo docker exec -it jellyfin bash RE: Skipping ahead broken on Android TV - Gexuma - 2024-12-12 It seems that this has fixed it, at least for now! Thanks for the help. |