Hey, I’m using Jellyfin and AndroidTV as client.

Everything is usually working fine using direct play. But for a few files, when using subtitles, I will get the message “burning subtitles” and the server will start transcoding it. I haven’t really figured out what format is causing it, but it only happens when enabling subtitles.

Anyone else having this issue? Can I do anything to fix it?

  • PetteriPano@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    27 days ago

    The Android client seems to have dropped a few player engines in a recent update. Previously there was an option to use libvlc, omxplayer or a third option that I can’t recall. Seems the developer opted to go with the worst option.

    The AndroidTV app can use external players such ss VLC. I went with kodi as a client instead.

  • just_another_person@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    27 days ago

    It’s not an issue, it’s expected behavior for transcoding when subtitles are in the original format.

    You can disable subtitles burning while transcoding, or you can try and find a different client that will use subtitles from a file, but it’s probably going to be hit or miss, and require a bunch of upfront work.

  • isgleas@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    27 days ago

    I’ve found that as well with some files. At first I thought the issue was with the jellyfin instance had not enough capabilities, but after trying the same file with its subtitles, it worked on any other client: flatpak, web, and regular android. So for me it is the chromecast/androidtv device, so I am now looking what to replace it with