Here is an album I have been working on: I load the tracks into Picard and scan for fingerprints. It identifies this album and loads into the right-hand pane. It then matches a selection of some of the fingerprints to tracks on the album. It never correctly matches all of the tracks, just some of them, and the number and selection of matched tracks is never the same each time. I then drag the unmatched tracks onto the album so that all of the tags turn green, and upload the scans. I’ll get a “submitted successfully” message. But then I can repeat this whole process over and over again (which I have been doing over the past week) with no real change except, as I said, the selection of matched tracks always varies.

During all this time, I have even seen oddball behaviour in MusicBrainz with this album, where I can look at the individual properties for the various Tracks/Recordings, and most of the time they will not have any associated fingerprints. Then the fingerprint associations would appear, but shortly afterwards would disappear again. Today, the fingerprints are all showing up, and that behaviour now seems to be permanent.  I had hoped this might indicate that the problems with Picard would have gone away, but no. Picard is still doing the same thing.

I've reported this on the AcoustID part of the forum, because, during the period while I have observed this behaviour, AcoustID has also been flaky, and I can't be sure whether what I am seeing is a Picard, a MusicBrainz, or an AcoustID problem.

I have (hopefully) attached a log file, but it is very big.  It is a log of a session where I did as described above ten times in total, each time with a different selection of tracks being matched to the album.