• picnic ( picnic@lemmy.dbzer0.com ) 
    link
    fedilink
    English
    arrow-up
    9
    ·
    2 years 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!

  • mub ( mub@lemmy.ml ) 
    link
    fedilink
    arrow-up
    7
    ·
    2 years 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?

    • ShortN0te ( ShortN0te@lemmy.ml ) 
      link
      fedilink
      arrow-up
      4
      ·
      2 years ago
      1. Not sure what you mean by that. Jellyfin has had an up to date version in the play store for years.
      2. Yes every Profile is separated into its own account, that’s by design and will most likely never change. An easy PIN option in the local network existed for years. Now you can even login with your phone app by entering a displayed PIN.
      3. I remember very few media that i had issues with in the past. Depending on the transcode hardware you have some things can be tricky
      • EtzBetz ( EtzBetz@feddit.org ) 
        link
        fedilink
        Deutsch
        arrow-up
        1
        ·
        2 years ago

        I tried Jellyfin recently and for some reason it doesn’t play any media at all when I disable hardware transcoding, even though my media all is 1080 h264/h265 and I don’t want to scale. On Plex it always seemed like I could just play everything natively, but Jellyfin seems like it always wants to transcode.

        Even if I enable transcoding, stuff won’t play nicely because I’m currently on a Pi4 (going to switch in the coming weeks to a proper server), but Plex is fine.

        • ShortN0te ( ShortN0te@lemmy.ml ) 
          link
          fedilink
          arrow-up
          1
          ·
          2 years ago

          Basically, when you do not run server side transcoding and instead rely on client side support you will run from time to time into issues. Jellyfin does not have the ppl to get every client to work with all the different formats on every hardware.

          1080 h264/h265 does not say much about the media format. Those codec differentiate in things like Chroma (4:2:0; 4:4:4, etc) or in color depth like 8 or 10 bit. So not every h264 media file does run on the same hardware. Audio codecs are even more complicated.

          I think since i setup my hardware transcoding I ran into a not playable file once. But depending on the hardware it can be worse. On android TV you may have to play around with the settings.

          I understand that this can be a deal breaker for some ppl.

    • Trainguyrom ( Trainguyrom@reddthat.com ) 
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 years ago

      For the not all media played successfully, I found it was primarily down to transcode settings trying to hardware transcode file types my server can’t hardware transcode. It’s something worth playing with

  • Lemmchen ( Lemmchen@feddit.org ) 
    link
    fedilink
    arrow-up
    6
    ·
    2 years ago

    Many major enhancements to transcoding and playback, including support for software tonemapping of HDR10, HLG and DoVi, preliminary support for DoVi Profile 10, support for Dolby AC-4 audio, more stereo downmixing algorithms, QSV device selection, and more! Our FFmpeg is also now based off the upstream FFmpeg 7.0 release for additional features and improvements there.

    Does that mean no grey mess anymore when playing HDR files?

      • 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.

    • when did you last try it and what clients? I’ve got friends/family accessing my library and I see them playing back stuff constantly and never seen or heard of any issues. This is across web, AndroidTV, Chromecast, Roku and mobile devices.