I have a folder of MP3s, some of which date back to 1999, just a few years after the format was popularised. Most of them have utterly terrible names (think RIDEONAM.MP3). I think at this point they might even survive the heat death of the universe. And they’ll still be terribly-organised.
Check out beets.
Why, what does it do better than picard?
Saved me a ton of time for some massive imports, but I do get @Wolf314159@startrek.website point, night not be the best tool for other cases.
It’ll destroy all your painstakingly crafted and curated ID3 tags much faster than Picard. I’m not salty or anything. Anyway, the lesson for me was that music is simply too complicated from a library perspective to trust to highly-automated tools like beets. Picard kind of encourages you to go directory by directory and release by release, and that is a good thing. These days so are does most of the library stuff for newly added things, but I usually end up fixing it all basic to my standard with Picard later.
Yeah, definitely agreed. There are so many edge cases. I tend to put new downloads/purchases in an “intake” dir and then run that through picard, which then saves it at the final local storage path with whatever tags I decide to use