166
Jellyfin 10.11.0 RC2 now available (github.com)
submitted 1 day ago* (last edited 1 day ago) by [email protected] to c/[email protected]
13 comments fedilink hide all child comments

Jellyfin, the open source media server, has released their 2nd RC for version 10.11.0. This is a major version release that transitions to the new EF Core database mapper. Please read on for more info from the Jellyfin team.

We are pleased to announce the second release candidate preview release of Jellyfin 10.11.0!

This is a preview release, intended for those interested in testing 10.11.0 before it's final public release. We welcome testers to help find as many bugs as we can before the final release.

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

Important Notes & Features

Please see the WIP release notes here for now: https://notes.jellyfin.org/v10.11.0_features

PLEASE READ THOSE NOTES THOROUGHLY BEFORE UPGRADING; current RC1 users should have a seamless upgrade. If you have any questions, please ask in our Matrix chat.

See the GitHub link for more details and a full list of changes.

top 13 comments
sorted by: hot top new old
[-] [email protected] 2 points 13 hours ago

Improved dynamic HDR metadata handling. Properly detecting HDR10+ videos and selectively remove DoVi or HDR10+ metadata to avoid black screen on devices that only support a single type of dynamic HDR metadata.(This may require client side changes to function properly.)

Good, I have a lot of issue with HDR so hopefully this will improve the experience.

[-] [email protected] 10 points 1 day ago

I LOVE that the migration to EF Core is finally complete, as I assume this will pave the way to using postgres as a database option soon. Thanks to the team for all the hard work! :)

[-] [email protected] 6 points 1 day ago

I tried reading the features list but I'm just a layman, can anyone explain the most impactful changes this update will bring when it's stable?

[-] [email protected] 8 points 1 day ago

The EFCore change is pretty big. They're basically changing how the data is accessed from the database so that would touch most of the software, so potential for new issues is fairly high. Hopefully it will improve performance and concurrency. If you are not comfortable with potential issues, I'd hold off on updating for a while.

[-] [email protected] 2 points 1 day ago* (last edited 1 day ago)

Thanks, so the goal is better performance? I'm not keen on testing betas but more performance, when the update is stable, is always nice

[-] [email protected] 5 points 1 day ago

Performance is not the goal, but cleaner code and more manageable code. But both will ultimately lead to better performance. As of now it was basically impossible to change something in the database structure since it was hard to estimate the impact of it.

[-] [email protected] 4 points 1 day ago

this is a "beta", the 2nd Release Candidate. they'll mark a stable version when most of the bugs have been ironed out.

[-] [email protected] 2 points 1 day ago

There was a typo in my previous comment, I'll definitely wait for the stable release.

[-] [email protected] 11 points 1 day ago* (last edited 1 day ago)

I think I'll add an exception to watchtower, so my Jellyfin image doesn't get updated to the full release when it comes out. I'm really fond of my plugins and the fact that the "seen" status doesn't change when replacing the underlying video file.

[-] [email protected] 4 points 1 day ago

If you use compose, you could use a version tag.

[-] [email protected] 1 points 22 hours ago

Good thinking, I've now switched to :10.10 instead of :latest.

[-] [email protected] 1 points 1 day ago

Thanks for pointing out these changes. I'm curious, which plugins are you fond of?

[-] [email protected] 1 points 22 hours ago

I've just checked and apparently I only use first-party plugins, so I'd probably not have any issues. I'll still delay the 10.11 update for the other reason I mentioned.

this post was submitted on 16 Jun 2025
166 points (98.8% liked)

Selfhosted

46672 readers
1226 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]