Jellyfin 10.11.0 RC2 now available (github.com)
from Untold1707@lemmy.zip to selfhosted@lemmy.world on 15 Jun 17:08
https://lemmy.zip/post/41446530

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: 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.

#selfhosted

threaded - newest

Lemmchen@feddit.org on 16 Jun 02:09 next collapse

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.

Gerprimus@feddit.org on 16 Jun 03:53 next collapse

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

Lemmchen@feddit.org on 16 Jun 14:55 collapse

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

pirat@lemmy.world on 16 Jun 06:00 collapse

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

Lemmchen@feddit.org on 16 Jun 14:54 collapse

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.

CybranM@feddit.nu on 16 Jun 06:28 next collapse

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?

zaphodb2002@sh.itjust.works on 16 Jun 07:38 collapse

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.

CybranM@feddit.nu on 16 Jun 07:52 collapse

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

ShortN0te@lemmy.ml on 16 Jun 08:12 next collapse

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.

WhyJiffie@sh.itjust.works on 16 Jun 08:40 collapse

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

CybranM@feddit.nu on 16 Jun 09:10 collapse

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

Einhorn@feddit.org on 16 Jun 09:03 next collapse

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! :)

NanoooK@sh.itjust.works on 16 Jun 23:34 collapse

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.