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.
EDIT 2: AFA mobile client goes, I’d absolutely consider paying for Symphonium, if it didn’t seem to require my having a Google Play account (fuck that). So instead I’m trying Tempo.
Could you explain how you use explo?
This is gonna get a bit into my particular setup but sure
Explo’s a super early in development “discover weekly” generator, relies on Listenbrainz scrobbling and runs on a cron job to download the playlist from your connected source (in my case slskd), put it in a folder, and create a Navidrome playlist out of it. I use the SLSKD_MIGRATE option (my feedback is actually the reason the dev even added it), so my files are downloaded to my slskd dir and explo moves them to a separate library.
I’m very particular about my library though so I don’t want it just throwing everything into the same folder as the rest of my music, and I have 2 users, so my directories are like:
Keeping the discover folders for Explo completely outside the main library, but mounted in Navidrome as additional libraries, helps keep things very separate. Explo’s also smart enough to check with Navidrome before searching for a track - if it already exists in the library, then it won’t redownload it.
I run 2 Explo instances, 2 hours apart, and in between those runs I have another cron job that wipes out my slskd downloads directory for a clean slate.
One small catch I ran into: Explo needs a Navidrome admin account to kick off the library scan, but my users aren’t admins (since an admin automatically has access to every single library). So each week when it runs I need to log in as an admin and re-assign each playlist accordingly. Not a big deal, and the dev already has some ideas in mind to address this in the future. This also becomes a small bit of an issue with the whole “don’t download existing tracks” thing - Explo’s looking at the admin’s library which is everything, not the individual users’ libraries. So if one user’s playlist has a track that’s in the other user’s library, it won’t be properly added. Not the end of the world, but a mild annoyance.
I will say (and this isn’t a fault of Explo), I’m not a big fan of Listenbrainz’s weekly playlist algorithm. About 2/3 of the playlist tends to be artists that I already listen to, so it feels like a bit of a waste. I hope down the road we can plug in last.fm or something which tends to be a bit better for that.