EAC ripping & encoding tutorial


Recommended Posts

After seeing many people ask about ripping and encoding audio CDs here, I have decided to make a little tutorial for people who want to make the best possible rips as well as encoding quality. EAC (Exact Audio Copy) is used to extract the audio as well as direct the encoding and tagging of the extracted wav files. EAC uses the best in audio extraction and error correction to ensure the highest possible end result. This guide will cover both MP3 and OGG audio compression options. MP3 is the most popular standard with very good transparent quality possible. OGG Vorbis is also used which is a newer compression which delivers better compression then MP3 as well as growing support.

I. Downloading needed files.

ASPI - allows your CD-ROM to rip audio

EAC ? used in ripping, encoding, tagging

EAC profiles ? easy setup pre-configuration of EAC

LAME MP3 ? the MP3 codec

Ogg Vorbis ? the OGG codec

II. Installation

First install the ASPI files. After installing you must REBOOT for these files to take effect. Second is to install EAC, it will ask you to search for LAME.exe and ask question about audio ripping, skip these as the profiles will take care of this. Next is to install the EAC profiles which should be extracted to the C:\Program Files\Exact Audio Copy\Profiles\ directory. Second is to download and extract the lame.exe and oggenc.exe into the C:\Program Files\Exact Audio Copy\ directory.

Now lets get EAC setup to we can start ripping and encoding audio. Let?s first set the default output directory to which you want your encoded files to go. To do this go to File, EAC options, and then the Directory tab and direct EAC where you want your files to go. Next let?s check out your CD-ROM/RW/DVD drive specs to see what ripping methods it supports. Go to File, Drive Options, and then Detect Read Features. You will want to have an Audio CD in the drive now that has a few light scratches so EAC can detect your drives features. Its best to use secure mode but if its too slow for you and you don? care so much about quality and possible clicks, check burst mode.

eac3.gif

Lastly you need to put in an email address of any kind from the File, freedb settings. It?s also good to update the freedb server listings here too. Now you can select the profile of the format you want encode and click load. Click on the CD icon to get the artists and song title info, make any changes to the genres or enter the date. Next, simply click the MP3 icon on the left to rip and encode to your specifications.

eac1.gif

This is a work in progress here, just really want people to start using decent audio compression as well as good quality ripps.

Edited by username
Link to comment
https://www.neowin.net/forum/topic/77696-eac-ripping-encoding-tutorial/
Share on other sites

When using high bitrates (-q5 to -q10) use Oggenc GT3 by gharf over at sjeng.org. Results almost rival Musepack. It fixes "preecho" and allows for better bit allocation.

Your URL for LAME also seems to be broken. Latest stable binary can be found here at Rarewares. When ripping with LAME it's better to set it up as an external encoder rather than using the EAC DLL which produces unpredictable results.

Secondly, C2 correction should be disabled even if your drive is capable of it.

Edited by Animaniac
  ToastGodSupreme said:
That was a bit brief. You didn't cover the one thing that I had a huge problem with when I first started using EAC:

Getting it to use a CONSTANT bitrate instead of a variable one.

This is what I finally came up with in my compression options:

Why would anyone use CBR?

  Animaniac said:
I believe tags itself, if you tell it that you're using Ogg Vorbis in the external encoder pane.

Yeah, just tried it again, and it did tag the files--first time might have been a fluke. I am digging ogg though. :yes: :cool: Just wish there was greater hardware support, and a WMP plug in would be nice.

  Mav Phoenix said:
Yeah, just tried it again, and it did tag the files--first time might have been a fluke. I am digging ogg though. :yes: :cool: Just wish there was greater hardware support, and a WMP plug in would be nice.

WMP plug-in via DirectShow filter is availible here: http://tobias.everwicked.com

^_^

  Animaniac said:
When using high bitrates (-q5 to -q10) use Oggenc GT3 by gharf over at sjeng.org.? Results almost rival Musepack.? It fixes "preecho" and allows for better bit allocation.

if you notice the profiles i have to download, there is a Ogg GT3 one, thats what i use personally, didn't mention it in the thread because i don't want to get too complicated here

  Mav Phoenix said:
