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.
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 :) !
Entirely possible, I know they have commented before on not wanting to do it.
Which I kind of get if you’re parsing metadata, you’d have to create a whole new method for parse and view which can be a pain. Though I’d hardly call it evil myself since its how I sort too.
I’d agree on having to think and duplicates are possible, but that’s possible in so many scenarios.
shrug
Either way metadata I think is important, but ive been a pain about metadata since the 90s (because burning CDs and having the actual track info was awesome).