[mb-devel] Picard & tag mapping

[Vidar Wahlberg]

On Sun, Aug 19, 2007 at 11:24:37AM +0200, Lukáš Lalinský wrote:
> On Ne, 2007-08-19 at 10:58 +0200, Vidar Wahlberg wrote:
> > myself i'd really like to see these keys be the same across as many
> > tag-formats as possible.
> 
> I personally don't see the reason for this, it will never be identical
> across formats. If you working on an application, you would need
> specialized tag mapping code for each format, anyway.

not necessarily, but let's leave this for now. maybe i can give some
good examples in the distant future exactly what my idea is.


> > i don't quite agree here, even if the other mb ids were placed in PRIV
> > frames it would be inconsistent with mp4.
> 
> Hm, why? It would be inconsistent with VC or APEv2 tags, but that's just
> because of their limitation (they don't support hidden tags).

"hidden" is pretty much like a "hidden" file in linux (or maybe this is
depending on file system, i don't know). the only meaning is that "it
should not be shown unless specifically asked for", but it's still there.
most audio players have a mapping for eg. "ARTIST" in ogg vorbis to show
in the "artist" field in the audio player. if you add a field the audio
player is unaware of, like "GOBBLERS" it's usually not shown, or shown
in a box of "i don't know what these tags are". this tend to be the same
for TXXX frames in id3 (at least what i've seen).
now i must admit that i don't know the comment style for mp4 very well,
although it appears to be fairly equal to id3 in style (you have
predefined "frames" where "----" appears to be equivalent with id3's
"TXXX"). if musicbrainz tags in id3 should be in different frames (UFID,
PRIV) and only in "----" frames in mp4, that appears to be inconsistent
to me.


> (But as I mentioned in the previous mail, I don't think the current
> format of saving MB tags is good, It's just that it isn't really
> possible to change it without a good reason.)

then at least we agree that it's currently not "optimal" :)
i could ofcourse draw up a table, much like
http://wiki.musicbrainz.org/PicardQt/TagMapping only showing what i feel
is most intuitive & consistent, although the only changes i want are
those i've already mentioned.
couldn't it be possible [in the future] to write MUSICBRAINZ_TRACKID in
both a UFID frame and a TXXX frame and rather deprecate UFID and then
remove it completely in 2 years time?
<wish>hopefully id3 won't exist in 2 years time</wish>


-- 
Regards,
Vidar Wahlberg