5 ms·
I spent a couple of nights working out how to configure beets to my liking and have loved it ever since. My “workflow” is now: - buy album on Bandcamp - downl
by Yodel0914 11mo ago
I spent a couple of nights working out how to configure beets to my liking and have loved it ever since. My “workflow” is now:
- buy album on Bandcamp
- download zip
- beet import {zip file name}
And beets extracts the zip, matches the album to musicbrainz, updates any metadata, and drops the files into the directory structure that I like (naming the files how I like them, too).
Very rarely an album will need some more attention, in which case I use Picard to fix it before using beets to import it.
- Hamuko 11mo agoIsn't beets going to just overwrite whatever you did in Picard?
- siddboots 11mo agoWell, one might use picard to find a musicbrainz release id, so that beetz has something to grab on to when importing.
- Hamuko 11mo agoI mean, you can just do that in the browser too. "Enter ID" allows you to enter the MusicBrainz UUID (or just full URL). You can even do in the command itself. beet import "Iron Maiden.zip" -S 4500ad36-5f92-4e4c-bb24-3a9a57faf550
- Yodel0914 11mo agoNo, you can tell it to use the metadata as-is. Sometimes there’s just weirdness though - for example recently I bought an album and the band included all the tracks from their previous album as bonus tracks. So I used Picard to split them into the 2 “proper” albums.
- curioussquirrel 11mo agoA very similar workflow on my end, both beets as the main tagger/organizer and Picard to pick up whatever can't be processed through beets. Beets is amazing!