11–20 of 124 posts
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 mo…
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 mo…
Isn't beets going to just overwrite whatever you did in Picard?
Earlier quoted context omitted.
Isn't beets going to just overwrite whatever you did in Picard?
Well, one might use picard to find a musicbrainz release id, so that beetz has something to grab on to when importing.
beet import "Iron Maiden.zip" -S 4500ad36-5f92-4e4c-bb24-3a9a57faf550I recently looked into beets, but it seems it’s focused on automation, is that correct? I often buy stuff that has just been released, and that’s not yet in any database, so no automation works. My current workflow is download, unzip and manually tag (mainly genres, sometimes badly named artists/albums) with MusicBee (which gives me autocomplete for genres so I can reuse existing ones), and then copy the files to the…
If you add a lot of new stuff to your library, you'll often need to add them to MusicBrainz yourself. I use beets and I currently have added 2697 releases (2543 release groups) to MusicBrainz.
I recently looked into beets, but it seems it’s focused on automation, is that correct? I often buy stuff that has just been released, and that’s not yet in any database, so no automation works. My current workflow is download, unzip and manually tag (mainly genres, sometimes badly named artists/albums) with MusicBee (which gives me autocomplete for genres so I can reuse existing ones), and then copy the files to the…
If you add a lot of new stuff to your library, you'll often need to add them to MusicBrainz yourself. I use beets and I currently have added 2697 releases (2543 release groups) to MusicBrainz.
I'm in the midst of a major music library overhaul and would not know how I'd ever get it done without Beets. For example, it's clearing out embedded images, fetching new hi-res artwork and verifying FLAC integrity, as I go through artist by artist.
Been using with Claude via MCP to tag a bunch of old ripped CDs - fun with mixed results.
I recently looked into beets, but it seems it’s focused on automation, is that correct? I often buy stuff that has just been released, and that’s not yet in any database, so no automation works. My current workflow is download, unzip and manually tag (mainly genres, sometimes badly named artists/albums) with MusicBee (which gives me autocomplete for genres so I can reuse existing ones), and then copy the files to the…
Been using this for several years now. It's definitely not for the average user. But nothing is quite so flexible.
There is a webpage on beets website where they list all the functions and explain what it does. Very useful when you go back after half a year and can't remember how it works.