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
Disambiguation not working with custom fields #1775
Comments
Hmm; yes, I can see how this would get into trouble if only some albums have the field. Can you check whether this works if you add that field to all of the albums that need to be disambiguated? Some could have an empty string, or something like "none," but this might work as-is as long as there are no actual missing values. |
Ran |
I did also notice that |
Cool; thanks for trying. I actually think the I just pushed a change that might fix this problem. Could you please clone the latest source and see if it works? |
I git-cloned, then did For example, I did |
Hmm; that's too bad. This kind of thing can be hard to debug. Can you show the metadata for all the albums involved? For example, something like:
for the relevant albums. |
Info mildly redacted:
|
Hmm; so they're both missing a value for |
Correct, but when I run
It returns the remastered album |
Ah, the key is that |
In retrospect, that's so obvious. I've been trying to disambiguate albums by using track metadata. |
Wonderful! ✨ |
I have two copies of an album:
By default, I use
$year
in the folder name, so I thought a good workaround might be to create amastering
field and use it (beets modify mastering=HDTracks album year:2014
which is very handy syntax).It set successfully, but now I can't figure out how to disambiguate with it.
path:
beet move
results inalbum [1995]_no such field 'mastering'_
The text was updated successfully, but these errors were encountered: