• picnic@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 days ago

    I really like JF.

    My biggest issue with it is that subtitles appear to be messed up timing wise upon continuing playback and its impossible to reset.

    But other than that, I like it a lot. Thanks JF team!

  • Alfaspyke@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    9 days ago

    I just recently converted from kodi to jellyfin after a Nas hardware crash. I run the server in a docker container on my Nas and the client on a Nvidia shield. Works great, but there is one niggle I haven’t figured out and had much better experience on kodi. Subtitles.

    I can’t seem to find any adjustments for the subtitles in case they don’t fit the video completely. There is no menu I have found that allows for adjusting the timing of subtitles.

    How are you all coping with this? I use the arr stack and get subtitles through bazarr.

    How do you all handle these things?

    • Flying_Hellfish@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 days ago

      Are you using subtitle sync in bazarr? I don’t use jellyfin, but have found that bazarr has fixed most of my subtitles that were not in sync just by enabling the option. I think it’s CPU intensive though, so don’t do the whole library at once.

    • Domi@lemmy.secnd.me
      link
      fedilink
      arrow-up
      1
      ·
      9 days ago

      Probably a bad time to suggest the Jellyfin for Kodi plugin (since they removed the network paths in this version) but it’s what I use for my main playback device.

      All the goodies of playback via Kodi but play state and metadata gets synced from Jellyfin.

      Another option of course would be to open the file(s) in MKVToolNix to add and correct the subtitle offset there.

      • damo_omad@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        8 days ago

        Is that the native paths method they removed? I never used it and didn’t understand the reason for it, but I’m guessing its useful for some users?

    • Aquatic_Melon@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      9 days ago

      Depends on the platform you’re using. Mobile you have the integrated player that doesn’t support subtitle offset and the web player that does. Everything else is a version of the web player basically and they all support subtitle offset

      • Alfaspyke@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        9 days ago

        Nvidia shield is a android device so it tracks that this is the mobile player without srt adjustment. That sucks though. Maybe I should look at kodi and jelly plugin…

        • Aquatic_Melon@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          6 days ago

          If it uses he android client there should be a setting to choose which player, at least with mobilie there is.

          On the client go to settings -> client settings -> video player

          It might let you change it, you’ll want the web player.

          • Alfaspyke@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            6 days ago

            Oh? Very interesting! I was not aware that this was available as a setting. Thanks for the heads up

    • Xariq@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      ·
      8 days ago

      It isn’t built in to JF; they just added a framework that makes the process easier. You’ll still have to use a plugin to skip intros.

  • mub@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    9 days ago

    I liked Jellyfin when I tested it last year but it had 3 show stoppers for me.

    1. Samsung app was flakey and had to be side loaded.
    2. Each profile had to use a password and had a full keyboard to enter. Needs a no password option, and a pin pad option.
    3. Not everything played successfully.

    Have any of these things been fixed?

    • Bronzie@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      9 days ago

      1: The official Android app didn’t work?
      That’s strange as I run it on a Samsung and Pixel straight from the PlayStore. What were your problems?

      2: This is not required as long as the profile is set up wthout a password.

      3: This depends on the client and codecs supported by it. Newer phones support most, or is able to transcode. Weaker/older units are not.

      • herrvogel@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        9 days ago

        They’re probably talking about Samsung TVs, not their android phones/tablets. Installing jellyfin on those things can be a chore. My experience with LG was similar. The official build was out of date and riddled with issues that didn’t exist on other versions. It refused to play videos that worked well enough on other devices, transcode or no.

        • Bronzie@sh.itjust.works
          link
          fedilink
          arrow-up
          2
          ·
          9 days ago

          That thought didn’t cross my mind, and you must be right.

          I’d say go for a streamer of some sort as a solution. Not had many issues on the CCWGTV.

  • blackstrat@lemmy.fwgx.uk
    link
    fedilink
    arrow-up
    0
    ·
    9 days ago

    Last time I tried it it was a much worse experience than Emby across all devices and for all media types. I don’t understand all the love it gets.

    • allywilson@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      9 days ago

      Worse how? Jellyfin was forked from Emby, and since then has continued to improve in my eyes.

      • blackstrat@lemmy.fwgx.uk
        link
        fedilink
        arrow-up
        0
        ·
        9 days ago

        It was forked but somehow lacked a huge amount of functionality that Emby had (and still has) Like I think it only supported films, not music or TV shows. The app infrastructure was awful across fire stick, Roku and android and wasn’t backward compatible with the Emby apps. I just didn’t see the point of forking it if you’re just going to make it worse or only address the server side and neglect the clients. The whole thing has to work together with good clients and server.

  • DaGeek247@fedia.io
    link
    fedilink
    arrow-up
    0
    ·
    9 days ago

    Shame about the network location regression. That’s the only thing that keeps my kodi device from taking 5-15 seconds to load each sub menu.

      • DaGeek247@fedia.io
        link
        fedilink
        arrow-up
        2
        ·
        9 days ago

        Network paths in libraries have been fully removed and will no longer work. This functionality has been deprecated for a long time, and most of it was removed in 10.9.0, but this removes the remainder. See PR #12446. Third-party clients relying on this functionality should be able to re-implement it as required.

        from the article.