Don’t think you’ll see anything change until the stat graph perks up: Statistics | AcoustID and\or we hear something from @lukz
3 Likes
Seems that @lukz is doing some work on the AccoustID server code, might be getting a fix in the near future.
6 Likes
13 days without any new additions (or is this just a graphical problem)?
I hope @lukz will let us know with a new blog entry.
UPDATE 24.08.2021:
It seems that AcoustID is back!
I think AcoustID now in read-only mode. API return OK for submissions, so maybe they store in some buffer storage until better times. Maybe not. There is few looks-like-performance-related commits in git log
1 Like
Do notice the git log dates fit with this thread. I assume the dev is currently hitting the AcoustID server with a tuning fork until he can get it back into singing the correct tune.
4 Likes
I think it is a problem if, when submitting Fingerprints via Picard, Picard reports that the Fingerprint was successfully submitted to AcoustID, when in fact it was not. Having said that, I’m not sure at which end the problem lies.
2 Likes
I think they were received by a queue and they will eventually appear, no?
It’s hard to know. Will they survive two weeks of accumulated queuing?
1 Like
I don’t know what else Picard could do, though. The acoustid server accepts the submission and returns status 200.
6 Likes
Submissions are processed asynchronously by a background job. However, this normally only takes a few seconds…
API documentation
As far as i understand normal AcoustID API behavior is put submission to database or some buffer and return status 200 (Ok) to client. Seems like this part of AcoustID work well all the time. But another part, that shall somehow process submission and make it usable for users not work at lest last 9 days
6 Likes
That looks promising. Acoustids that I submitted a week ago haven’t yet appeared on the recordings; I imagine there is a very large backlog and it may take some days to catch up.
1 Like