-
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
Different releases incorrectly considered duplicate #5250
Comments
It doesn't make much sense to me to keep that in a separate option from It worked, but I had to install the developer version, that flag isn't available in 1.6.0. PS: It turns out it was not disambiguating between my import and whichever one of these I have, but it now put in the same directory the ones I said in the OP, which are two singles in the same release group. PPS: Despite the criticism this software in a life changer, thank you very much! |
My config has an example of aunique, but it's many years old. YMMV. https://gist.github.com/RollingStar/86e041338df295afbbf77a9027903068 |
Problem
I'm trying to import both https://musicbrainz.org/release/3e475b92-6217-43cf-8557-e0c11bc96091 and https://musicbrainz.org/release/0701e066-6823-4987-946e-ad04a972bb0c but when I try to import the second one it is considered duplicate. Catalog number is different and they have different tracks, but I'm not allowed to have both albums in my library.
Setup
My configuration (output of
beet config
) is:The text was updated successfully, but these errors were encountered: