You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.
Describe the bug
Since the Jellyfin Android TV version 0.18.x update, subtitles no longer work.
My library is composed entirely of WebM containers, with AV1 for video, Opus for audio and VTT for subtitles.
It doesn't automatically select any subtitle by default. If I go to the player settings under subtitles, I see both subtitle tracks available, but when I try to select one, nothing happens. If I revisit the settings, "No Subtitles" is checked again.
If I revert back to version 0.17.x, everything works.
I know that there was a complete overhaul of the subtitle handling between the two versions 0.17.x -> 0.18.x.
I read my videos in DirectPlay mode :
EnablePlaybackRemuxing: False
EnableVideoPlaybackTranscoding: False
EnableAudioPlaybackTranscoding: False
It might be related to WebM VTT format, as I haven't seen any ticket here regarding the issue.
No errors in the server logs.
Logs
No response
Application version
0.18.x
Where did you install the app from?
Google Play Store
Device information
TCL 43C635 2022
Android version
Android TV 11 (Google TV)
Jellyfin server version
10.10.3
Other sources
No response
The text was updated successfully, but these errors were encountered:
@aworan I have experienced the same issue although do not recall what subtitle format I had at the time. Selecting a subtitle displayed nothing.
I resolved this by converting the subtitles to SRT format. Clearing the default subtitle flag will let the user select a subtitle. Turning the flag on automatically plays the track. This is a good bit of work (reformatting the containers) but it was the only reliable way I got subtitles to work.
I’m experiencing a similar issue with subtitles not displaying, but my file format is different from the one described in this issue. Here are the details of my file:
Container: Matroska (MKV), not WebM.
Video Codec: HEVC (H.265).
Audio Codec: AAC.
Subtitle Format: ASS (Advanced SubStation Alpha), not VTT.
Despite the differences in container and subtitle format, I’m encountering the same behavior:
Subtitles do not display by default.
When I manually select a subtitle track from the player settings, nothing happens, and the selection reverts to "No Subtitles."
This suggests that the issue might not be limited to WebM containers and VTT subtitles but could also affect other formats like MKV and ASS subtitles. I’m using:
Jellyfin Android TV version: 0.18.4
Subs work on my android phone btw (but this is ofcourse is not using the android tv app)
Could this be a broader issue with subtitle handling in the 0.18.x update, rather than being specific to WebM/VTT? If there’s any additional information or logs I can provide to help debug this, please let me know.
This issue respects the following points:
Describe the bug
Since the Jellyfin Android TV version 0.18.x update, subtitles no longer work.
My library is composed entirely of WebM containers, with AV1 for video, Opus for audio and VTT for subtitles.
It doesn't automatically select any subtitle by default. If I go to the player settings under subtitles, I see both subtitle tracks available, but when I try to select one, nothing happens. If I revisit the settings, "No Subtitles" is checked again.
If I revert back to version 0.17.x, everything works.
I know that there was a complete overhaul of the subtitle handling between the two versions 0.17.x -> 0.18.x.
I read my videos in DirectPlay mode :
It might be related to WebM VTT format, as I haven't seen any ticket here regarding the issue.
No errors in the server logs.
Logs
No response
Application version
0.18.x
Where did you install the app from?
Google Play Store
Device information
TCL 43C635 2022
Android version
Android TV 11 (Google TV)
Jellyfin server version
10.10.3
Other sources
No response
The text was updated successfully, but these errors were encountered: