-
Bug
-
Resolution: Invalid
-
Normal
-
None
-
2.5.6
-
None
-
Windows Server 2019 Standard
Sometimes when I use Scan button on some local files, if the AcoustID is missing from the database it is not getting written into the file's tags. If I then match the file manually to one of the recordings and press Submit AcoustIDs, nothing actually gets submitted.
I only work with FLAC files and this problem is somehow random. At the moment I have found a file where it doesn't work. If I select a single file, right-click and select Generate AcoustID Fingerprints, nothing happens. The expected result, is that an AcoustID is written into file's tags, and the file is marked as 'dirty', so it can be saved.
There's no errors in the Help->View Error/Debug Log.
If I manually generate the fingerprint, it gets generated properly, for example using this command:
> "C:\Program Files\MusicBrainz Picard>fpcalc.exe" "C:\Users\{username}\Downloads\Pascal Schumacher, Maxime Delpierre - Drops & Points Reworks [2018]\01. Gogopoints.flac"
I don't really understand where else to look for errors and what to do next. I will appreciate any guidance.
- has related issue
-
PICARD-2108 No ability to refresh files if filesystem has changed without Picard knowing
-
- Open
-
[PICARD-2152] Generated AcoustID is not shown
No, the cover art must be unrelated. AcoustID itself is really a separate project and the MB recording page just asks the AcoustID server for results. So how long it takes for AcoustID to take up any new submissions is really on the AcoustID side.
What could be, but I'm unsure, is that newly added releases maybe take a bit longer to fully show up on AcoustID. AFAIK AcoustID works with a copy of the MusicBrainz database that gets synced with official database dumps from MusicBrainz. But if and how this affects fingerprint submissions and the mapping to recording IDs I honestly don't know, so that's pure speculation.
I close this issue then. If you have any questions surrounding this feel free to ask on https://community.metabrainz.org/ . Also if you have any suggestion how to further improve this to make it more understandable.
The details how this works are very technical and hard to communicate to users in a simple way. We tried to do this a bit with https://picard-docs.musicbrainz.org/en/tutorials/acoustid.html , There are also some tickets around how to improve submission, e.g. PICARD-119 and PICARD-2096 (which is also pretty open and includes a similar discussion as we had here).
One thing that I noticed, it takes very long time for the AcoustID to show in Musicbrainz interface if there's a Cover Art I've recently uploaded. If it is a new release, but the cover art hasn't been uploaded yet, the acoustid shows up immediately after it has been submitted. That's why now when I'm adding a new release, I try first to submit fingerprints and then upload the cover art.
I don't know if my interpretation is correct, maybe it is just a coincidence, but I was observing it very often, though. As I am not familiar with the Musicbrainz architecture, let me know if this makes sense.
And I guess this ticket can be closed then. Thank you so much for such a comphrehensive explanation.
Philipp, thank you so much, it is a very good explanation! Indeed, I was mixing up two separate things - fingerprint is not the AcoustID, now after you've explained it to me, it seems obvious. Also, great stuff about showing the Fingerprint column, and also adding other columns as well, this is something I have not known before.
I also understand now that Fingerprint processing is not that fast, that's why Scan doesn't immediately work after Fingerprints have been submitted.
> How do you determine that nothing got submitted?
I was using the Fingerprint tab in the recording view on MusicBrainz. Now with the previous point, I understand that nothing will be shown there, unless the fingerprint has been processed by AcoustID server.
This comes up frequently, not sure how to better explain this to users.
If you don't get any results from a fingerprint lookup there is no AcoustID to display. The AcoustID is not the fingerprint, those are two distinct things.
The fingerprint is the result of audio analysis with fpcalc. You can see in Picard whether a fingerprint was genereated for a file or not by enabling the "AcoustID fingerprint" column. If that column shows a fingerprint icon a fingerprint was created with fpcalc, if not then not.
An AcoustID is obtained by sending the fingerprint to the AcoustID server and asking it for matches. If there are no matching AcoustID there just is no AcoustID to show.
> If I select a single file, right-click and select Generate AcoustID Fingerprints, nothing happens. The expected result, is that an AcoustID is written into file's tags, and the file is marked as 'dirty', so it can be saved.
"Generate AcoustID fingerprints" is intentionally for fingerprint generation only (without lookup). The expectecd result is that the file afterwards will have a fingerprint icon in the fingerprint column.
If you want to get AcoustID tags you need to use "Scan".
> If I then match the file manually to one of the recordings and press Submit AcoustIDs, nothing actually gets submitted.
How do you determine that nothing got submitted? If the fingerprints have been submitted to AcoustID there will be a debug entry in Picard's log "AcoustID: %d fingerprints successfully submitted". If there was an error there will be an error entry "AcoustID submission failed with error {error}".
After submission there is also not an AcoustID tag, if that's what you expected. But once the AcoustID server has processed the submissions you can use "Scan" to get matches again.
The AcoustID server processing the submissions always can take a while. But at the moment the import might additionally delayed by recent technical issues on AcoustID and the required changes to the server in the near future, see https://community.metabrainz.org/t/acoustid-downtime/522087/
Closing, see also PICARD-2108 for similar discussions