• TimLovesTech (AuDHD)(he/him)@badatbeing.social
    link
    fedilink
    English
    arrow-up
    3
    ·
    25 days ago

    I think the transcode part is decided by the client, but in the Jellyfin server admin you can control if a client can request a transcode (which may not be actually needed - and if you know what client they are running it’s probably easier to decide). This could just be client setting though, because I know on Jellyfin you can change the “backend” in the client that it tries to use and can make the difference on things like x265/HVEC playing back or not.

    • Dhar@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      24 days ago

      Hmm, I’m not sure that’s the case here. I tried this with two different browsers (Firefox & Chrome) on two different computers, plus the native client on an Android phone, Android TV, and Android tablet, with various server settings - none of them worked.

      • TimLovesTech (AuDHD)(he/him)@badatbeing.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        23 days ago

        Yeah, sounds like the more mature Plex backend might just be better for your use case. But just because I’m curious are you running Jellyfin as an app or in docker? And is your Synology Intel based or AMD, as the latter will only do software transcoding and probably easily overwhelm a NAS CPU.

        • Dhar@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          20 days ago

          Running as a socket container - I don’t think there’s a native Synology package for Jellyfin. This is an Intel Synology.