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.
You must log in or register to comment.
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.
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! :)
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?
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.
Thanks, so the goal is better performance? I’m not keep on testing betas but more performance, when the update is stable, is always nice
this is a “beta”, the 2nd Release Candidate. they’ll mark a stable version when most of the bugs have been ironed out.
There was a typo in my previous comment, I’ll definitely wait for the stable release.
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.
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.
Thanks for pointing out these changes. I’m curious, which plugins are you fond of?
If you use compose, you could use a version tag.
Good thinking, I’ve now switched to
:10.10instead of:latest.
