iTunes 24 bit AIFF Album Art

I concur with David on the duplicating via iTunes working for me. Select the songs, then under the Advanced menu, choose Create AIFF Version and it will make dupes which will accept artwork. You'll need to then delete the originals. I have only done this with 16/44 files converted via Max however, so I'll bet David's warning about it converting 24 to 16 is true. Chris, thanks for contacting Apple about this. I'll send in a complaint form as well. I've seen a few mainstream artists recently offering FLAC downloads and Max is the handiest tool to use for converting to AIFF, but this glitch is annoying.<br />

<br />

TheOtherTim<br />

<br />

Chris, have you tried to run <strong>coverArt</strong> script? <br />

<br />

It's a Python script which allows you to load album covers into iTunes, without attaching them to individual song files. Works with iTunes 8.0. Here's a link to a personal page of a guy who wrote the script: http://www.jacobweber.com/scripts/<br />

<br />

I use WAV files in my iTunes library and since iTunes doesn't support album art for WAV out of the box, coverArt script fixed my problem, supports all files 16 or 24 bit. and it works with AIFF as well, just did a quick test converted a 24 bit WAV file into 24 bit AIFF and added album art w/o any problems.<br />

<br />

I know it's more of a workaround but if you don't mind running a script once in a while to upload your album art it will fix your issues untill Apple fix iTunes... just a suggestion.<br />

<br />

<br />

Hi Dimsal - thank you very much for the information and link. I checked out the script, but don't think it's a solution that I would use or many of the readers would use. <br />

<br />

I looks like you need to run a "proxy" or what really is a packet sniffer / interceptor in order for everything to work. It is much more than a script.<br />

<br />

Let me know if you think otherwise, I'd be very willing to use this one if it's something other than my research suggests.<br />

<br />

Thanks again for the post!

Yes, basically it intercept iTunes' requests for cover art, and allow you to send your own images. They're sent back to iTunes in the same format that the iTMS sends them, so they work just as well. The script includes a basic browser-based interface for selecting images for each album. You can enter your own URLs, or search Amazon for covers.<br />

<br />

You'll need to have Python 2.4.3 installed, and not be afraid to edit your hosts file. If you want to search Amazon, you'll also need to sign up for a free Amazon Web Services account.<br />

<br />

I do realize it's a bit more work for a regular readers, that's why I suggested it to you personally, knowing you don't afraid to get your hands "dirty". In my own experience the only inconvenience is you have to edit your <strong>hosts</strong> file. And then when you're done you have to update it back to normal.<br />

<br />

At the end, I agree it's a temp workaround, not the perm solution for everyone. In my situation (I only use WAV files in iTunes) unfortunately this is the ONLY solution currently available. Perhaps it will help someone who was looking for something like this...

iTunes applies cover art with 24 bit Apple Lossless. I believe I was having no problems with iTunes 7.7. When they went to 7.71, I lost the ability to apply cover art to 24 bit AIFF.

Hi dimsal - I think the newest version doesn't require a hosts file edit. One step closer to being easy!<br />

<br />

Thanks for the detail on your followup post. I certainly did not mean to discredit your work-around. It was me who asked people for work-arounds :-)<br />

<br />

Thanks again!

Chris,<br />

<br />

I talked to Apple and had them put it in Radar for someone too look at.<br />

<br />

Thanks<br />

Gordon

Very cool, thanks a lot Gordon!

