New Jellyfin Server/Web release: 10.11.8

[Sea Monkey]

simply don't expose it online and use it locally only until it's fixed

Or put it behind a VPN, which is what you should do for anything you don't want the entire internet to have access to.  Just assume that anything that provides acess to your network will have security vulnerabilities exposed sooner or later, and act accordingly. 

I would absolutely upgrade if it were just a bit slower, but Jellyfin for Kodi can't even successfully sync my library on 10.11.x.  It's not my intention to dogpile on the developers, but I will echo the sentiment that this is more than a minor regression.  I'm eager for the release of 10.12.x, and hope for the best, but I will wait for others to confirm that everything is fixed before moving on from 10.10.7.

[matt1984]

simply don't expose it online and use it locally only until it's fixed

Or put it behind a VPN, which is what you should do for anything you don't want the entire internet to have access to.  Just assume that anything that provides acess to your network will have security vulnerabilities exposed sooner or later, and act accordingly. 

I would absolutely upgrade if it were just a bit slower, but Jellyfin for Kodi can't even successfully sync my library on 10.11.x.  It's not my intention to dogpile on the developers, but I will echo the sentiment that this is more than a minor regression.  I'm eager for the release of 10.12.x, and hope for the best, but I will wait for others to confirm that everything is fixed before moving on from 10.10.7.

Oh it is of course, but my point is still that 10.10.7 works whereas like you say 10.11 doesn’t. I’m in the same boat as you, I want upgrade but currently 10.11 is a downgrade compared with 10.10. Really hoping 10.12 /12 restores core functionality but given I lost 2 days waiting for my HV&P libraries to rescan in 10.10 after I downgraded last time I’m in no rush to go through tye long upgrade and full rescan again unless I know it’s working properly

[TIMFLIX1138]

I would absolutely upgrade if it were just a bit slower, but Jellyfin for Kodi can't even successfully sync my library on 10.11.x.  It's not my intention to dogpile on the developers, but I will echo the sentiment that this is more than a minor regression.  I'm eager for the release of 10.12.x, and hope for the best, but I will wait for others to confirm that everything is fixed before moving on from 10.10.7.

This is my situation and I wasn't aware that Kodi has issues with 10.11 (I should have been). So just waiting till 10.12 at this point. It will come and hopefully it will be a great success.

[Beban]

100%! This is spot on, 10.11 is fundamentally broken and there doesn’t seem to be any acknowledgment that it is actually on the radar to fix.

no, this is not true. 
devs are aware of it and made statement on jf's reddit sub too about how recent releases primarily focused on fixing long-standing security holes than improving performance. the fix you are waiting for will be applied on upcoming v10.12.

be patient. after all, being able to use a secure server is more important than loading libraries in a shorter time.

I dare to disagree. Safety is useless when the app is not usable at all. I'd rather have a working app, because I can take care of securing it (I access my LAN from the outside via VPN anyway, I don't expose my data to the internet), than have a secure app, which however does not do what I expect it to do (basically is slow to the point it's not usable).

[TIMFLIX1138]

2 things can be true at the same time. Safety is vitally important. Functionality is as well. We are stuck in the middle of those 2 dynamics at the moment (those of us who aren't easily able to upgrade) and it comes down to which of the 2 issues is the lesser importance to the individual.

That doesn't mean the people working on this aren't aware, understanding nor looking to make things better. There are other places out there whic hARE doing essentially that, ignoring the user base outright and pushing their own agenda forward no matter how much it will cost them. I don't get that from the JF team at all. But for them sometimes what best is to say less than some might want (demand).

[PJ R.]

100%! This is spot on, 10.11 is fundamentally broken and there doesn’t seem to be any acknowledgment that it is actually on the radar to fix.

no, this is not true. 
devs are aware of it and made statement on jf's reddit sub too about how recent releases primarily focused on fixing long-standing security holes than improving performance. the fix you are waiting for will be applied on upcoming v10.12.

be patient. after all, being able to use a secure server is more important than loading libraries in a shorter time.

It's 100% true, I've not seen anywhere any confirmation that the HV&P is on the radar to be fixed (feel free to show me a link that proves otherwise). 
As the previous poster said, it isn't that the libraries take a long time to load - it's that they don't load - they're non-functional. Restoring this functionality isn't "improving performance" as you call it, it's fixing what was completely broekn. This is exactly why the previous poster said, people just make out it's a minor issue. It isn't. I'd suggest that a media server that isn't able to serve media is more of a fundamental issue. The security issue, simply don't expose it online and use it locally only until it's fixed. The inability of the media server to serve media, no amount of not exposing it to the internet is going to fix that!

It's actually 0% true, thanks.  The devs already acknowledged your issues.  The libraries load just fine for me, they don't load for you.  That's not non-functional for everyone.

[User 22046]

2 things can be true at the same time. Safety is vitally important. Functionality is as well. We are stuck in the middle of those 2 dynamics at the moment (those of us who aren't easily able to upgrade) and it comes down to which of the 2 issues is the lesser importance to the individual.

That doesn't mean the people working on this aren't aware, understanding nor looking to make things better. There are other places out there whic hARE doing essentially that, ignoring the user base outright and pushing their own agenda forward no matter how much it will cost them. I don't get that from the JF team at all. But for them sometimes what best is to say less than some might want (demand).

You don't seem to get the point, it is NOT about "in a shorter time" for the ones complaining, its about THEY DO NOT OPEN AT ALL RIGHT NOW.

Again for the 10th time, it is not "click on library" -> wait 3 instead of 8 seconds (This is what your post seems to refer to)
It is "click on library" -> wait 1 HOUR and depending on size it's still loading and will NEVER OPEN.

There is no dynamic balance if it does not work. If you need a calculator for your exams and someone hands you a bible saying there are no security holes in it, that's not a logical balance thats nuts.

It's actually 0% true, thanks.  The devs already acknowledged your issues.  The libraries load just fine for me, they don't load for you.  That's not non-functional for everyone.

... This is just ragebait at this point right?

Can you link to the post where this issue is acknowledged by the devs or a upcoming fix for it is mentioned (Nested Sub-Folders, infinite loading)?

Here is the existing issue (many more have been closed due to duplicated and linked to it): https://github.com/jellyfin/jellyfin/issues/15141 thread
The main proposed fix is https://github.com/jellyfin/jellyfin/pull/16366:
this person seemed to had the best grasp (look at the time improvements he had!!!)

The previous commit addressed the GroupBy anti-pattern but the real
bottleneck remained: FillUserDataDtoValues runs a recursive unplayed
count query for EACH folder item in the response. For a books library
with 37 author folders, this meant 37 sequential AncestorIds-join
queries (~1s each = 35+ seconds total). Collections (BoxSet) had the
same issue with 69 items taking 42+ seconds.
[...]
Collections (69 BoxSets) Before: 42s After: 0.04s Factor: 1000x

And it was closed by the devs (NOT IMPLEMENTED) with this explanation:

"We already have a mega PR (#16062) that will serve as the foundation for the next major Jellyfin release addressing the performance issues related to the issue you linked.
Have you tested that PR, and how does it compare?"

The "MegaPR" https://github.com/jellyfin/jellyfin/pull/16062 is still open and in this megaPR mentioned under Effects:

Collection library API requests are now within usable response times (<2s)
Related items and folder queries (Series, Artist, Album, etc.) significantly faster - e.g. loading all 20+ seasons for One Piece down to ~2s from 7+

This does NOT mention the nested sub-folders, it's seems to adress other issues and was assumed nested folders fall under the same "performance" issue.
Also there is no mention of "FillUserDataDtoValues" which the first dev who tried to fix it mentioned, could be just me not finding it of course or it actually be unrelated.

But reality is all issues opened were closed / as duplicate and not directly adressed by the devs, they proposed fixes but none are specifically about NESTED SUB-FOLDER LIBRARIES but only mentioned through some other bug they were working on ASSUMING it would be fixed with them.

[matt1984]

100%! This is spot on, 10.11 is fundamentally broken and there doesn’t seem to be any acknowledgment that it is actually on the radar to fix.

no, this is not true. 
devs are aware of it and made statement on jf's reddit sub too about how recent releases primarily focused on fixing long-standing security holes than improving performance. the fix you are waiting for will be applied on upcoming v10.12.

be patient. after all, being able to use a secure server is more important than loading libraries in a shorter time.

It's 100% true, I've not seen anywhere any confirmation that the HV&P is on the radar to be fixed (feel free to show me a link that proves otherwise). 
As the previous poster said, it isn't that the libraries take a long time to load - it's that they don't load - they're non-functional. Restoring this functionality isn't "improving performance" as you call it, it's fixing what was completely broekn. This is exactly why the previous poster said, people just make out it's a minor issue. It isn't. I'd suggest that a media server that isn't able to serve media is more of a fundamental issue. The security issue, simply don't expose it online and use it locally only until it's fixed. The inability of the media server to serve media, no amount of not exposing it to the internet is going to fix that!

It's actually 0% true, thanks.  The devs already acknowledged your issues.  The libraries load just fine for me, they don't load for you.  That's not non-functional for everyone.

Where? Show me the link where they have acknowledged this issue and that it’s being worked on for the next version?..
You clearly don’t have the same volume of content and/or don’t have a nested organised structure because if you did you’d find it doesn’t work for anyone.

[EliteAlien]

I have the same issue with 10.11.X a lot of people have here. Though unlike most people, downgrading, I upgraded to 10.12.0 after 10.11.6 which just was complete hell to use. I don't remember the exact build number I started on with 10.12.0, but I've been through about six or seven builds now. It started off more stable than 10.11.X but still not good. Then after about two builds in I lost support for a handful of plugins sadly. Though improvements came, but out of curiosity I downgraded to 10.11.8 hoping it was better now, only for it to still be an absolute garbage fire for me. So I went back to 10.12.0 the build I was on before and the slowdown I got from 10.11.8 kind of stuck around like a plague. The next update of 10.12.0 it got a bit better but scans were still a bit slow but much better everything was faster, but "Media Segment" scans could literally take days even on 10.11.X and this new 10.12.0 and the lockups still happened.

All that being said, the latest build of 10.12.0 which is "2026050513" is like it's back to being 10.10.7 "almost". They seem to have added a initial scan of the database which removed thousands of duplicates the 10.10.7 to 10.11.X and/or 10.12.0 (old build number here) would make. Now my Jellyfin is snappy, doesn't hang, no more "Failed to load" on videos, server lockups, and so much more. The worst thing that happens is five blue circles randomly on some loads of video and the images on a season like "People" can sometimes take up to about five seconds to load at random. While other times it's perfectly fine. (It's kind of sad the "Unstable" is more stable than the so called "Stable". They really should have left this in "unstable" longer to iron things out, but anyway....)

TL;DR: Basically if you can live without a few plugins and/or don't use that many to begin with. The unstable 10.12.0 "2026050513" might be something you want to try. https://repo.jellyfin.org/?path=/server/...t-unstable or https://repo.jellyfin.org/?path=/server depending on what OS/Distro you are running.

Edit: It seems a few advanced features like LiveTV and photos are still bad on this build. So if you need these or every plugin, avoid "unstable". Otherwise give it a shot and see. Specially if you are like me with just using Jellyfin for movies, TV shows, and music mainly and nothing much beyond that.

[mtoss]

I did a quick test of the 2026050514 and was disappointed. New GUI is fine but 10.10.7 LiveTV streaming is much better. The same m3u stream tested with 10.10.7 is remuxed but in new version is transcoded. The same settings and the same client. What can I say more.
As for the Photos slide show, I like that we can now adjust it to our liking. I was able to adjust it but it will not safe. So it still remains as 5 seconds no matter what value you set.