When you rip to ogg, how can you have EAC tag your files?

If you use the profile, it will tag it automatically, make sure the "add id3 tag" is disbled as well for ogg vorbis

should look like this

eac4.gif

you will want the commant line to be this

%s -q 6 -t "%t" -a "%a" -l "%g" -c "comment=EAC: v1 ogg @ q6" -G "%m" -d %y -N %n

and you can change the comment tag to you liking

  zivan56 said:
Or you can just use CDex which has all of those Codecs built in.

but EAC has is more secure ripping for quality, but CDex does the job nice too

Edited by username

Is there any good user manuals for encoding with ogg? I recognize some of the parameters that you listed but It'd be nice if there was something that I could look at as a reference and as a means to learn more about this format.

edit:

Is there anything that I could use in order to join ogg files? I have some classical stuff that I just ripped but the one piece is broken up into movements by track on the CD and I'd like them all to be in one ogg file, if you know what I mean. Or is there a way to rip a grouping of tracks into a single file?

Edited by Mav Phoenix
  • 4 weeks later...
  • 2 weeks later...
  • 1 month later...
  • 1 month later...

may i just suggest an awesome plugin for Winamp which allows ripping CDAs to MP3s? no need for a software, if you're using Winamp, simply download, install, download the CD-reading applet/patch/plugin and you're set.

Chun Yu Shei-'s MP3 Ripper for Winamp (don't ask about the name)

  Quote
Rip CDs to MP3 directly with Winamp! Why use a different program to rip CDs when you can rip them with Winamp? No ACM codec required either! Be sure to grab the CD Reader plugin from http://www.url.ru/~copah/ if you want to rip CDs (and read the help file too). The help file is HTML help, which most versions of Windows should be able to read. If you can't read it, go to www.microsoft.com and get the HTML Help viewer. You can use VBR and ABR encoding and select how to name the output. New in this version: Can add ID3 tags to output. Added option to display speed statistics after encoding each file (don't use it when you want to encode a CD, since a dialog box pops up after each track).
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Hello, Yes, and yes. More specifically, there are lots of features in Windows that I do not use--I cannot recall the last time I needed to run EUDCEDIT.EXE or ODBCAD32.EXE on a computer I own, but I'm sure that for some people they are useful, and for a smaller set of people they might even be indispensable. I don't begrudge Microsoft for including them as part of the standard Windows installation nor the people who need such tools; sometimes it is convenient to have some little utility or feature readily available. One thing I do begrudge is Microsoft's over-reliance on its own telemetry, and perhaps surpisingly on the flip side, customers who disable it. Collecting telemetry is generally a good thing, if it is done for good reasons and does not include any customer PII. However, how you interpret that telemetry is even more important, as that can lead to all sorts of disastrous decisions. On the customer side of things, telemetry is your "vote:" it's how you tell companies what features you use in the program, and lets them prioritize things appropriately. One glaring example is Windows 8, which shipped with the full-screen Start Screen because Microsoft's telemetry told them the average Windows user pressed the Windows key to bring up the Start Menu less than once a day. I have often wondered how many "power users" of previous versions of Windows (XP, Vista, and 7) that relied on the Start Menu disabled the telemetry that would have told Microsoft a difference story about its usage. More recently, I came across a young lady who had a problem with a third-party sync program on her computer running Windows 7. An update for the utility removed Windows 7 compatibility, and broke her backup process. Now, support for Windows 7 ended over 5 years ago in 2020, but there are ISVs who still support their software on it, but decisions about stuff like that are made, in part, by knowing what percentage of your customer base is on what operating system version. When I asked about that, she mentioned she had specifically disabled the telemetry from the sync program to its developers, which was optional to begin with. What made things even worse was that this was an open source utility, and its authors had a very clear, well-designed and scoped policy on the telemetry they collected, the pains they went through to avoid collecting any PII, and even other ancillary risks involving information disclosure (like just using of the software) because of the network connection made for the checks. Yet, she took herself out of telling the project maintainers "Hey, I use your software and I'm running Windows 7" by disabling the telemetry checks, which could have let them know they needed to continue supporting it. In a sense, sending telemetry is just like voting: Individually, you may not think it matters much, but it is often the basis for very important decisions. Regards, Aryeh Goretsky
    • Hello, My thoughts on this are mixed. Microsoft has hosted malicious code in the Microsoft Update Catalog where third party device drivers are stored; I wrote about one such incident about fifteen years ago, so if there are any other old malicious drivers floating around in the catalog, this will be a good step towards preventing any infestations from reoccurring. Another thing, which surprisingly is not mentioned in Microsoft's announcement, is that this helps protect against BYOVD (Bring Your Own Vulnerable Driver) attacks, where malware either comes with or downloads an older device drivers with vulnerabilities in it that can be exploited to gain access to kernel memory. Removing all those old device drivers from the Windows Update Catalog, potentially with all sorts of undisclosed vulnerabilities in them, means an attacker can no longer leisurely count on being able to download them from Microsoft's servers--something that may go unnoticed or ignored by security analysts. This makes the adversary attack a little more noisy, since they have to either include the device driver with the rest of their initial payload or download it from a third-party site at some point prior to beginning their BYOVD attack. On the other hand, it means that people who are looking for a specific version of an older device driver for whatever legitimate reasons, like compatibility, performance or stability, may end up going to dodgy third-party sites in search of older drivers, which increases the risk of exposure to everything from nuisance advertisements and unwanted software to actual malicious code. As for me, I have keeping copies of all the device drivers, firmware updates, etc. I have downloaded over the years, some dating back to DOS and Windows 3.x era, not just for hardware I won, but popular things like unified chipset and video card drivers, just in case I ever needed it. It might seem silly to collect such a thing, but the hardware drivers, firmware updates, and documentation are just about 2 TB in size. From my perspective, it is an inexpensive form of insurance, especially given that disk space is always getting cheaper over time. Regards, Aryeh Goretsky
    • @Raze Bold it boy. (I admit, we all did it from time to time..)
    • Fan Control V227 by Razvan Serea Fan Control is a powerful and versatile portable utility that allows you to monitor, control and customize the fans of your GPU and CPU to keep your machine cool and running smoothly. Fan Control supports a wide range of devices and hardware configurations, giving you complete control over your computer's cooling system. Fan Control backend is mainly based on LibreHardwareMonitor, an open source fork of the original OpenHardwareMonitor. This means that hardware compatiblity is entirely open for anyone to contribute, and doesn't rely on a single developer who may stop caring at some point. Combined with the plugin system, Fan Control is unlocked for many generations of hardware to come. Main features Guided setup process on first launch Save, edit and load multiple profiles Change the theme and color of the application. Multiple temperature sources ( CPU, GPU, motherboard, hard drives... ) Multiple fan curve functions, including a custom graph Mix fan curves or sensor togethers (max, min, average) Low resource usage Advanced tuning with steps, start %, stop %, response time and hysteresis FanControl V227 changelog: Allow decimal with hysteresis values Radeon Pro support through ADLX Fix a bug when cancelling the graph editing dialog Update LibreHardwareMonitorLib Download: FanControl V227 | Installer ~15.0 MB (Open Source) View: Fan Control Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Lol tf you are talking about. People are PAYING by using this app exclusively, just indirectly. Do you have any idea how much facebook charges for api access to WhatsApp which has become more or less a monopoly in e-commerce.
  • Recent Achievements

    • Contributor
      GravityDead went up a rank
      Contributor
    • Week One Done
      BlakeBringer earned a badge
      Week One Done
    • Week One Done
      Helen Shafer earned a badge
      Week One Done
    • First Post
      emptyother earned a badge
      First Post
    • Week One Done
      Crunchy6 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      660
    2. 2
      ATLien_0
      266
    3. 3
      Michael Scrip
      235
    4. 4
      Steven P.
      165
    5. 5
      +FloatingFatMan
      149
  • Tell a friend

    Love Neowin? Tell a friend!