Optimal CDEx Settings

I couldn't find a review, comparison or guide for CDEx settings when using the Lame encoder so I did some playing around today. Before today I just set CDEx to a bitrate of 192 and forgot about it. Now I'll be going back and re-ripping a bunch of disks that I actually like to hear, because I expect my MP3s will be around longer than a bunch of my CDs and they're a whole lot handier.

Since my desktop speakers suck I tested with my daughter's Sennheiser HD437 headphones (a good deal for the sound), my old Sony MDR-AV5s (don't look, they don't exist anymore), and then my Sony inner-earphones (MDR-EX51LP). First conclusion: the Sony in-earphones aren't as good as I thought; fine for the laptop when EQed, not so great when compared with decent headphones. Though it doesn't affect the results here, the old Sony set was the best sounding and the Sennheisers (surprisingly) ran a hotter signal.

The computer has a garden variety sound card, the CD drive is actually a generic CD-RW/DVD-R, and I played everything through WinAmp with a flat EQ.

I used the Breeder's old Safari EP for the test -- Do You Love Me Now? and Safari were the tracks I picked. This EP was originally recorded and engineered on tape and later encoded for the CD, and for this purpose that means there's more to hear; on a good system you can tell where channels and effects punch in and out, and background sounds from the studio aren't edited out. When you can hear Kim Deal lick her lips between notes, that's a good thing.

These will be my settings until I find or hear something new...

Thread Priority: Above Normal.
It doesn't make a difference to the sound, but does make ripping go faster.

Version: MPEG I.
Set it to anything else and the bitrate maxes out at 160.

Bitrate Min/Max: 192/320.
Set to VBR and you get a range instead of just one bitrate setting. I first tried 160/320 and the sound was noticeably warmer and nuances were better defined at 192. To me, it was worth whatever size it added. I later tried 256/320 and the difference wasn't as impressive. Though the actual bitrate varies, Winamp reports a single value which I would guess is the average and the tracks I tried reported 238 and 268 at 192/320 (for an extra 1Mb per file), 285 and 286 at 256/320 (.5 Mb difference). So the reported bitrates went up by 47 and 18 respectively, and while the sound was closest to the original CD, I didn't hear anything new and the difference didn't justify the extra storage.  192/320 is where I'll live.

Mode: Stereo.
Definitely preserve the original channels. The alternatives save space in ways that seem to me like saying "sometimes mono is just as good."

Quality: Very high (q=0).
At min/max bitrates of 160/320 and a Quality setting of High (q=2) I saved about 200k per song vs. Very High, but there's a slight choppiness that comes off like stair-stepping in the wave. At 256/320 the files sizes were identical so this seems to be a relative setting that may not come into play at high bitrates. If it does make a difference, I'll take the setting that isn't liable to sound choppy at lower bitrates.

On-the-fly MP3 Recording: Disabled.
This copies the track to the hard drive before running the final conversion. When enabled you get occasional stutters in the output, and I suspect it's worse with badly scratched CDs since you're relying on the drive mechanism to stay in synch with the codec that much more.

VBR Method: VBR-MTRH.
Variable bitrates mean that extended silence takes less to store than a busy section. Rather than rip everything at 256 or 320, this sounds like a good idea to me. VBR-HTRH was indistinguishable to me from VBR-New, and produced the same file size. It's a hybrid between VBR-Old and VBR-New, so why not.

VBR Quality: VBR 0
Lower is better. One of the few things I didn't bother to test changes with.

With these settings and the Sony headphones I could hear as much in the recording as I'd expect from a good set of monitors -- mistakes, breaths, the natural reverb of the room on the vocals, gating on the drum mics -- that's as much information as I expect from an inherently lossy format like MP3, and better than I expected.

