Determine duplicates by how they sound using GenPUID

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Determine duplicates by how they sound using GenPUID

Re: Determine duplicates by how they sound using GenPUID

by Owyn » Sun Jul 05, 2009 3:03 pm

RobertSmith wrote:
Owyn wrote:Which tool did you use to store "MusicIP PUID" in "Composer" tag?
See previous post ;)
Mp3Tag
Thanks, our posts crossed.

Re: Determine duplicates by how they sound using GenPUID

by RobertSmith » Sun Jul 05, 2009 2:58 pm

Bex wrote:I'll add all custom fields to ADFF so you don't need to use the composer field for it! :)
Great! I dislike using tags in a way they not supposed for :)

Re: Determine duplicates by how they sound using GenPUID

by Bex » Sun Jul 05, 2009 2:20 pm

I'll add all custom fields to ADFF so you don't need to use the composer field for it! :)

Re: Determine duplicates by how they sound using GenPUID

by RobertSmith » Sun Jul 05, 2009 2:07 pm

Owyn wrote:Which tool did you use to store "MusicIP PUID" in "Composer" tag?
See previous post ;)
Mp3Tag

Re: Determine duplicates by how they sound using GenPUID

by Owyn » Sun Jul 05, 2009 2:04 pm

RobertSmith wrote:My temporary solution is to store a copy of MUSIC IP in Composer, it works perfect together with above mention scripts. No need for xl.
Which tool did you use to store "MusicIP PUID" in "Composer" tag?

Re: Determine duplicates by how they sound using GenPUID

by RobertSmith » Sun Jul 05, 2009 1:43 pm

Owyn wrote:Robert, how did you get
a)"MusicIP PUID" tag loaded reliably. MusicIP archives "MusicIP Fingerprint" but not "MusicIP PUID". Picard Scan followed by Save does load "MuiscIP PUID". Is there a better/faster solution?

b)Load the extended tag to Composer. I am looking into doing it with a Perl script, but, if there is available way of doing it already I would be interested.

Composer tag is not a good target for me. I have extensive real composer data loaded already. MM custom tag is another possibility but MM's implementation does not seem to be portable to other applications, e.g. MP3Tag.
b)I use Mp3Tag
You can use MM CustomX it's a extended tag in the same way as MUSICIP PUID, use Alt-T to see it in Mp3Tag (Custom1 = COMMENT SONGS-DB_CUSTOM1).

To Copy PUID to Custom1
Select ACTION, then create a new action (upper right hand "star" icon). Give your action a name (e.g., Copy PUID to Custom1), then in the next box, click the upper right side "star" icon to create the action. It will ask you for type. Use the drop down box to select FORMAT VALUE. Within this select the field (COMMENT SONGS-DB_CUSTOM1) then enter the format string (%MUSICIP PUID%). Then save this.

Now you have an action, run the action on one file. You can select 1000s of files at once to run the action on (test it on a few first).

a)I'm not sure, I use GenPUID and Picard. GenPuid seems to be the most reliably and with GenPUID it's easy to make a batch job, see post 1. But normally I use Picard for tagging and to save PUID. I save files also if were are no match in MusicBrainz (save them in left windows, to store only PUID).

Re: Determine duplicates by how they sound using GenPUID

by RobertSmith » Sun Jul 05, 2009 12:10 pm

My temporary solution is to store a copy of MUSIC IP in Composer, it works perfect together with above mention scripts. No need for xl.

Re: Determine duplicates by how they sound using GenPUID

by RobertSmith » Sun Jul 05, 2009 8:28 am

trixmoto wrote:Well my "MusicIP Tagger" already does all of this except store the PUID in a custom field. This is however on my list for the next version.
I know that you can use MusicIP Tagger for tagging (but as i wrote in previous post not the best source, I prefer MusicBrainz and Picard Tagger). But how can I use MusicIP Tagger to find duplicates, I most have mist something?

Edit: or do you mean that in "next" version can run MusicIP tagger (and only for tracks missing PUID) without tagging, only store PUID?

Re: Determine duplicates by how they sound using GenPUID

by trixmoto » Sun Jul 05, 2009 7:53 am

Well my "MusicIP Tagger" already does all of this except store the PUID in a custom field. This is however on my list for the next version.

Determine duplicates by how they sound using GenPUID

by RobertSmith » Sun Jul 05, 2009 3:43 am

Edit:
xl is unneeded, see following posts

I have many duplicates with different titles/artists (all with different hash). Most of my tags are from MusicBrainz, but what is no guarantee for unanimous titles since titles can be different on different releases because whoever decided of the design of physical release.

Before I start to clean up (delete and transfer PlayStat) with the amazing Advanced Duplicate Find & Fix my first step is to make sure they all have same title and artist. To do this I use xl and GenPUID with MusicDNS web-service, which returns a PUID (PUID could also be returned with MusicBrainz or MusicIPmixer).

Start to download GenPuid from MusicDNS, you need an account to be able to download GenPUID 1.4 and to get your key.

You start GenPuid from Windows Command Line. I prefer to use a batch file. I have two bat files one for writing PUID to tags and one for creating an XML file to be used with xl (they could be combined but...).

MyGenPUID - Write PUID.bat

Code: Select all

genpuid e10...[key from MusicIP] "G:\Music MP3\By Artist" -r -archive -xml=temp.xml
There are several switch, I only use few of them, see reedme for more information.
-r
Recursively processes all sub-directories.
-archive
Write MusicIP tags into the song files as they are identified.
-xml=temp.xml
Generate output in XML format

It can takes hours to run GenPUID depending on number of tracks, so be careful and don't start with your entire collection, just start with a testing directory. Even if there are only a few tracks it can takes 10 minutes per track if a track doesn't exist in MusicDNS. Normal time is 2-3 sec per track (25000 tracks = ~20h ...). If you store PUID in tags you don't have to run GenPUID again, so there is a good idea to have new tracks in a temp directory before they are moved to correct directory. If you don't receive a PUID check status for each track in the XML file and search for Pending.
Pending
The server has not yet generated a PUID for this track, which can take up to 24 hours. If you have submitted a fingerprint for PUID creation, you will need to re-request it from GenPUID after that time frame has lapsed.

MyGenPUID - Create MyCollectionXML.bat

Code: Select all

genpuid e10...[key from MusicIP]  "G:\Music MP3\By Artist" -r -rmd=1 -xml=MyCollection.xml
-rmd=1
Returns extra metadata. (1: Include basic artists name and track title metadata)

I don't know why but GenPuid doesn't currently cope with Unicode filenames and will generate invalid XML. But it's simple to correct just open MyCollection.xml in notepad and save it as UTF-8 (UTF-16 ?).

With PUID stored in extended tag MUSICIP PUID export your collection using i.e. Mp3Tag -export (CSV)

Code: Select all

$filename(csv,utf-16)Album;Title;Artist;MusicIP PUID;Path
$loop(%_filename_ext%)%album%;%title%;%artist%;%MUSICIP PUID%;%_folderpath%
$loopend()
In xl use pivot-tables to look for duplicates (tracks with equal PUID). Rename yellow titles.
Image
Rename artist and title (move feat. Kesha to title)
Image

With xl it's also easy to check your tags (Artist, Title). Import your library CSV file and MyCollection.xml wish contains tags from MusicDNS (not the best source for tags, but to find big mistakes it's OK), sort them both by PUID and compare the tables.

Since GenPUID can create an XML file maybe someone want to develop a script so PUID could be stored in a MM Custom field. And in the future be an option in Advanced Duplicate Find & Fix or Magic Nodes. No need for xl :)

Top