Greetings Lemmings!
I am not new to self hosting; been at it for a few years. And I have neglected a very important part of my home lab; MUSIC!
So I stream music from Navidrome to all of my devices.
My music library has grown organically over the years, for probably the past 17 years. And a few times I had manually organized and fixed up some of the tags. But ultimately I ended up with a mess of a library.
I am working on cleaning that up. Though I absolutely should have cleaned it up before I created 2 backup scripts.
In short, I have a script that is called from a systemd service on a timer that runs my backup script that essentially more or less uses rsync to mirror the files in LiveMusicDir to MusicArchive1. This happens on my docker host where my Navidrome lives. The Music is on an NFS share hosted outside of the docker host.
The next step I run another similar setup on my desktop; systemd service running a script on a timer that uses rsync and other dependencies to track changes.
What I plan to do is organize the source. I am using beets, and learning as I go.
What methods do you use for managing a large music library?
“unsorted” folder contains input. “Music” folder has full library; any imports must go through beets. rsync to remote backups; one scripted/automatic, one manual & password-protected. Restores (needed once or twice) are done with beets import, but whatever flag that does “just import, don’t tag”
Once I have my music gone through and deduped, as well as tagged, I will likely never have to run it again; as the music my server ingests is already properly tagged.
The deduping is a little difficult. Obv matching files are caught with regular dedupe tools, but I’ve been meaning to make a script to use fingerprinting (dejavu is the library I think?) to find matches. Problem is the fingerprints are about as big as the music files themselves.
Beets can do some sort of fingerprint with ffmpeg and in another comment I posted a snippet that I used ti generate a log. I’ve only done dry runs.