Something I didn't expect happened when I let the CD run from Safari (track 3) on to track 4. I've long complained that when listening to a lousy cd player -- and this one's obviously designed for data, not music -- everything seems to stutter, like the sound really is delivered in digital chunks one after-an-other rather than as a smooth wave. So I ripped track 4 to the above "best-of-all-worlds" setting too, and the stutter disappeared. Whether the stutter was caused by a scratch or a lousy mechanism I don't much care, reading from a reliable medium solved it. If all it means is that you're better off ripping to a drive than playing cds through a computer, then hey, I learned two new things today.

Published Sunday, March 27, 2005 6:18 PM by erobillard
Filed under:

Comments

Sunday, March 27, 2005 8:36 PM by Chris

# re: Optimal CDEx Settings

If you're looking for the absolute best quality in MP3, you should really use the latest stable LAME with the --preset-standard switch. You can choose to use an external encoder in CDex, then apply that switch to it.

This switch has been tuned by the LAME developers and the community using blind tests to be completely transparent (aka "CD Quality"), and creates files with bitrates around the 190-230kbps range.

Take a look at HydrogenAudio.org (where developers for most audio codecs hang out) for more information about it.
Monday, March 28, 2005 12:05 AM by Eli Robillard

# re: Optimal CDEx Settings

Thanks for the lead! The best reference I can find for the "-preset standard" switch is here (step 29): http://eac.forgiven5.com/eacsetup.htm

I'll have to give it a whirl and see if it's for me. Given where my preferences landed (averages of 238 and 268 for these tracks and unhappy below), my next test would be to see if I can bring the max bitrate down for a min max of 192/256 which should be close to what the "-preset standard" switch hits, and then give myself a double-blind between the new setting and the switch.

I'm a bit skeptical that I'll prefer the switch, I'm sensitive to the highs that split the verdict in this range and turned out not to like 192 CBR too well when I put it through decent gear. Real curious to try it out.

Quick story about being sensitive to highs -- those deer whistles they put on cars in deer-infested areas drive me nuts. Can't be in a car with one above 80kph. And given than when my friend John hit his second deer it knocked the whistle right off, so I'm not so convinced the deer know they're supposed to avoid the sound either, but that's another story.

For anyone else who's reading, the version built into CDEx is at least Lame v1.92, the current version on SourceForge is 1.96.1. The "last stable" version listed is 1.90.

Again, thanks for the post, I've learned a ton today.
Monday, March 28, 2005 12:13 AM by Eli Robillard

# re: Optimal CDEx Settings

Er, and one of the other things I was reminded of today was "Exact Audio Copy," which is the most exact way to turn CDs into wav files. If drive space were cheap enough to store full wavs, this will be the way to archive a collection.

So do you think it would make a difference if you're compressing the audio anyway, whether you're starting with a "regular" wav rip (or read) from CD, or starting with an EAC wav rip from CD? Or is this something only a deep sound geek would brag of?
Monday, March 28, 2005 2:36 AM by Chris

# re: Optimal CDEx Settings

It really all depends on how much you trust DAE on your drive. :P

EAC is nice in that it gives you all the tools you need to make sure you get bit-perfect rips from your CDs. Things like test-and-copy with CRC compare and gap detection are very nice.

That said, if your CDs are in good condition and you have a good drive, CDex should do you just fine. It's best to use it on full paranoid mode for the occasional scratch, though.

Also, have you ever thought about using a different lossy codec (such as Musepack(mpc)) or even going lossless? If, after a double-blind test you still find MP3 lacking, it may be worth a look. There are good FAQ's on HydrogenAudio about all the different codecs though, so I won't repeat them. :P

For what it's worth, I use EAC test-and-copy and compress using Musepack --standard --xlevel. I don't have a portible audio player (I must be the only one by now ;)), so portability doesn't worry me and Musepack is known to be the best lossy codec for bitrates in the 150-250kbps range, so it suits me very well.

Good luck. :)
Tuesday, April 05, 2005 9:27 AM by Latest Lame encoders

