3 ms·
I have my Picard and beets configs hosted here - https://github.com/hashhar/picard-beets-config https://github.com/hashhar/picard-beets-config I currently have
by hashhar 5y ago
I have my Picard and beets configs hosted here - https://github.com/hashhar/picard-beets-config https://github.com/hashhar/picard-beets-config
I currently have a workflow like:
1. Add tags, move and rename files using MusicBrainz Picard.
2. Run beets on the files with the writing, tagging and renaming options disabled.
The keys which are left empty in the yaml need to be provided by a local config file like beets -c secrets.yaml. A sample secret file can be seen here[1].
This means that I can still use beets to do things like fetching lyrics (but not writing to ID3 tags), creating smart-playlists, updating my MusicBrainz collections etc.
Due to this workflow you might find that the beets config is lacking a lot of plugins and configuration that would allow it to replace MusicBrainz Picard like the chroma plugin, fetchart etc.
Some of the cooler beets plugins that complement Picard are:
mbsync: It can fetch updated metadata for existing tracks solving my biggest issue with Picard.
lastimport: To import playcounts from Last.fm
smartplaylist: To generate rule-based playlists. Now I can have playlists by decade or by genre or even something like "songs from 2000-2010 with danceability > x (from AcoustID)"
missing: to list missing tracks from an album
[1]: https://github.com/hashhar/picard-beets-config/blob/master/beets/sample_secrets.yaml https://github.com/hashhar/picard-beets-config/blob/master/b...