New Jellyfin Server/Web release: 10.11.1

[Edhel]

I have done this before with the trakt plugin about 2 or 3 years ago. Exported my watch data from jellyfin to trakt, then with a fresh install, I imported all my watch data back in from trakt to jellyfin.
Do keep in mind that if you have multiple jellyfin accounts, you will need to do this for separate trakt accounts too.

[mtoss]

How did we end up with the official 10.11.x releases that have some major bugs?
Well, for one, and this is speaking from an extensive experiance (retired) we tried too many modifications all at the same time.
Then, releasing so many RC copies that IMHO never have seen on any platform or software. I tried few times to upgrade only to find that I basically cannot proceed to live with RC or any 10.11.x code.

We should never repeat that again. I hope PM learns the lesson. People would prefer small increments but tested.

[JohnDorian]

I also had major problems updating from 10.7 and had to give up in the end. I have now completely reinstalled Jellyfin and created all users from scratch. Since then, I haven't had any problems. Everything is running smoothly and well.

[matt1984]

I think it may’ve been better if the database migration had been taken out of the main application and made as a separate migration tool which produced the database file to be dropped in to the new version when installed?
It would be interesting to know how many people either tried to upgrade, failed and reverted or just read about the many issues and have decided it’s not worth the hassle when their existing setup works. As it stands I can’t see me moving from 10.10.7 which is a shame as some of the new features sounds good, but if it won’t scan without crashing without any obvious reason then it’s not serving and media.

[KodiUser1138]

Sounds like I should continue waiting to migrate my 2 managed servers over to 10.11. Appreciate the work to advance the cause but my head still hurts from previous upgrade issues.

[Necromind]

First of all I registered to say thanks for all the work went into Jellyfin yet. I really like it.
Regarding the 10.11.x update the upgrad as is worked for my library really smoothly and fast. I have a library in range of a couple thousend files.

But in the end I reverted back to 10.10.7 yesterday, after getting mad with some nasty problems.
First of all the "continue watching" topic is buggy. It doesn't appear in the main menu. The current workearound is, and I can confirm it, enable "continue watching" on all library topics and it will show up again. Just turn one of and it's gone.
The other major bug is, where I failed to find a fix for, the collections don't work. If I try to select collections, the spinner do it's thing, one core on the server gets load and never stops, as so does the spinner. Selecting collections again, another core gets load and the spinner runs... you can repeat this until the server is on 100% load.

Another side effect after upgrading was on the client side. The android app on my phone as like the app running on my andorid TV was struggling. On my phone the app won't load. Just the spinner made its thing. Clearing the app cache solved this effect. On the android TV the app won't login. Clearing the cache didn't fixed it, but reinstalling did the trick.

Overall I spend some hours of reading, fiddling around, server stopping, server starting... Sad to finally revert back, but I have some users not really familiar with such "computer stuff" and the support eats up too much time for me now. So I reverted back and will see what patches may come in the future.
I am totally aware such huge achitectural changes result in a lot of struggle in the first few weeks or month after such a release. But I really hope the devs can get the problems fixed somehow to give us a smooth update experience.

Well, long story short: I went back to 10.10.7 for now and hope the best for the near future. Cheers!

[beerman]

Jellyfin Rocks!

Only blocking issue so far with 10.11.1 is migrated library based on Folders view

This call times out 95% of the time. 
http://{server}:8096/Users/{userid}/Items?StartIndex=0&Limit=100&Fields=PrimaryImageAspectRatio%2CSortName%2CPath%2CChildCount%2CMediaSourceCount%2CPrimaryImageAspectRatio&ImageTypeLimit=1&ParentId={parentid}&SortBy=IsFolder%2CSortName&SortOrder=Ascending

[jellykrabbypatty]

The only problem I'm still having is my items do not update instantly when I make a change and I have to scan the entire library for a change to take effect. Also, unusually long library scans. I had luck earlier with FinAmp replacing the metadata for the entire library, so I might try that again for my other libraries to see if it's a weird logic issue with unupdated data.

UPDATE: Ok, I fully replaced the metadata on all my libraries, updated everything in scheduled tasks, rebooted, but it is still very slow as far as library scans, turning/opening pages, and image and custom metadata changes do not take effect unless I perform a full library scan. The "Home Videos/Photos" library types is VERY noticeably slower to open. Hopefully it gets patched up

[alike]

Metadata scanning for libraries is my biggest issue since updating, especially with music but overall the system is just slow at handling metadata now.

Anything to improve library scanning / metadata performance coming?

I am experiencing the same problems.

The guide for updating told us only to run normal library search after the update... but I had to run the whole find new metadata thing on everything (several times) before most of the titles came back. It was quite problematic the day I updated.

I had manually identified movies, music, and music video titles that have gone back to their original broken way after this update. Was this expected? I think I spent perhaps a couple of weeks in pure working hours on this work earlier.

There is a lot of just filenames on my titles now. Haven't seen that before.

Having issues where the sorting on the latest titles (based on sort on date added) is not correct on some video libraries now, after the update.

Fortunately, I do have backup from a couple of days before the update. I am keeping the new version for now and am happy to try to find out why I am having issues with it, if my involvement is needed.

I am reverting to 10.10.7 and using backed-up files and config until I read about the stability of this project again.
I can't have this instability right now. Have other things to do.

[tomstephens89]

Been running 10.11.1 for a few days now and the biggest issue I see is still performance/unreliable Library scanning/metadata management. Its very slow, unreliable, doesn't appear to be writing nfo's for everything scanned in that I add new.

Music library wouldn't monitor two folders, had to merge and add as one. Sorting issues as well it would seem.

I am holding out from reverting back as my library is large (70TB). I have faith in the Jellyfin team! I have been using Jellyfin for over 2 years and its been fantastic, this is a massive update and it would have been impossible to test everyones deployment scenario. There are some really poor installations out there on poor set ups.

However I am on bare metal, i7 13700k, 64GB DDR5, OS/JF on 1TB NVME SSD and media on an 8 disk RAID 0 of spinners.