jhollington said:
Unfortunately, not at this time.
The image database only exists on the iPod photo itself. In iTunes, the artwork is only stored within the MP3/AAC file. It transfers it to the image database when you sync the song to your iPod (assuming that you have the "Display Album Artwork" option turned on).
So this does mean that you're technically wasting some space on the iPod by storing the album artwork, and of course with 700x700 images, that's probably a larger amount than strictly necessary, since the iPod photo itself only displays them at 140x140 and 50x50, but unfortunately the full image size is what gets stored in the MP3/AAC file.
You could resize the folder.jpg files before importing them into iTunes, but you'll have to decide whether that's worth the trouble or not... To do the math, consider the size of each existing folder.jpg file multiplied by each MP3 file in that respective folder (since the artwork has to be stored in each MP3 file individually).
Ok, I know about the image DB in the iPod.. Did some calculations:
Resizing covers with Photoshop to 140x140 and saving them optimized for size (Save for Web option) gives a file around 6-8k. Multiply that by an average of 12 songs per album, you get something below 100k so that's reasonable.
Now, the iPod will have in addition to that, 2 "BMPs" of 140x140 and 56x56 so 39200 Bytes + 6272 Bytes so around 45k.
Now does it create an entry in that DB for each song or does it reuse the same copy for all MP3s.
If it reuses them, with an average of 12 tracks, that would mean about 150k per album of overhead. At 50 Megs per album average, that's 0.3% overhead. So if you fill up 30 GB, you endup with 90 Megs of covers.
If it doesn't reuse it, then you have to count 45k + 6-8k per track, so for a 12 Track album, it will take up about 650k per album, so using the same 50 Megs per album average that gets to 1.3% overhead or 390 Megs of cover.
Considering the size of my collection and how much space there will be to spare on the HDD, I'll be ok with that.