Didn’t want you to think it was something personal going on. I’m faffing around with some unloved cheap compilation CDs which have a lot of data missing. Have attempted the AcoustID data upload using Picard from two different machines and nothing appearing yet… At the same time Picard is still being nippy at looking things up.
It seems the aIDs for my tracks appear now. Either the issue was fixed or the backlog was cleared.
1 Like
Good news. We can further improve the MB database.
1 Like
I think the term is “catching up”… mine are still pending…
Editing on MB is sometimes a lesson in patience. 
2 Likes
My queued AcoustIDs also caught up now… (okay… some have, some haven’t)
2 Likes
How can I see what acousticIDs I have in queue?
(I use Picard to submit them, since some time, a lot don’t come through, and it seems for long tracks this is a rather consistent issue, although it might just be perception based on the latest 2 releases passing none of the acousticIDs, being both releases with only +15minute tracks.)
I’d like to know that myself, but I don’t know if that’s possible. That is exactly the issue: if the server’s down, it’s down; but if it’s not, you just don’t know if something’s wrong, or it’s just taking longer than usual.
It’s generally possible to ask the AcoustID API for the status of a submission. But Picard doesn’t store past submissions and hence cannot check the status.
There is a ticket https://tickets.metabrainz.org/browse/PICARD-2163 about this. Generally having some kind of AcoustID submission dialog with more details would be indeed useful.
But in the end it wouldn’t tell you anything new except that the submission is still pending. And for those cases where the fingerprints never get processed and they are stuck in pending this is not of much help. Have a look at the issue Submission stuck in pending state · Issue #70 · acoustid/acoustid-server · GitHub , it has a couple of API calls to submissions that are stuck in pending state.
4 Likes