Open raimundomartins opened 1 month ago
It doesn't make much sense to me to keep that in a separate option from aunique
since the latter will never kick in without changing the former (especially because the former is not currently available in most distributions).
It worked, but I had to install the developer version, that flag isn't available in 1.6.0.
However, it did not disambiguate the path of the albums like I expected with the %aunique{}
. Is my usage incorrect (I couldn't find a clear example of how to use it)?
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: