Talk:How PUIDs Work

From MusicBrainz Wiki
Revision as of 18:38, 12 June 2011 by 194.88.211.253 (talk)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

How could I add PUID for the track?--194.88.211.253 18:38, 12 June 2011 (UTC)


Therefore MB needs a simple command line (or drop-files-here) tool, that does all this if we really want to populate the database with PUIDs. We should harness the past matching activity of our users. --DonRedman


It should be easy enough to create a script that:

  1. Traverses your music files, and finds everything with no PUID
  2. Fingerprint all the matching tracks, then submit the PUIDs
  3. Analyse the remaining tracks to generate PUIDs

Re-run the script 24-hours later, then your entire music collection will have PUIDs.

I intend to do this to my collection once the command-line analyser ships. I should probably make a start on fingerprinting stuff with libofa before then, but it hasn't hit Debian yet. --MartinRudat


It should also be easy (hopefully) to create a script that:

  1. Traverses your music files and finds everything with a PUID and a MB TrackID.
  2. Submits these pairs to MusicBrainz.

Such a script could populate MB with the PUID--MBID pairs which are needed for PUIDs to become really useful. --DonRedman

It seems that the script prints "No MB ID" for files which either have no MB ID or for which no PUID was found, which confused me for a while. Perhaps two separate error messages are appropriate? --foolip


I have run into at least one case (I'm generating PUID's for everything in my library) where Picard does not generate a PUID and the genpuid tool does return a PUID. Not sure what might different about how Picard is handling generating the PUID that might account for this exception.