I was hoping to go all in with Jellyfin, but it’s been absolutely maddening to try to get it to play nice with my curated library. It just makes too many dumb assumptions about artist metadata.
Any other suggestions?
EDIT: I installed Navidrome, then poured over the documentation for the config file and micromanaged every setting. This has allowed me to get damn near close to the exact unobtrusive behavior I had hoped for.
Just curious, why folder structure? Are your directories not artist/album?
It’s
.../music/artist/album/song.flacThis does not work with Navidrome if the metadata is weird. I have a lot of songs that Navidrome refuses to even list because their metadata is bad.
I browse my music by folder structure, not metadata. Folder structure is universal and does not care about inconsistent metadata.
It can’t handle radio shows or VA mixes well either.
Yeah… Newer genration are into “put everything in 1 big messed up directory and find all you needs by tags” structure.
I get the gist, but calling directory structure evil is kinda extreme. It allows to structure your thoughts and if somehow your metadata is corrupted, you still have a directory structure.
I work on both front for compatibility issues but nothing beats a well thought directory structure!!
Who called it evil?
I was wondering because all I do is /artist/album/, which is going to be the same logical appearance in navidrome as at would be from a dir structured view so couldn’t understand the point.
The difference is the metadata, which I’m much more strict on so I haven’t seen these sorts of problems.
I read that somewhere from a github repository maybe even in Navidrome’s pull requests or Issues maybe?
I think the argument was that in directory structure you always have to think where you have to put your files and sometimes a file can be at 2 different places at the same time and I do agree to some degree, that’s why I use both :) !
Ah, I write the metadata on import in lidarr, so kind of a non-issue for me.