10.11 first library scan will take AGES because of the new db changes or something. My library is huge (~100tb of media) and it took days. Subsequent scans are much faster, like 10-12 minutes on 10th gen Xeon (roughly i5 equivalent) for a full library scan.
Comment on State of the Fin 2026-01-06 | Jellyfin
avidamoeba@lemmy.ca 3 days ago
Just upgraded from 10.07. Seems to have gone well. Library scan still going.
ragebutt@lemmy.dbzer0.com 2 days ago
avidamoeba@lemmy.ca 2 days ago
Fucking hell. OK, I’ll upgrade again and wait longer. Mine’s ~15TB.
ragebutt@lemmy.dbzer0.com 2 days ago
Do you have music? I don’t know this for sure but I also wonder if music collections slow things down. My music collection is pretty massive (like 40% of my storage) and it’s a shitload of files to index.
Thankfully I don’t put my books in jellyfin because my ebook/manga library is also pretty massive. If the apocalypse occurs I’m set for the 2-3 days I’d have power after the end of times
avidamoeba@lemmy.ca 2 days ago
I do. It could be this:
After the migration it is recommended that you perform a full scan through the admin dashboard. We have observed that for some users, some elements might not work properly otherwise (e.g parental ratings). As of RC8 a scan for missing metadata may be required for music libraries to function properly. The first scan after the migration might also take quite a bit longer than usual, though subsequent scans should be as quick as before.
From the release notes.
Cyber@feddit.uk 2 days ago
Wow.
Ok, I don’t have anywhere near that amount of media, but MythTV takes seconds to rescan ~2TB of videos and maybe a minute to get any missing details like fanart, etc.
Similar amount for music - but I feed it the files after I’ve run them through Picard.
I’ve not done a complete rescan of eveything for ages, but from memory it’s like an hour absolute tops. More like ~30 mins.
And that’s on an underclocked CPU (for quietness).
ragebutt@lemmy.dbzer0.com 2 days ago
I found the link
“Library scans are expected to take (way) longer in 10.11 because we are now a) properly validating all existing data and b) properly applying concurrency limits. Usually only the first scan after the upgrade takes significantly longer because it will fix some data inconsistencies we can not repair while doing the initial migrations. Any subsequent scan should be faster but if you add a lot of new files it will still take longer than before because of the concurrency limit.”
github.com/jellyfin/jellyfin/issues/15070
From the thread for people with more realistic media libraries like yours (5-20tb) the initial scan is more like a few hours. However, if you’re like me and hoard shit expect it to potentially take days
Lonewolfmcquade@lemmy.world 2 days ago
Thanks for this. Good to know! I haven’t taken the leap yet. I’ll plan the upgrade when we will be on vacation…
LifeInMultipleChoice@lemmy.world 3 days ago
I was using Jellyfin it to watch old episodes of Sherlock Holmes last night, during a break we switched over to playing a few songs I had thrown on there. The interface for movies and shows seems great but my spouse asked me, “why is there a shuffle option for shows?” To which I said idk, maybe if someone watches something like family guy it doesn’t matter. But then when we were under my music section, I couldn’t for the life of me figure out how to use shuffle. It was probably user error, but it seemed strange
h0rnman@lemmy.dbzer0.com 2 days ago
Looks like when you’re in a “mixed Playlist”, whatever that means, the shuffle and loop buttons are removed from the interface of the audio player (AudioPlayerView.bs:148-159). I’m not sure why that is, but it seems like it’s deliberate.
1hitsong@lemmy.ml 2 days ago
A mixed playlist is a playlist of mixed media. Movies, shows, audio, etc. all mixed together in a single playlist.
LifeInMultipleChoice@lemmy.world 2 days ago
Yeah, apparently it’s top/center for Android and web based, and not present for Roku. But thank you for that information. The other person who responded made me investigate. So I need to find the person earlier who said they program the Roku one, and suggest shuffle for entire music playlist., also make a donation lol
1hitsong@lemmy.ml 2 days ago
Which client were you using? Android? Roku? etc.
LifeInMultipleChoice@lemmy.world 2 days ago
I run the server from Mint, play from Roku client. I have a copyparty server set up on that mint sever as well, and we resorted to pulling up the website and having a 80s competition, trying to top the other but not by much so we didn’t go to what we thought would be the best song right aways, which we played from our phones so the other could scroll and look. Hers Samsung, mine Motorola, so both android
ohulancutash@feddit.uk 3 days ago
For me it was far too hungry on CPU at “idle”.
bonenode@piefed.social 2 days ago
I got a issue that it keeps my servers hdd awake even when not in use. Hope they can fix that soon.
besbin@lemmy.ml 3 days ago
10.11 is still a hot mess for large home media collection. Especially one with images mixed in. The team doesn’t even seem to prioritize fixing all of that before moving on building new features. Music collection are also slower and albums meta don’t load correctly anymore. I would hold off from fully converting to it if you have a large collection
avidamoeba@lemmy.ca 3 days ago
I do have a large collection and I haven’t checked the music lib state yet. I have a zfs snapshot from before the upgrade so I could restore if shit hits the fan.
kumi@feddit.online 2 days ago
SWIM has a sizable aged library - wouldn’t be surprising with sqlite db corruptions by now - and absolutely no issues smoothly upgrading to 10.11. Had sweaty upgrades a few times over the years but this was not one of them.
timbuck2themoon@sh.itjust.works 1 day ago
Honestly it’s a testament to the devs that it mainly worked for most people as well as it did.
Like kudos to them. That was a huge, huge migration to a different library/format and they pulled it off.
ragebutt@lemmy.dbzer0.com 2 days ago
I honestly found it much better to create a new db for 10.11 vs migrating. Both took about the same amount of time but the fresh db has no issues and the migrated db has some hiccups like you described (and some others). Main downside is you lose watch status