As a workaround for the 24-bit AIFF album artwork problem in iTunes, I purchased a copy of Media Rage ( http://www.chaoticsoftware.com/ ). Once I've converted FLAC or WAV to AIFF in Max, I then use Media Rage to add artwork and to modify other fields. Only then do I add the files to my iTunes library.

Hi david - Thanks for the Media Rage link. The app looks pretty cool and a tone of features.

I've reproduced the problem with AIFF, but for me, the solution is easy: the problem goes away once the file is converted to Apple Lossless.<br />

<br />

I just downloaded some albums from High Definition Tape Transfers and underwent a FLAC -> AIFF (via Max) conversion, then import to iTunes, then AIFF -> ALAC (via iTunes). The 24bit sample size and high sample rate were preserved during the entire process. And the files get a bit smaller.

Thanks for the tip, watchnerd! When I tried this in iTunes 7.x when the problem first appeared, the conversion resulted in 16bit/44.1kHz ALAC. However, I just tried it now with iTunes 8, and it seemed to work just as you say, with the added benefit of also saving disk space.

I just did a get artwork for John Mellencamp's "Life Death Love and Fredom", and it works with 8.0.1.<br />

<br />

Peter

Hi Peter - I just tested it and it's still not working.<br />

<br />

Is your AIFF 24 bit?<br />

<br />

Do you have another version of this album in your library that does have cover art?

Yes I do, Ok I see now, I'd forgotten that it worked if the album was already there. it is 24bit .aiff, imported from max.<br />

<br />

Peter

Hey Peter - I just figured out I was doing all of my testing on the one remaining Mac I own that didn't have the 8.0.1 upgrade!!!<br />

<br />

So, I tested everything and it works!! Repeat, 24 bit AIFF files support album art once again!!!

All good here as well! Great stuff. <br />

<br />

--<br />

djp

Good news, and just to verify, I went through the exercise of re-importing into iTunes an album of songs that I originally downloaded as FLAC (David Byrne and Brian Eno's recent album) and had converted to AIFF via Max, and which previously did not accept artwork. Re-did that with the new version of iTunes and it took the artwork when dragged into the Get Info screen. So, yay.<br />

<br />

TheOtherTim<br />

<br />

Wondeful that all the AIFF lovers had this fixed. I know it would bug the hell out of me if I was a big AIFF user.<br />

<br />

But can I ask an ignorant question: is there an advantage to AIFF compared to ALAC?<br />

<br />

Because from what I can tell, they're pretty much equivalent, except ALAC is smaller. Am I missing something?

watchnerd, alac is lossless and compressed and aiff is just lossless. Some other things like alac is stored within an MP4 container and aiff is pcm. The source is wikipedia. <br />

<br />

Now, its generally understood that having the computer stream the raw pcm without additional uncompression at the same time just sounds better. Removing the DMR prior to playback better as well. Play the file from a hardrive vs cd/dvd optical drive and hard drive rules. But wait solid state drive is better than regular harddrive. Finally, usb with async is better than optical/spdif. PS My opinion...we need to thank Gordan Rankin for the ultimate usb-dacs and Benchmark for the runner up! Did I say finally, less we forget that no matter what computer or OS or software we use, that we need to set it correctly! PS we need to thank Benchmark for the setup options. I would give my opinion on the best setup, but I dont want to start a war...hehehe.<br />

<br />

vortecjr

"Now, its generally understood that having the computer stream the raw pcm without additional uncompression at the same time just sounds better"<br />

<br />

By whom?<br />

<br />

If the file is lossless, and the uncompression is flawless, the bits should be the same and should sound the same. I don't understand the logic behind your allegation.<br />

<br />

Do you have any data to support what you're saying is 'generally understood'?

No raw data, but plenty of supporting evidence. Ill try my best, so have an open mind for the time being. <br />

<br />

Ok, why is it that some DACs are so called top 5% and others are not? They were made the same, they were made side by side, they have the same code and they were cooked together? Lets not try to answer the why, but understand that some are special and sound better for whatever reason. <br />

<br />

Why do cd players over sample the data and compare notes? The data should be the same if read twice or three times or eight times? Well it does so because of errors. No cd is perfect and some have scratches right? Again, lets not try to answer the why, but understand that no process is perfect.<br />

<br />

So now if your on board and have some faith in that no process is free of issues, then things always happen (Murphy's law) and you have two processes going on in tandem at very high speeds....I conclude that you have twice the number of possibilities to have issues and If you uncompress the FLAC with care and store/play the WAV it will sound better. Yes, you could argue that when you uncompress and store the WAV file that you also store the issues and no gain. I would replay, that when you uncompress with good software at a slower speed than playback that you minimize the issues and you get a better file to play back.<br />

<br />

My local dealer (who I trust) has been trying this for him self (things are slow with the economy being the way it is) and he confirms via audio tests. <br />

<br />

You say, "If the file is lossless, and the uncompression is flawless" well nothing is really flawless, but if you take steps to minimize the flaws then the music will sound better. <br />

<br />

Regards<br />

<br />

Vortecjr

"well nothing is really flawless"<br />

<br />

I think you're applying an analog mentality to a digital data process. And, yes, you can have completely error-free compression/uncompression. In fact, most of the time, you do.<br />

<br />

Lossless, but compressed, digital music files can be seen as analogous to compressed text files. If it uncompresses correctly, it can't be worse or better than the original because the content isn't any different from the original.<br />

<br />

If a file passes a checksum test, it is bit perfect and therefore can't sound different, unless errors are introduced elsewhere in the chain, because it isn't different.<br />

<br />

Regarding errors elsewhere: playback software can definitely introduce errors of its own, but that's true regardless of the file format.<br />

<br />

By the way, here is an example of a checksum test for files in WAV, AIFF, and ALAC.<br />

<br />

We start off with all three files:<br />

<br />

Kagemusha:cktest david$ ls<br />

Sonata.aiff Sonata.m4a Sonata.wav<br />

<br />

We then do a checksum on the original WAV file:<br />

<br />

Kagemusha:cktest david$ cksum *.wav<br />

305351298 116115932 Sonata.wav<br />

<br />

We then delete the WAV file:<br />

<br />

Kagemusha:cktest david$ rm *.wav<br />

Kagemusha:cktest david$ ls<br />

Sonata.aiff Sonata.m4a<br />

<br />

We then decode the ALAC file to recreate the WAV file, and then do a checksum on the resulting WAV:<br />

<br />

Kagemusha:cktest david$ /Users/david/Temp/xld/xld Sonata.m4a -f wav<br />

|===================>| 99% (Track 1/1)<br />

done.<br />

Kagemusha:cktest david$ cksum *.wav<br />

305351298 116115932 Sonata.wav<br />

<br />

NOE: The checksum is the same! Which means it is byte identical and a flawless recreation of the original WAV.<br />

<br />

Next, delete the WAV file again:<br />

<br />

Kagemusha:cktest david$ rm *.wav<br />

Kagemusha:cktest david$ ls<br />

Sonata.aiff Sonata.m4a<br />

<br />

And then recreate the WAV file again, this time by decoding the AIFF, and do the checksum test again:<br />

<br />

Kagemusha:cktest david$ /Users/david/Temp/xld/xld Sonata.aiff -f wav<br />

|====================| 100% (Track 1/1)<br />

done.<br />

Kagemusha:cktest david$ cksum *.wav<br />

305351298 116115932 Sonata.wav<br />

<br />

Again, a flawless, byte perfect recreation of the original WAV file.<br />

<br />

Watchnerd, first thanks for taking the time to conduct the test. We need to be careful in interpreting the data though. I am not saying that we need to be paranoid just careful. I agree that the compression and uncompression should be flawless. Now having the check sum add up doesn't make it bit perfect. The programs can't dish out 23bit word lengths or 25bit word lengths it has to output 24bit each time. Part of the error correction to achieve this is that it fills in for missing data based on other information. It may even guess right most of the time. Finally, software conversion is not the same as real time conversion during playback. My point is that you would need to compare the actual bits (every 1 and 0) and not the size of the file being produced during playback. In software conversion you can select slower speeds to insure the accuracy and you can't do that in real time playback. <br />

<br />

When the concept of jitter was introduced people laughed. People said computers are perfect and in equals out. Jitter is real and present in every conversion. The less conversions the less errors and if you have to convert use a better process like a good software at slow speeds. Some people spend thousands on better gear. All I am saying is to spend some extra time. <br />

<br />

Can we agree on flac for everyday and wav for those seeking something better?<br />

<br />

Regards<br />

<br />

vortecjr