Closed Mortimerp9 closed 10 years ago
Another case, with colors:
Are you using fingerprinting? Or do your tracks have IDs already? Beets seems to be weighting those over the track titles. If it's the former, fingerprinting may be doing its job (discovering that your tracks are mislabeled).
I enabled the chroma plugin, so there should be fingerprinting. I'll take your word that it means that my files were badly tagged to start with.
Is there a way to show what criteria is used for the ranking?
The yellow stuff in the parentheses show mismatches. So where you don't see an "id" mismatch, beets apparently made a match based on the MBID from Acoustid.
Have a better idea about how we can display this kind of information? If so, please file an issue with your suggestion?
BTW, #327 has a similar suggestion buried in there somewhere.
ok, I will check, the idea was that that 73% match comes from an aggregate of scores, no? so there could be an option to show the split. Will check the code a bit and send an issue.
Yes, showing the (ranked) breakdown would definitely be an interesting idea. Our somewhat-new Distance
class should make this relatively straightforward.
another side question. How hard would it be if I wanted to create a new (browser-based) interface for the import process?
Pierre Andrews, Ph.D. Research Fellow
On Wed, Apr 9, 2014 at 7:00 PM, Adrian Sampson notifications@github.comwrote:
Yes, showing the (ranked) breakdown would definitely be an interesting idea. Our somewhat-new Distance class should make this relatively straightforward.
Reply to this email directly or view it on GitHubhttps://github.com/sampsyo/beets/issues/674#issuecomment-40021931 .
Of medium to advanced difficulty, but immense value to the community. :smiley:
If you're interested, I'd love to help you do it. We've architected the importer to have a theoretically pluggable interface (we split between the core logic in ImportSession
and the CLI-specific stuff), so you wouldn't be starting completely from scratch. There would still be significant complexity in working out the details for an interface that can show more than one thing at a time.
Let's chat more, potentially in a different issue, if you're interested in pursuing this. It would be an amazing addition to have, so I highly encourage it.
See also this recent discussion on the mailing list: https://groups.google.com/d/msg/beets-users/Y0U70pAEFVg/tFMuuXaYTxYJ
cool, I definitely do not have the time right now, but I'll keep it in mind :)
Pierre Andrews, Ph.D. Research Fellow
On Wed, Apr 9, 2014 at 7:07 PM, Adrian Sampson notifications@github.comwrote:
Of medium to advanced difficulty, but immense value to the community. [image: :smiley:]
If you're interested, I'd love to help you do it. We've architected the importer to have a theoretically pluggable interface (we split between the core logic in ImportSession and the CLI-specific stuff), so you wouldn't be starting completely from scratch. There would still be significant complexity in working out the details for an interface that can show more than one thing at a time.
Let's chat more, potentially in a different issue, if you're interested in pursuing this. It would be an amazing addition to have, so I highly encourage it.
Reply to this email directly or view it on GitHubhttps://github.com/sampsyo/beets/issues/674#issuecomment-40022525 .
This doesn't seem to make much sense, it's just shuffling tracks when they are actually in the right order already