Although Apple’s iTunes program is very good at keeping a computer-based library synchronized to an iPod automatically, or for manually transferring tracks from your computer’s iTunes library onto your iPod, it provides extremely limited functionality for transferring information in the opposite direction—from your iPod back to your computer.
One of the likely reasons for Apple to have taken such a restrictive approach to this is to combat piracy and thereby maintain good relations with the music labels that are currently selling their content via Apple’s iTunes Store. In reality, however, there are any number of legitimate reasons why a user may want to copy music from their iPod back to their computer, such as recovering from a catastrophic system failure, or easily transferring a large iTunes library over to a new computer.
Before we get into the details of how to copy media content from the iPod back to your computer, it’s important to begin with a discussion of how that content is actually stored on the iPod. An understanding of how the iPod stores its content will make it more clear as to what the various recovery or copying options actually do, and help decide on what the best option is for a particular situation.
Unlike many other portable media players, the iPod stores its content using a database methodology. iTunes copies the content itself to a hidden directory structure on the iPod and then updates a database stored on the iPod. It is this database that is used both by iTunes and the iPod interface itself to index and catalog the content that is stored on the iPod.
For the most part, this database information is gleaned from the internal header tags within the media files themselves, in much the same way that iTunes indexes and catalogs your media library. Information such as the track name, artist, album, genre, and a myriad of other information that you can find for each track in iTunes is actually stored in each file, and the name of the file has no bearing on what iTunes or the iPod sees or how it catalogs any given media file. In fact, the only time the file name is ever used by iTunes is if the tags themselves are not present.
The iPod database also contains additional information about your music that is not normally stored within the tracks themselves. This includes your playlists and the listing of their content, as well as track metadata such as rating, play count, last played time, skip count, last skipped time, and more.
This particular means of storing information on the iPod has both advantages and disadvantages. The major advantage to this approach is that music is catalogued in such a way that it is easily and rapidly accessible from the various menus on the iPod itself, without having to search through individual track information or build a separate cache. The disadvantage is that the music must be tagged properly in order for this to work, and of course this obscures the actual layout of the music files themselves, making it more difficult to find and copy specific tracks from the iPod back to the computer.
Fortunately, a number of third-party utilities have been developed that can read these iPod databases directly, and use them to not only locate specific tracks to recover, but in some cases even recover playlists and other additional metadata such as rating and play count.
On the iPod itself, all of the internal iPod information is located in a hidden folder called iPod_Control. Most of the information in this folder pertains to internal iPod operations, such as device configuration and settings and the library database described above. However, beneath this iPod_Control folder is a Music folder that contains all of the individual audio and video files that are stored on that particular iPod. The only information not stored here is photos, which we will discuss separately later in this article.
The files in the Music folder won’t necessarily be organized in any meaningful way for a human, since they are expected to be accessed via the iPod’s library database, which contains all of the information and other metadata for each track cross-referenced with the location of these individual files.
Disaster Recovery
So you have a nice big 80GB iPod with your entire media library loaded onto it, synchronizing automatically with your iTunes library, when suddenly the unthinkable happens… Your computer’s hard drive decides that it’s been spinning for long enough, and gives up on you.
You now suddenly find yourself in the position where your only copy of your music library is on your iPod itself, and you need to get those tracks back off the iPod onto your computer, so you can rebuild your iTunes library.
In a situation where you’ve been using automatic synchronization with your iTunes library, and you suddenly find you no longer have an iTunes library to sync with, there are a couple of additional considerations that are important to keep in mind.
Automatic iPod synchronization from iTunes is, for the most part, a one-way experience. Some information does come back in the other direction, such as ratings and play counts, but the bottom line is that iTunes considers the library on your computer to be “authoritative”—meaning that the iPod mirrors the iTunes library, rather than the other way around.
The unfortunate downside to this is that if you have an empty iTunes library on your computer, an iPod that is automatically syncing to it will happily mirror the content of your empty library. In other words, everything on the iPod will be deleted and replaced with, well… nothing.
The good news, however, is that this is only really a problem if you’re actually using the same library as you were syncing with before. iTunes is intelligent enough to notice when an iPod that you connect was previously associated to a different iTunes library database, and prompt you with a warning as to what you want to do next:
If you are trying to recover your music from your iPod, you obviously do not want to select Erase and Sync. Simply click Cancel instead, and your iPod will remain connected to your computer, but the auto-sync process will not run.
