Thanks very much for your kind reply. Your perspective is very helpful to me, since my experience in this area is very limited. Your suggestions will hopefully help me avoid making poor judgments that will come back to bite me later.<br><br>I know it was a long list of questions, and I appreciate your patience in addressing them all.<br><br>I am very grateful.<br><br><b><i>Jud White <jwhite@cdtag.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> 1. Yes, text in TCON is compliant. It's not defined as only a numeric <br>string.<br>2. The preferred way to delimit genres is with a null terminator, <br>although only a few apps/libs support this. There's no reason spaces <br>should break another reader.<br>3. TIT1 might be good for "Theme", if your software writes this frame. <br>The definition for TIT1: "The 'Content group description' frame is used <br>if the sound belongs to
a larger category of sounds/music. For example, <br>classical music is often sorted in different musical sections (e.g. <br>"Piano Concerto", "Weather - Hurricane").". If not, TXXX seems most <br>appropriate, but you mentioned MM doesn't support these either. Foobar <br>definitely allows TXXX. I would stay away from using COMM, because it's <br>not a comment, although iTunes and other software abuse this frame <br>liberally.<br>4. It doesn't break the spec that MM writes its own COMM identifiers, <br>but it is messy IMO. I wouldn't worry about it breaking another app, <br>but I would doubt another app would treat a MM COMM frame as anything <br>other than a comment.<br>5. TXXX is appropriate if you want to define your own metadata. A <br>populer one is "Album Artist" for compilation CD's. So you could have <br>TXXX/Album Artist/DJ Dara, for example. COMM is meant for comments, <br>maybe some notes about a live recording, or a press release about a CD, etc.<br><br>If
you use proprietary descriptors in COMM then you're righ to worry <br>about lock-in. You may be able to find someone willing to write a <br>conversion utility to take COMM/MediaMonkey frames and translate them <br>into whatever you're looking for in the future.<br><br>John Slane wrote:<br>> As you will be able to infer, I am pretty much a newbie to mp3 and <br>> ID3. I am about to begin tagging a few thousand mp3 files, and I sure <br>> would like to get it right the first time. I've read through the <br>> ID3v2.3 standard and I have experimented with modifying tags using <br>> mp3Tag and MediaMonkey. I look at how each program modified the tag <br>> by reading the tag with id3.exe. While I believe I understand the <br>> basics now, I have a couple of nagging questions that remain, and I <br>> hope that you can kindly help me out.<br>><br>> I want to use tag metadata to build "AutoPlaylists" in MediaMonkey. <br>> Basically, I'd like
to be able to tell my jukebox - for example - to <br>> play songs from 1968 that have the Genre = Soul or Funk AND the Theme <br>> = Cars or Dancing. This idea raises a few issues:<br>><br>> (1) A TCON (genre) frame in ID3v2.3 is defined as a numeric string. I <br>> notice, though, that both MediaMonkey and mp3Tag write alphabetic <br>> words into this frame (as confirmed by id3.exe). Is this in <br>> conformity with the spec, and might it cause any problem with reading <br>> the tag in other programs?<br>><br>> (2) Although only one TCON frame is allowed per tag, I was able to <br>> write multiple genre values into the TCON frame, simply by writing <br>> them as a string, delimiting them with spaces or other characters. <br>> MediaMonkey is able to then search on any portion of the string to <br>> make a playlist. Is there any potential problem (with any tag-reading <br>> software) that arises from putting multiple genre
values into the <br>> single TCON frame?<br>><br>> (3) Now I come to my "Theme" field. Since there is no declare Theme <br>> frame type in ID3 and no Theme field in MediaMonkey, I could sneak <br>> "Theme" values into one of MediaMonkey's predefined fields that I do <br>> not use; but it would, of course, be mislabeled. On the other hand, I <br>> could put my "Theme" values into a TXXX or a COMM frame. MediaMonkey <br>> does not create or recognize any TXXX frames, but it does offer a few <br>> user-defined COMM fields (Custom1 - Custom3). So I could use one of <br>> these, and use the Descriptor "Theme," and enter my multiple-valued <br>> theme data in as a string, with whatever delimiters seem appropriate. <br>> Does that make sense? Are there any kind of rules for choosing <br>> delimiters, in terms of compatibility with the world of software out <br>> there?<br>><br>> (4) When I do use one of MediaMonkey's
"user-defined" COMM fields, I <br>> note that MediaMonkey imposes its own descriptor on the tag frame. <br>> For example, if I enter "January" into user-defined field "Custom 1", <br>> I get the following tag frame:<br>> COMM = Songs-DB_Custom1 January.<br>> So MediaMonkey has predefined descriptors that it uses for its <br>> "user-defined" fields/frames. These fields seem to work just fine <br>> within MediaMonkey, for making playlists, etc. But will they cause <br>> problems for me in the future if I migrate my music collection to <br>> another jukebox software or some other software application? I fear <br>> that using the MediaMonkey jargon in the tag will cause me recognition <br>> problems elsewhere.<br>> <br>> (5) Considering Issues (2) and (3) together, I wonder about the <br>> difference between a text frame and a comment frame. For example, how <br>> are a TXXX and a COMM actually different (so I know which to
choose <br>> for what). Each one can have multiple occurrences in the same tag; <br>> each one takes a descriptor to distinguish it from its kin in the same <br>> tag; and each one accepts a text string as its actual data. So how <br>> are they different? Does one allow a LONGER string, or broader <br>> formatting, or what? I'd like to know when a TXXX is appropriate, and <br>> when a COMM is appropriate.<br>><br>> As you can see, I'm trying to figure out how to cram non-standard <br>> information (multiple genres, music themes, months of the year) into <br>> my ID3v2.3 tags. And my current jukebox (MediaMonkey) apparently <br>> gives my a couple of options for doing this, but they seem rather <br>> limited, and I worry that using them will tie me to this application <br>> for the rest of my life (unless I want to retag thousands of files). <br>> Any general advice you can offer on making universally acceptable tags <br>>
that contain non-standard metadata will be greatly appreciated.<br>><br>> Thanks for your patience in reading all this, and for any advice you <br>> might have on any or all of these issues. I feel a bit overwhelmed at <br>> the moment, and reluctant to begin tagging my collection until I get a <br>> bit more comfortable.<br>><br>> jaslane64<br>> Dublin Ohio<br>><br>> ------------------------------------------------------------------------<br>> TV dinner still cooling?<br>> Check out "Tonight's Picks" <br>> <http: us.rd.yahoo.com="" evt="49979/*http://tv.yahoo.com/"> on Yahoo! TV. <br><br><br><br>---------------------------------------------------------------------<br>To unsubscribe, e-mail: id3v2-unsubscribe@id3.org<br>For additional commands, e-mail: id3v2-help@id3.org<br><br></http:></blockquote><br><p>
<hr size=1>Everyone is raving about <a href="http://us.rd.yahoo.com/evt=42297/*http://advision.webevents.yahoo.com/mailbeta">the all-new Yahoo! Mail beta.</a>