New Jellyfin Server/Web release: 10.11.5

[lolish]

@Derfel The mixed libraries option is legacy and probably should come with a warning not to use.

There is a post from 4 years ago on Reddit r/jellyfin from a Jellyfin Team member saying: "Mixed libraries are basically never the right answer. It's really hard for the scanner to correctly identify a media type based on a folder name, and support for them in clients is frustrating at best. That library option is mostly there for legacy reasons."

They go on to say: "it was there when we forked, nobody has removed it yet, and if we remove it now a small subset of people will revolt."

I appreciate the clarification, but I would ask how users are supposed to handle niche / independent content which maybe you don't expect there to exist public metadata for at all, and which doesn't fit neatly into the existing categories? For instance, I have a collection of instructional VHS/DVD/YouTube content (and another collection of academic lectures) ripped to my library, where some of it is serial and some is one-off. I would really like to avoid creating two separate "How-To (Movies)" / "How-To (Series)" libraries.

I don't necessarily need Jellyfin to fetch metadata and cover art for me; are there existing library types that support this use case? I really do think that, at a minimum, this use case should be acknowledged in the docs and forums, even if only to say "We don't officially support a way of doing this yet." Surely, I can't be the only one who has a whole collections of obscure media types that you wouldn't expect to find on tmdb or omdb?

(also congratulations to the devs on another release; always very grateful for the free software 🙇🏻)

There is "home videos and photos" library type which I use for a use case similar to yours.

Im running windows server on ryzen 5600g 
32gb ram and 36 TB disk allmost full of stuffs everything works great super smooth. if you experiance slowdowns i think you did something wrong.