Musicbrainz Picard is a lot easier than beets, although it does require some introductory concepts to make sense (e.g. terminology like “release”, “release group”). And it makes it too easy to accidentally poison datasets in an attempt to be helpful. Harder to automate than beets, too.
Both of them also benefit from a decent knowledge of where your files came from, not as good for a random pile of mp3s.
wetbeardhairs@lemmy.dbzer0.com 9 hours ago
No I’m sure there will be an obscure shell script that someone wrote to do all of the install for you that will suddenly fail on a broken python dependency (because why not) and then leave your system in semi-altered state that doesnt really work wrong but its never quite right again
r_13@lemmy.world 9 hours ago
I 100% learnt to use docker specifically to avoid the exact situation you described.
Hawke@lemmy.world 8 hours ago
Got any good resources for learning?
In my (limited) experience Docker is just “run some script from a random GitHub that loads more stuff from a random GitHub… now you have a blob of code on your PC somewhere that’s unmodifiable and inaccessible unless it’s a web app in which case it’s listening on a random port with no access to any system resources”
I assume there’s something more I need to be doing but all the learning resources just kinda assume you understood wtf it’s doing.
notoftenthat@sh.itjust.works 7 hours ago
Switch “some script” to “docker compose” and you are a subject matter expert.
Sir_Kevin@lemmy.dbzer0.com 5 hours ago
Welcome to the linux community.