- cross-posted to:
- opensource@lemmy.ml
- jellyfin@lemmy.ml
- cross-posted to:
- opensource@lemmy.ml
- jellyfin@lemmy.ml
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.jsonAfter migrating please perform the following steps.
Perform a full library scan to restore alternative versions Run the "Optimize database" scheduled task___
You must log in or # to comment.
Let me guess, another price increase.
I can confidently say that the Jellyfin team intend to raise the price 10x the previous price.
Those bastards! I knew it!
Plexing their muscles, as usual.
Thank you for the reminder to donate to them <3
The price increased 4 times over the previous price.
Jellyfin is free. What price? :D
That’s the joke.
$0 x 4 😡😡😡
I think they’ll increase the number of ads
Now THAT is a changelog.
Really excited about the query performance improvements, and the improvements to subtitle handling.
I’m wondering if this has anything to do with the team lead changing?
A big push in features that had been waiting on the back burner?
Can’t speak to that, I’m not involved. All I know is that,
- Jellyfin server gets significant upgrades in subtitle capabilities and performance,
- Jellyfin AdroidTV just released an RC that finally includes direct play for ASS/SSA subtitles,
- and on Monday, I FINALLY resolved a hardware issue (faulty cable) that made my Jellyfin almost unusable whenever ASS/SSA needed to be played (and only in that situation. Fun!)
So yeah, I don’t know or really care about leadership change, I just know it’s gonna run like a rocket now 😄
I’m so curious what the cable was and how it affected only ass/ssa subtitles?
Haha. Might have slightly exaggerated. But only slightly.
The Proxmox host in question has a 1Gbit connection to the NAS. (Unfortunately. The other hosts don’t have a GPU, but SPF+… Oh well, can’t have everything.)
At some point in the last couple of months, it must have been damaged, and negotiated down to only 100Mbit. This must roughly have coincided with the Jellyfin 10.11 update, since I remember thinking that it must be the cause, due to close proximity of update and first issues.
Anyways. For basically everything in my library, 100Mbit is fine. Streaming an episode NAS->Jellyfin and Jellyfin->TV at the same time basically never saturates the link.
BUT, from what I’ve gathered by digging through Jellyfin issues and PRs, there’s a separate issue where Jellyfin will pull the episode, and if you need subtitles extracted from the episode file server-side (to transcode them in, if the clients can’t play them), it will at the same time pull the episode AGAIN, and together with the Jellyfin->TV direction, that’s frequently enough that it saturates the link.
Symptoms is (was) either a 20-30s wait before the episode would start playing, or complete freeze.
However, I believe this particular issues has been solved for a while. I’m not sure, because I instead opted for the Subtitles Extractor Plugin, which runs nightly and pre-fetches all the subtitles and stores them on the Jellyfin VM itself.
Where it was still noticeable though was if one of [Library Scan/Trick-play Extraction/Subtitle Extraction/Media Segment Scan] ran while playing an episode, the server would completely lock up.
Long story short: cable swapped, 1Gbit, all issues gone.
whoops!! that’s an interesting overlap of issues! glad a new cable did the trick (and that jellyfin fixed that).
I’m so happy that I got the 253 years subscription.
Ha! Shows what you know. I got a 256 year subscription at only 10x the price!
Wao, I got ripped off. I’m a fucking moron.
best money I’ve ever spent
The reason is the feedback we got after 10.11.0, which we first raised in January and confirmed in May. A release like 10.11.0 was, by any reasonable measure, a major release - it rewrote the library database - but the version number presented it as a minor update, and people upgraded with expectations to match. The leading 10. never changed and never told anyone anything, so all it did was push the number that actually mattered into the middle position and make “major” releases look minor. Dropping it means the first number moves when the release is big.
lol. All the Jellykins in here lost their minds when this was pointed out.
I dont get why they didn’t just call that update 11.0? Or use that for this update?
I guess if you’re changing the semantics of your version numbers its also a good idea to introduce a deliberate discontinuity to mark the change?
I was confused too, but I guess their logic is that 10.11.x is 11.x.x. They might have been more explicit about that.
This one goes 1 more than 11
My guess is that people would call the 10.11.x update something like .11.x instead of the full version because “they don’t change the first number anyway” and it would cause confusion to call the next update version 11.x.x so they just jumped to 12
Multiple versions for episodes
❤️
Edit: so I have two libraries, 4K and HD because of different viewing locations. Transcoding 4K to HD is not an option, hardware is too slow for that.
Now my multi quality tvshows get combined into one “view” per show which is nice. But it seems it still shows seperate episodes per quality and does not track viewing progress yet sadly or am I missing something?
Can you in theory set the servarr stack to fetch multiple languages of the same media now, when available?
I don’t think seer, sonarr, or radarr support that but in theory could. You’d also need your sources to have a good way to supply those details in a good way as well. I wish they had a good way to filter for languages now as I hate dubbed anything.
I don’t have the arr stack now, but when I fiddled with it a year or two ago I had to set one language. I ended up scrapping it because of it and just continuing with the streaming services. I also hate dubbed anything, but have small kids who want to see their shows in Norwegian. Switching them over to English on shows or movies they already know in Norwegian would be a great way for them to learn. Maybe I get to watch the Disney movies in English with them finally.
The annoying but workable answer is to run two instances, one for each language.
Sorry, but why not just fetch a single media file with multiple languages?
Of course, if it is available then that would be a good option. But if not then I would want it to download one of each.
My wait for OIDC support for sensible client logins continues
I know it’s not the same but quick connect works well. Why not log in that way using a six digit code?
Couple reasons.
- Jellyfin is not security software, and given the inconsistency and general lack of polish of every other aspect of Jellyfin, its raw login page is not something I’d comfortably expose to the internet to begin with.
- Quick connect is a poor, unintuitive imitation of Device Flow. A non-technical user would have to also have a Jellyfin app or bookmark in their phone already, and know where to navigate in it to reach the quick connect function. This on its own is insurmountable.
- It’s not SSO. Jellyfin is yet another username and password they must remember when every single other thing I self host supports OIDC out of the box and they get one user account for everything.
Fair points. Thanks for the lesson. TIL a lot.
Man, I really appreciate so many good folks giving info and not flaming each other. This is a great community.
Its about safety not just ease of use
I agree with you but also about 90% of watching on my instance happens on smart TV’s. So even though I would like to have oidc supported for the occasional phone/pc user I would still need something basic that a TV can use.
Smart TVs should be able to support OIDC easily out of the box.
And if it didn’t, you can just use a Device Flow
What a great software
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System NAS Network-Attached Storage Plex Brand of media server package SSO Single Sign-On VPN Virtual Private Network ZFS Solaris/Linux filesystem focusing on data integrity
[Thread #98 for this comm, first seen 8th Sep 2026, 17:10] [FAQ] [Full list] [Contact] [Source code]
Good bot.
Is anybody who updated already using Findroid? Just wondering if the update breaks anything in terms of 3rd party apps.
Edit a few days later: made the plunge and can confirm Findroid works without issues.
How do you get this to work remotely easily for old people on smart tvs?
Tailscale is a pretty good option if said old people have an Android or Apple TV, not sure about availability of Tailscale on any other OSs. Run it on your server and the TV client, grab the Tailscale IP from the dashboard and enter [Tailscale IP]:[Jellyfin port] when the Jellyfin app asks for the server address. You could homebrew a VPN too. Only other option would be a domain name and a reverse proxy.
Only other option would be a domain name and a reverse proxy.
This is how I set it up for my family and friends. Works like a charm, especially if you have a dynamic IP. Everyone just signs in through whichever app they want to use.
this is the way imo. I also took the time to disable internal authentication and hook up authentik via the ldap auth plugin. so for my users, I can text them a link, they set up their credentials and verify their email, then they can sign in to jellyfin with the same creds and it automatically creates a profile and everything.
Same, I had enough people I wanted to have access to it that I didn’t feel like explaining Tailscale to all of them. Also, you can’t easily run Tailscale alongside a regular VPN like Proton or Mullvad. Of course, you have to pay for the domain name and setting up a reverse proxy and appropriate DNS forwarding rules are not trivial tasks.
Domain + reverse proxy. The security issues some people here claim are significantly overblown.
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.
You could just upgrade, I assume RAM is cheap, haven’t looked in a while, just let me look up memory prices real quick…
They died from the shock. 😔
deleted by creator
If it’s direct play, this makes sense, but it sounds like maybe they are transcoding video
@Statick
That’s what I thought…
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.
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%
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 -mshows Jellyfin using maybe 2 Gigs.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
JF uses south of 480 mb right now on my rpi4 2gb when idling. It plays fine too, though struggles with transcoding.
I think you’re accidentally transcoding something
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.
I’ve been running the RC’s, smooth sailing in all regards.
Using Wholfin as my main client on all compatible devices, works great.
I’ve tried multiple Jellyfin apps for TV and all but VoidTV refuse to play Atmos with DV. 5.1 works, but 7.1 doesn’t. Including the offical Jellyfin app. It’s odd because it used to work until it didn’t.
Same here with DoVi profile 7. I installed CoreELEC on a USB stick and boot my player (Xiaomi TV box 3) from that if I need DoVi 7. My guess: Anyone setting up and maintaining a JF instance should be comfortable doing the same.
Out of interest I checked again to see which app works with Atmos 7.1. Offical Jellyfin AndroidTV app and Wholpin trigger transcoding on the server. VoidTV and Moonfin play it without an issue. I know there’s an open issue on the Github somewhere, but I don’t think there was any progress there.
True, it gets mushed into HDR10, afair.
We both might have found the same ancient GH issue. :)If I remember correctly, I’ve tried different client options as well, but had other issues with them, like missing audio after pause/resume, not switching to selected audio track and so on.
Also, none of them were able to play DoVi FEL and fell back to MEL.
Might be my player / Android TV restriction with my specific player, but with CoreELEC on the same box, FEL is fully supported and is a significant improvement, IMHO.there are only a small handful of devices that can fully decode FEL, regardless of the software you run on it.
That’s not going to change untill we manage to completely crack it and decode it in software or figure out how to bake it in via some kind of transcoder.
What are you trying to tell us?
Ho ! Thanks, I was quiet pissed with the way Jellyfin on android TV was so slow (maybe the embeeded android is to blame), I will try Wholfin to see if anything enhances
Ok, I tried it yesterday, I can’t thank you enough, it’s fast, clean, and I won’t go back to the stock app
FINALLY. it’s been so many candidates and every one has so many bug fixes
I wish they’d fix the screen off while audio plays on android issue.
Try Findroid. I found it to be a better overall experience.
Or if just looking for a solution too music, Finamp is pretty good as well
I’ve been using Jellyfin for years, on different hosts. Music has never worked on any of my devices - there’s a bug where you try to play a track and it ignores you and plays the first track off the album instead. You can literally never play anything after that. To be fair, I haven’t tested this in six months, but it was a consistent bug for years before that and I’ve tried every client under the sun. Nowadays I use Jellyfin for video and Navidrome for audio instead and it’s all good.
i wish they’d fix the black screen and not returning to home after episode ends issue/feature, and also not being able to scroll after manually returning home. can’t use old enough versions anymore where it still worked right (2023 versions and older i think)
Are there different hardware requirements? I’m running on a raspberry pi 4, and as soon as it tries to load my movies the entire server crashes. This happened with the first release candidate, but seems to still be happening.
Did you report the issue?
Was able to fix it. The initial library scan caused the server to crash (ran out of resources) so every database load would make the server crash since the initial scan never ran. The solution was to turn off the other containers I had running, then run the scan, then turn everything on.
Nice
Not yet. I’ll have to mess with it more when I get home tonight.
