-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid duplicates on unmatched tracks #5228
Comments
The
|
Thank for the information @jackwilsdon. Do you know if it' possible to specify multiple keys? E.g. use |
If importing un matched music that has no musicbrainz link 'as is' then beets will not be able to identify duplicates.
For example, if I import a track that is not on music brainz I use the following flow
If I follow this process again (e.g. import a second time and follow the above steps) then I end up with a duplicate track. Even the duplicates plugin does not detect this track as a duplicate.
Is there any way to configure beets to detect such duplicates? It should realise it has the same meta data for the track in the db surely? Same tags for artist, track, album etc.
For example, first import:
shows single track in collection:
If I then import again:
I then end up with a duplicate:
Clearly beets knows this is a duplicate somewhere as it has had to add the ‘.1’ extension to the track. Is there a config option to tell beets to merge the duplicate instead? I have the duplicate merge action set in my config. Perhaps this doesn’t work with tracks that aren’t matched against musicbrainz?
The issue is similar to this: https://discourse.beets.io/t/deleting-duplicate-songs-on-import/1224 however I'm looking for a solution that works for tracks that don't match against an entry in musicbrainz.
The text was updated successfully, but these errors were encountered: