Release 12.0 · jellyfin/jellyfin
github.com
🚀 Release notes for 12.0 Notes on Updating Before upgrading from an earlier version, a full backup of the data directory is strongly recommended, as this release includes database changes that prev...

cross-posted from: https://aussie.zone/post/36389875

Why jump from 10.11.11 directly to 12.0? -> Blog Post

You can find more details about and discuss this release on the official forums.

As always, please ensure you stop your Jellyfin server and take a full backup of your metadata/configs before upgrading!

Direct upgrades from 10.10.7 and 10.11.x to 12.0 are supported; intermediate upgrades are not required. Users running releases older than 10.10.7 are strongly encouraged to upgrade to 10.10.7 before migrating to 12.0.

Installed repository plugins (anything not built-in) should also be removed before migrating. Plugins will likely need time to adapt to the new database changes, so re-adding them afterward is the safest approach for testing.

Official plugins compatible with Jellyfin are available through the stable plugin repository. If you have changed to the unstable plugin repository please change it back.

Go to Dashboard -> Plugins -> Manage Repositories
Update the Plugin Repository URL to: https://repo.jellyfin.org/files/plugin/manifest.json

After migrating please perform the following steps.

Perform a full library scan to restore alternative versions
Run the "Optimize database" scheduled task

___

  • German The Jackal@pawb.socialEnglish
    131·
    2 days ago

    Any changes to the massive memory footprint of JF? I’m basically stuck on Plex because JF eats multiple gigabytes of my very limited RAM.

    • jj4211@lemmy.worldEnglish
      482·
      2 days ago

      You could just upgrade, I assume RAM is cheap, haven’t looked in a while, just let me look up memory prices real quick…

    • smiletolerantly@awful.systemsEnglish
      3·
      2 days ago

      Does it actually? My VM has a lot of RAM, and Proxmox reports usage always around 90%, but that’s no matter how much RAM it ACTUALLY has, because almost all of that is cache and not strictly necessary. free -m shows Jellyfin using maybe 2 Gigs.

      • German The Jackal@pawb.socialEnglish
        1·
        2 hours ago

        2 gigs is ludicrous for a glorified file server with built in ffmpeg, Plex has never used more than 200mb for me. Maybe I’m outdated but I find that pretty unacceptable. I wouldn’t care if I had 32 gigs, but I have 8 and most of that is occupied by other stuff like ZFS or buncha Docker crap

    • ohulancutash@feddit.ukEnglish
      2·
      2 days ago

      Yeah that mostly ironed out by 11.11.

      But its also a different philosophy where JF caches more in RAM than it did before, but that’s available for use by other proceases if needed.

    • Funkt4st1c@lemmy.worldEnglish
      7·
      2 days ago

      Only if either your app requires it to transcode. My cpu is maxed if i try to play off chrome on my phone, but the same file on the jellyfin app keeps it under 1%

      • German The Jackal@pawb.socialEnglish
        1·
        2 hours ago

        See, that’s a problem for me, because Plex uses anywhere between 20 and 200MB depending on what it’s doing. Mostly it idles at 50MB which keeps me very happy. When I tried Jellyfin fairly recently, it ate 1.4GB just to initialize and then promptly crashed my system. I don’t like to dunk on languages like that, but Python man… I don’t have that kind of luxury. It’s not just “cache” either, I wasn’t able to configure JF in any way where it wouldn’t crash, it’s certainly not “reclaimable” memory usage, it’s just a chunky program.

        I never even got to transcoding, it’s impressive, honestly, how fast it destroyed my homelab lol.

    • cholesterol@lemmy.worldEnglish
      41·
      2 days ago

      JF uses south of 480 mb right now on my rpi4 2gb when idling. It plays fine too, though struggles with transcoding.