I think it’s safe to say that I put iTunes through its paces more than most people do. As of this writing, I have more than 27,000 tracks in iTunes. That’s not a complete representation of my music collection. I’ve got another 40 or so CDs that I’ve acquired in the past month which will get ripped, and I’m in the process of re-ripping my existing CD collection to ensure that everything’s in ALAC. I mostly like iTunes, but there are some things that I wish would change.
Over-the-air podcasts
Once I have listened to an episode of a podcast on my iPhone, I’d like to be able to update that podcast to get the next podcast in the queue. I feel this pain most acutely on the weekends, when I’ve run out of podcasts on my iPhone but I can’t update since I sync my iPhone with my work Mac. I know that there are apps like Podcaster, but they require that I only listen to podcasts on my iPhone.
Device-independent podcasts
Related to the previous point, the only reason that I sync my iPhone to my work Mac is podcasts. I have some podcasts that I like listening to on my Mac while I’m working, such as the All Songs Considered live concert podcast. I shouldn’t have to think about where I’m going to listen to a podcast and decide which of my Macs/iPhones/iPods will be with me when I am going to be there.
Better auto-complete
Since I have a massive iTunes library, there’s a lot for auto-complete to draw from. But auto-complete also gets in the way.
This is most noticeable when capitalisation between what it’s trying to auto-complete and what I’m actually typing differ. Once I get past the point where iTunes gives up on auto-complete because my new entry isn’t in its database, it keeps the capitalisation that it already had. For example, I was entering the band name ALO today. I typed A, and it came up with Al Franken. Then I typed L, so it kept Mr Franken, but changed my upper-case L to a lower-case l. And then I typed O, but it still had the lower-case l there. In other words, I entered that information, don’t lose it.
Another potential improvement for auto-complete would be to match the composers field with the artist field. If I’m in the composers field and start to type the first letter of the artist’s name, don’t give me the first entry that matches that alphabetically. Give me that artist; if I keep on typing more, then maybe the song’s composer isn’t the artist. But it usually is, so save me a little bit of typing.
Improved ability to update an album
As I mentioned earlier, I’m going through my CD collection. Since I’ve been using digital music for years and years, my music is in a variety of formats. As I re-rip my discs, I delete the old version. I’d love to be able to select the old version and tell iTunes that I’m updating this album, and thus keep its tags and metadata. I know that I can do this if I’ve kept all of its tags the same as what’s in the CDDB, but I correct the tags on my files when there’s incorrect or incomplete information in them. I don’t want to lose the metadata because the CDDB is wrong.
Better handling of the “composers” field
Today, the composers field is just treated as a single text-entry box. But modern music usually has multiple composers. I’d like them to implement some kind of delineator (slash or semicolon would work well). Then I could have auto-complete work on the individual composers of a song, instead of the whole list of composers of a song. For example, Michael Stipe’s sister Lynda has writing credits on a song on Fables of the Reconstruction, so I’d love to be able to type “Bill Berry; Peter Buck; Mike Mills; Lynda Stipe; Michael Stipe” for that song and save myself a little bit of typing since everyone but Ms Stipe is a composer on another song in my library.
Carriage returns in comments
I love the comments field. It makes my geeky little heart sing with joy. I’d love to keep more information in the comments field, but it’s hard to do so because I can’t use a carriage return to provide visual separation. I don’t want to write a novel in the comments field. For example, I have a smart playlist for “covers”, which looks through the comments field for that string. I also use the comment field for live songs, to note when and where they were recorded. Without a carriage return, a song which has both of these pieces of information is messy. It’s keeping me from using the comments field for other smart playlists, too.
What improvements would you like to see in iTunes?
Regarding your first point; I thought I’ve downloaded podcasts through the iTunes app directly onto my iPhone and had them copied back to my Mac the next time I synced–am I imagining something?
I would love them to split the device syncing capabilities into a separate app (say, iSync?) so my copy of iTunes doesn’t freeze up whenever I plug in my iPod; but that’s just me. 🙂
I think you’re imagining something, so I’d love to hear confirmation.
I completely agree about iTunes freezing whenever I plug my iPhone in. I try to remember not to plug my iPhone in until I go to lunch so that I don’t hit this, but I’m never entirely successful.
Yeah, I just did it.
iPod app -> Podcasts section -> selected a podcast -> “Get New Episodes” appeared after the last item in the list. Tapping it sends you to the iTunes app where the podcast page is displayed and you can tap to download new episodes. Just plugged my iPhone into my Mac and I got “Transferring purchases from iPhone” during the sync and now that podcast is on my Mac as well.
Perhaps you have to add the podcast through the iTunes Store (that’s what I’ve always done)–you can subscribe manually to an address, can’t you? I’d guess that might not work.
You do realise that iTunes contains a tool to convert files MP3’s for example to M4A’s… no need to sit there for hours re-ripping… just convert them!
What’s the point in converting a lossy format like MP3 to anything else? If you’re converting it to another lossy format, you’re just increasing the loss. If you’re converting it to a lossless format, you’re preserving the loss, only in a larger file size. Re-ripping to ALAC gives me lossless files.
I’m actually going through a very obsessive-compulsive process for this whole thing, which I probably shouldn’t admit to because it’ll make me sound crazy. But why else should I blog, if not to sound completely crazy? I’m listening to each CD at least once through (sometimes more, when I love the album) to ensure that the disc itself is fine. Then I rip the disc to ALAC, including getting all of the metadata tags correct. (This step is hardest on compilation albums.) Then I catalogue the CD in Delicious Library, again making sure that the correct information is in there. I’m going through all of my discs in alphabetical order, and I’ve just gotten up to Jeff Buckley, so I’ve got a ways to go. Compounding the problem is that I do the same thing every time a new disc enters the house. I acquired about 80 CDs in December and January, so I’m going to be stuck on whatever’s after Mr Buckley for awhile.
Once this is all done (which, at the rate I’m going, is probably going to take eleventy billion years), the next step is to rip the audio off of all of the official live DVDs that I’ve acquired over the years. This one is more difficult because there isn’t Mac software that will get the raw AC3 or PCM files off of the disc and convert them to something listenable. I’ve cobbled together a solution using Mac the Ripper, mAC3Dec, and PCM2AIFF. It’s quite time-consuming, so I’ve been putting it off in the hopes that a better solution will come around. I’ve documented it on a thread at the MacRumours forums.
iTunes will allow a carriage return in the comments field if you cut and paste the character into the field. For example, use text edit to create a blank line by pressing enter and then select and cut that line from text edit. This can then be pasted into the iTunes comments box.
Not a great solution, really just a nasty hack but it works with iTunes v10.1.2 and some earlier versions. Since this works it is curious why Apple disallows the carriage return in the comments field.