Picard can't match AcoustID of a track, but the AcoustID is added

[Comrade_Mike]

@yindesu

D: 22:05:36,557 webservice_init_._handle_reply:553: Response received: {‘results’: , ‘status’: ‘ok’}

This is the same problem that I’ve been having:

AcoustID API returning empty results

I’ve had a problem since I first started using AcoustID in January where it consistently won’t return any results for certain fingerprints, no matter how many times I’ve submitted them. I’ve tested this with Picard, VLC and Metatogger. For example, looking up this fingerprint returns: {“results”: [], “status”: “ok”} Looking up the same recording from a different release gives the expected result: {“results”: [{“id”: “6222d0f4-3e53-48fc-afe2-20d527d1856b”, “score”: 0.989583}], “status”: “o…