On iTunes, Graphics, and Standards Documents
(Yes, yes, I should be asleep. What's your point?)
iTunes comes so very close in so many ways to being great, and falls short again and again. It's rather more frustrating than if it was just unusable, in which case I'd not use it and not worry about it further.
iTunes has a reputation for supporting ID3 tags pretty well. It is in fact the only implementation I have that claims to support ID3 v2.4.
I wanted to leverage the genre, style and tone information I already had from the All Music Guide to build some playlists for the iPod. A piece of cake, right? The genre part is pretty much free: put the genre name (completely ignoring the old silly numbered-code concept) in the TCON field (text: content), and iTunes & the iPod would make genre lists automatically.
ID3 v2.4 has added a "TMOO" (text: mood) tag which would work just fine for the 'style' information. Oops, but iTunes doesn't pay any attention to it. Ah, well, there's the TXXX fields, explicitely designed for user-defined text information. Nope, doesn't pay any attention to those, either.
Okay, then, comments. ID3 v2.3 supports multiple comment fields, so long as they have separate language and content descriptors. This is a fabulous way to allow users to keep semi-structured data attached to their files without walking on each others toes. Unfortunately, iTunes only supports one comment (the english-language comment named ""); or is it one per language, with comments appearing and disappearing as users with different language preferences log on? Well, that's a pain, but so long as I stick to a tag/value convention in my comment text, I'll be okay.
Oops, not quite. Although iTunes can read comments containing newlines just fine, there's no way to add newlines to comments in iTunes' comment editor. So, I can't add comments in iTunes -- a sacrifice I can live with, I suppose.
Oops, it still won't work. iTunes only reads the first 256 bytes of a comment field. Okay, shorten up my encoding format (instead of multiple nice lines like "Tone mellow", "Tone sensual", there's now one line like "T mellow|sensual"). Oops, some still too long; okay, throw away some random data.
Now, to script up some smart playlists. Oops, there's no scriptable way to make a smart playlist. Okay, script up some dumb playlists. God, I can't believe how much work this is turning into, but at least I'm learning AppleScript (ha!)
Okay, all that is done more or less satisfactorally. Or it will be, after I write another script to sort the playlists into the correct order, since iterating through a selection of tracks goes in almost-but-not-quite a linear order.
Now, on to cover art.
The APIC attached picture frame is similar to the comment frame in supporting multiples, but when iTunes creates the tag it's always type 0 'other' with no description, so we'll stick with that. (side note: type 17, "brightly colored fish"???). Update my auto-tagger, run it across my files, and...VOOOM, images!
Well, sometimes. "The Beatles", 1: yes; A Hard Day's Night (UK): no; Beatles for Sale: yes; Help! (UK): no; Let it Be: no; Past Masters: Volume 1: yes; Please Please Me: yes; Revolver: yes; Rubber Soul (UK): yes; With the Beatles: no; Yellow Submarine: no.
The ones that don't work, iTunes recognizes that there's an image, so it doesn't show the "Drop image here" logo. It doesn't show the image, though, just a white box. Clicking on it pops up a white window. Dragging it to the desktop, however, creates a clipboard file -- and double clicking that file opens up a window with the image. iTunes is clearly reading it and exporting it correctly, just not displaying it.
What's different between the ones that work and the ones that don't? Good bloody question.
2003-11-19 04:30:00
| Comments (4)
| TrackBack (0)
|
Computers::Macintosh