[Issue]: [Fire TV App] mkv embedded subtitles not showing up for some files

[micadam]

Please describe your bug

Hi, I'm having an issue with not seeing subtitles embedded in some (not all) .mkv files, in the app version jellyfin-androidtv 0.15.11 release. When comparing the file metadata available under "debug options", I don't see any major differences. I'm attaching details from an example file that works, and an example file that doesn't.

I tried various combinations of transcoding, exoplayer, libvlc, etc, and the one constant is that subtitles do not show up for those specific videos. The subtitles do show up in the web app (including in the web browser on my fire tv), and in the Android app on my phone (2.5.2).

My server information from the dashboard:

Server: raspberrypi
Version: 10.8.10
Operating System: Linux
Architecture: Arm

Jellyfin Version

10.8.z

if other:

No response

Environment

- OS: Linux raspberrypi 5.15.32-v7l+ jellyfin/jellyfin#1538 SMP Thu Mar 31 19:39:41 BST 2022 armv7l GNU/Linux
- Linux Kernel: see above (I think)
- Virtualization: Docker
- Clients: Fire TV app 
- Browser: various
- FFmpeg Version: ffmpeg version 4.3.6-0+deb11u1+rpt2
- Playback Method: direct play, mostly
- Hardware Acceleration:
- GPU Model: None
- Plugins: None
- Reverse Proxy: None
- Base URL: 
- Networking:
- Storage:

Jellyfin logs

No response

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

Does work:

Does not work:

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[micadam]

Worth mentioning is there is a subtitle switcher in the player, and in the videos that work it works as expected, whereas in the videos that don't it's always turned to "subtitles on (embedded)", and I can't change it. When I re-select "subtitles on (embedded)", it just says "burning subtitles into the video, it might take a few seconds" -- this is regardless of whether transcoding is enabled or not.

[jellyfin-bot]

This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.

If you have any questions you can use one of several ways to contact us.

[corigne]

Any word on what causes this? I have the same issue on jellyfin-androidtv 0.16.4 on a newer FireTV 4K.

[fockboi-lgtm]

Yeah, seeing the same issue (Can share some logs if required)

[jellyfin-bot]

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

[corigne]

If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

Still affected by this.

[jellyfin-bot]

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.