-
Improvement
-
Resolution: Unresolved
-
Normal
-
None
-
2.5.2
-
None
-
Debian Linux
The AcoustID column in the album/track listing doesn't seem to be at all consistent about the information it displays.
If I add an album that is already tagged accurately, it doesn't show either that the AcoustID has already been calculated and is known, even though it's stored in the existing tags. The AcoustID column is just blank.
If I then right click on the album, and re-generate fingerprints for it, it now shows the fingerprint in red for every track (which I believe indicates that these fingerprints would be submitted), even though I know for a fact that most of the tracks already have matching fingerprints for the tracks on that album.
If I drag the album back to the "Clusters" (unmatched) area, and then select the "Scan" option from the context menu, it now gets populated into the right hand pane and shows mostly what I would expect, which is that most of the tracks have a gray fingerprint indication (the track matches and does not need to have its acoustid submitted), when they had all been red before, even though nothing has changed with the files (no changes have been saved yet).
This just seems weird to me.
First, the indication in the fingerprint column should be consistent, and right now it's not. But it would be even better to also indicate more information, maybe something like this:
- blank if a fingerprint is not known from either tags or being calculated
- gray (or maybe light green?) if a fingerprint is known from tags and matches that track
- black (or maybe dark green?) if a fingerprint has been calculated (not read from tags), and matches that track
- red if a fingerprint is known, but does not match that track (would be submitted if the user chooses to)
- orange (or some other color) if a fingerprint is known, but that track does not yet have any AcoustID's associated with it (would also get submitted if the user chooses to)
- blue if a fingerprint is known, but Picard was not able to or got an error looking up that track's AcoustID. These could be either submitted or not?
I think there should also be a context menu ability to submit only a single track's AcoustID, rather than all of the ones that might be in the right-hand pane. This would make it easier to only submit a new AcoustID when the user is very confident that a specific track is good, without having to submit everything, even ones you may not be so confident about.
It would also be nice to have a context menu option to re-query any acoustid's that Picard wasn't able to look up, or just re-query for a single track.
- has related issue
-
PICARD-119 Picard should indicate when something goes wrong with fpcalc
- Open
-
PICARD-286 Picard should report error on 502 from acoustid.org
- Open
-
PICARD-1413 Submitting AcoustIDs
- Open
-
PICARD-2134 "Submit AcoustIDs" submit ALL available fingerprint data, not only the selected ones
- Open