Replies: 1 comment 2 replies
-
If you have multiple duplicates, you need to re-tag each of them separately in order for the tags to be updated.
For this one, it would be best if you submit a new issue and fill in the issue template providing the relevant details. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
These are my import options in config.yaml:
My usecase is to track all of the 'correct' tags in beets but to not touch the files underneath. I imported a lot of music 'as-is' and I am trying to go back and re-tag it with commands like
beet import -L artist:blinkto re-tag all of the various blink-182, Blink-182, and Blink 182 albums to have the same tags from musicbrainz. Re-importing the albums like this does add the correctly tagged albums to the beets db, but it does not delete the old entry. I can see that the album is stored with the old bad tags and the new tags with the duplicates plugin:beet dup -k path -F '${path} ${artist} ${album}'. Shouldn't beets delete the old entry for the imported path?A related issue is that I would like to clear deleted albums from the database. I have read some issues and seen that
beet updateis supposed to fix both of these problems, butbeet updatedoesn't seem to actually change the db and the deleted files remain in the db.Any suggestions?
Beta Was this translation helpful? Give feedback.
All reactions