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___



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,
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).