# re: Optimal CDEx Settings

The latest LAME encoders are numbered 3.xx, ie 3.92. -- not 1.xx.
Sunday, April 10, 2005 6:07 PM by Richard

# re: Optimal CDEx Settings

In terms of audio compression, it's not all-or-nothing.. there is a happy medium between the data loss of MP3, and the massive files of WAV, and that is lossless compression.
There are several codecs which can compress your CD audio with absolutely no data loss. Sure, they won't get the files as small as MP3, but it's still about half the size of a wav, and they sound great.
The two most popular lossless formats are FLAC (flac.sourceforge.net) which is completely open source, and Monkey's Audio (monkeysaudio.com) which is open source with various licencing caveats.
Tuesday, April 12, 2005 7:58 AM by scottws

# re: Eli Robillard

I'm the author of the EAC setup guide you listed. Most of my information and knowledge is gleaned from HydrogenAudio.org which Chris already posted about. I suggest going there and reading up on -preset standard or --alt-preset standard (same thing, just different versions of the LAME encoder). Hydrogen Audio will have a lot more information than my guide does on the subject.

The best place to start is here: http://www.hydrogenaudio.org/forums/index.php?showtopic=28124. Another good reference is this: http://www.hydrogenaudio.org/forums/index.php?act=ST&f=16&t=593
Monday, May 29, 2006 6:37 PM by moutray.com » Optimal CDex Settings

# moutray.com » Optimal CDex Settings

# AVforum.no - skal rippe cd samling, lurer p? hvilken kvaltitet

Wednesday, May 16, 2007 12:18 AM by Savior Machine » links for 2007-05-16

# Savior Machine » links for 2007-05-16

Thursday, July 05, 2007 11:50 AM by ANdrew Schneider

# re: Optimal CDEx Settings

Any updates on settings here? Also, do folks have a better ripper that they use? I use Cdex and have no complaints, but I was wondering what the experts think. Thanks!

# Man with a Plan » Blog Archive » Optimal LAMEEnc compression settings?

Pingback from  Man with a Plan  » Blog Archive   » Optimal LAMEEnc compression settings?

Sunday, October 12, 2008 12:48 PM by P2P_DownUnder

# re: Optimal CDEx Settings

This is how i rip my MP3s with CDex 1.70 beta 2

Tag: ID3-V2

No Normalization

Filename Format: %A\%Y - %2\%A - %Y - %2 - %7 - %4 - %1

(makes it nicer to look at in explorer with albums organised chronologically automatically becoz of the albums year being in front of the name. the end filename also means that if you have several different artists and albums copied and pasted say onto a phone memory stick, then it will sort them by artist name, then album year, then album, (then track no. obviously).. its not great looking in the folder, but as long as your tags are right, any mp3 player will just show the tag info, not display the lengthy filename

Playlist: %A\%2\[Playlist] %A - %Y - %2

I'll add things like album covers (pictures) in the same folder as all my mp3s for a given album, so i have a system where everything except for the track mp3s start in [square brackets] and provides a basic description of what the file is, before the detail is read afterwards

Ripping Method: Paranoia, Full

UNTICK Use Native NT SCSI Library

LAME MP3 3.97 beta 2

Stereo CBR 320kbps Very High Quality (q=0)

UNTICK MP3 on-the-fly encoding

Tuesday, January 20, 2009 9:34 AM by Concerned

# re: Optimal CDEx Settings

I can't remember the last time I read such complete and utter bullcrap regarding LAME settings. Eli seems to have taken it upon himself to decide that he knows FAR more about LAME than the developers or the community who've helped tune it over the last decade do.

Ignore this idiot and use the presets. They ARE the best that can be done because they've been fine-tuned by people who actually UNDERSTAND the encoder, what it is, and how it does what it does. Eli quite clearly has no idea whatsoever! :(

Leave a Comment

(required) 
(required) 
(optional)
(required)