iTunes AAC encoder output at 320kbps hurts my ears

Question

jamie1992 Author

Level 1

0 points

iTunes AAC encoder output at 320kbps hurts my ears

I've been encoding various classical, opera and easy-listening audio CDs (accurately-ripped using EAC) from WAV to AAC format.

When I encode with iTunes for Windows using AAC at 320kbps, the output file has a noticibly unpleasant sound. Bass and mids are good, but the higher frequencies sound very harsh. The effect is similar to that of "scrape flutter" - a problem sometimes encountered with analogue audio tapes. It's most noticible with high-pitched violins, whistling, etcetera.

It "grates on me" and makes the files unlistenable.

Has anyone else noticed this effect?

Thanks,

Jamie.

( Software versions are: Windows 7 , iTunes 10.3.1.55 , QuickTime 7.69.80.9 )

iTunes-OTHER, Windows 7

Posted on Jul 3, 2011 9:20 AM

Reply

Answer 1

ed2345

Level 9

63,658 points

Jul 3, 2011 9:43 AM in response to jamie1992

Has anyone else noticed this effect?

Jamie,

Actually the web is full of opinions about the various encoding formats! AAC/320 is pretty good for most purposes, but is indeed compressed from full CD-quality.

Given the concerns and knowledge evidenced in your post, I'd guess that anything less than CD-quality lossless would not be suitable for your case. So, stick to WAV, AIFF, or Apple Lossless.

You may also be interested in checking out better-than-CD-quality music from online download stores such as hdtracks.com or eclassical.com They sell in 96/24 format (compared to 44/16 which is CD-quality) that can be appreciated by an audiophile but is lost on most of us.

Reply

Answer 2

jamie1992 Author

Level 1

0 points

Jul 3, 2011 10:14 AM in response to ed2345

Hi ed2345,

Thanks for posting.

I would prefer to use lossless, but unfortunately the target device doesn't support it.

I realise no lossy compression scheme is perfect, but typically the output from mp3 and other AAC encoders is not "painful" to listen to when played back. They can often sound dull, flat and/or muddy, but the iTunes phenomenon as-described seems quite different to my ears.

Anyway, I've switched to using the Lame mp3 codec at 320kbps for the time being.

Jamie.

Reply

Answer 3

ed2345

Level 9

63,658 points

Jul 3, 2011 11:18 AM in response to jamie1992

Jamie,

OK, it is possible that iTunes has had some (undocumented) change to its AAC encoder. But if LAME MP3/320 is working for you, then that is the best solution.

Ed

Reply

Answer 4

jamie1992 Author

Level 1

0 points

Jul 3, 2011 1:32 PM in response to ed2345

It seems the iTunes AAC encoder has changed at some point.

I just tried encoding with iTunes 4 on an old PPC Mac, and the AAC files it creates do not have the harsh-sounding effect in the higher frequencies, although Lame mp3 encoder still beats them overall.

Jamie.

Reply

Answer 5

ed2345

Level 9

63,658 points

Jul 3, 2011 3:04 PM in response to jamie1992

jamie1992 wrote:

It seems the iTunes AAC encoder has changed at some point.

I just tried encoding with iTunes 4 on an old PPC Mac, and the AAC files it creates do not have the harsh-sounding effect in the higher frequencies, although Lame mp3 encoder still beats them overall.

Jamie.

Jamie,

Interesting. It is well known that iTunes has a cr**py MP3 encoder, but now apparently the AAC encoder has gone downhill.

Reply