[mb-devel] Picard & tag mapping

Vidar Wahlberg canidae at exent.net
Sun Aug 19 09:10:52 UTC 2007


On Sun, Aug 19, 2007 at 10:58:23AM +0200, Vidar Wahlberg wrote:
> On Sun, Aug 19, 2007 at 12:52:32AM +0200, Lukáš Lalinský wrote:
>> No, it should be an UFID frame as it is. The other MB IDs should be in
>> PRIV frames, but it's too late to change that.

one more thing about UFID:
UFID = Unique file identifier
not "Unique track identifier".
what if you got 2 mp3s of the exact same song, one in 320kbit for your
home sound system, the other in 128kbit for your portable audio player.
you've also have some different tags in the files so you can distinguish
them in an audio player.
they would have the same UFID, but different data. and as the id3v2.4
standard says about UFID:
This frame's purpose is to be able to identify the audio file in a
database, that may provide more information relevant to the content.
a such database may be musicbrainz.
or it may be the database of an audio player that use the UFID value as
a unique name for files, in which you'd get a collision.

i still feel the UFID frame is not so well suited for storing track id.


-- 
Regards,
Vidar Wahlberg



More information about the MusicBrainz-devel mailing list