[...] in burst you have no safety, whether the timing problems were corrected or affect the music, [...]

What is in bold is misleading. Timing problems aren't something that can get corrected, nor are they any definitive indication that there were errors. A timing problem just indicates that the drive took longer to return data than expected.

There's really nothing wrong with Burst mode other than its inability to detect errors and attempt to correct them. For those with drives that cache audio data and discs in good condition, burst mode is a very attractive option. If you're worried about errors going undetected, follow Eli's advice in the guide to improve your chances:

QUOTE

When ripping the tracks, I suggest using Shift-F6 (test & copy) to decrease the chance of having a bad rip go undetected. The CRCs should match for the T&C, if they don't there is a problem.

I am using Exact Audio Copy 0.99 Beta 1. I have read the previous threads and can't seem to see or figure out how to disable accurate rip. It starts and tries to connect to the internet when I insert one of my cd's to rip. I checked the options within eac and cannot find the option to disable it. Any help would be appreciated.

I am using Exact Audio Copy 0.99 Beta 1. I have read the previous threads and can't seem to see or figure out how to disable accurate rip. It starts and tries to connect to the internet when I insert one of my cd's to rip. I checked the options within eac and cannot find the option to disable it. Any help would be appreciated.

I am using Exact Audio Copy 0.99 Beta 1. I have read the previous threads and can't seem to see or figure out how to disable accurate rip. It starts and tries to connect to the internet when I insert one of my cd's to rip. I checked the options within eac and cannot find the option to disable it. Any help would be appreciated.

Thank you!

Go to the EAC directory and rename AccurateRip.dll to something else like AccurateRip.dll.disabled.

However, I now strongly suggest using dBpoweramp Reference. Note, EAC is free, dBpoweramp is not, plus to get the real benefits you need the better (ie more expensive package - reference, not powerpack). However, dBpoweramp outperforms EAC in secure ripping, especially on drives with good C2 handling, being both faster and more reliable. In my experience dBamp is also more stable than EAC. dBpoweramp is also being actively developed and updated. Spoon, its developer, is an active member here at HA. dBpoweramp is much easier to set up and configure, but a guide will be after dBpowerAMP adds support for HTOA (hidden first track), at which time it will be a complete backup solution completely suitable for replacing EAC.

Hi,

I have over 1000 CDs to rip so I want to get it right! I am using Vista 64 and Slimserver.

With the latest version of EAC, is dBpoweramp still superior? I don't begrudge the $28, I just want the most accurate FLAC rips for networking.

Must admit I'd be interested to hear to. If dBpowerAMP really is THAT much better it would be nice to know why.

As for being easier I'm not so sure. I'd say it BADLY needs a user guide like this as the support/help screens I've accessed when trying to get it set up are pretty dire. Foobar doesn't seem to like/recognise it's default naming conventions and I've wasted hours this morning trying to bottom it out. If it wasn't for AMG I'd likely bin dBpowerAMP in all honesty. Took me 1/2 an hour to set up EAC and get it working fine. While DBPA may make the codec set up easy getting your head round it's tagging and naming conventions is far from it. At least there are countless good guides on EAC to help through the maze.

Hey guys, I'm just wondering if it's still okay to use Eli's setting posted on the first page?

QUOTE (countryman @ Aug 16 2007, 19:32)

QUOTE (Eli @ Jan 26 2005, 06:19)

However, I now strongly suggest using dBpoweramp Reference. Note, EAC is free, dBpoweramp is not, plus to get the real benefits you need the better (ie more expensive package - reference, not powerpack). However, dBpoweramp outperforms EAC in secure ripping, especially on drives with good C2 handling, being both faster and more reliable. In my experience dBamp is also more stable than EAC. dBpoweramp is also being actively developed and updated. Spoon, its developer, is an active member here at HA. dBpoweramp is much easier to set up and configure, but a guide will be after dBpowerAMP adds support for HTOA (hidden first track), at which time it will be a complete backup solution completely suitable for replacing EAC.

Hi,

I have over 1000 CDs to rip so I want to get it right! I am using Vista 64 and Slimserver.

With the latest version of EAC, is dBpoweramp still superior? I don't begrudge the $28, I just want the most accurate FLAC rips for networking.

Cheers.

I agree with what you're saying too. Can an expert come in here and weigh in on this topic? $28 isn't much if dBpoweramp is indeed better and easier to use than EAC.

I personally think a guide designed to help people with EAC ought not to come out and endorse a different program. For this reason, I don't think it's right for this thread to be a sticky any longer.

As far as the suggested settings go and although I don't think I've mentioned it before, I do take issue with the drive options. It is utterly pointless to tell EAC that your drive caches audio data if EAC's test indicates that it doesn't. Use of C2 pointers with EAC is generally not a good idea, but so long as you perform T&C rips with matching CRCs it should be ok. While it is true that these suggested options are intended to be the most fail-safe, they continue to reinforce the commonly-held myth that a rip is useless if the caching setting isn't checked.

Regarding the recommendations regarding "good C2 handling" and dBpowerAMP, I actually don't think it matters if the handling is "good" or not. dBpowerAMP uses C2 pointers in a very different way than EAC, and because of this, C2 pointers are useful with dBpA no matter how bad they are with EAC.

Purely from the perspective of ripping, if your drive provides C2 pointers or caches audio data, do check out a trial version of dBpowerAMP.

I personally think a guide designed to help people with EAC ought not to come out and endorse a different program. For this reason, I don't think it's right for this thread to be a sticky any longer.

As far as the suggested settings go and although I don't think I've mentioned it before, I do take issue with the drive options. It is utterly pointless to tell EAC that your drive caches audio data if EAC's test indicates that it doesn't. Use of C2 pointers with EAC is generally not a good idea, but so long as you perform T&C rips with matching CRCs it should be ok. While it is true that these suggested options are intended to be the most fail-safe, they continue to reinforce the commonly-held myth that a rip is useless if the caching setting isn't checked.

Regarding the recommendations regarding "good C2 handling" and dBpowerAMP, I actually don't think it matters if the handling is "good" or not. dBpowerAMP uses C2 pointers in a very different way than EAC, and because of this, C2 pointers are useful with dBpA no matter how bad they are with EAC.

Purely from the perspective of ripping, if your drive provides C2 pointers or caches audio data, do check out a trial version of dBpowerAMP.

I'm not sure if I understand you here. Should I have C2 checked or not checked? I realize this is a guide made for all people, but I have the original Plextor Premium drive and EAC is telling me to make use of C2 pointers while this guide is telling me not to.

Without the use of C2 pointers and especially without FUA, your drive will run pretty slow in EAC because it caches audio data. Your other option to speed up things with EAC is to use burst mode.

dBpowerAMP doesn't take the same kind of hit in ripping speed as EAC with caching drives because it doesn't need to flush in order to properly synchronize bursts. With FUA, flushing is no longer necessary in which case EAC and dBpA will deliver similar performance, though dBpA may be able to get accurate data from some damaged tracks that EAC cannot because it has the ability make use of C2 pointers during re-reads.

Without the use of C2 pointers and especially without FUA, your drive will run pretty slow in EAC because it caches audio data. Your other option to speed up things with EAC is to use burst mode.

dBpowerAMP doesn't take the same kind of hit in ripping speed as EAC with caching drives because it doesn't need to flush in order to properly synchronize bursts. With FUA, flushing is no longer necessary in which case EAC and dBpA will deliver similar performance, though dBpA may be able to get accurate data from some damaged tracks that EAC cannot because it has the ability make use of C2 pointers during re-reads.

I'll check out the thread, but are you sure that if I enable C2 pointers with Test and Copy, it won't affect the quality of my rip?

Just for the record, I have the original Plextor Premium drive. It is supposively the best CDRW to have ever came out. I'm not talking about the Plextor Premium's successor, but the original!

I don't have to enable FUA though right? I would think C2 and test and copy is more than adequate?

I'll check out the thread, but are you sure that if I enable C2 pointers with Test and Copy, it won't affect the quality of my rip?

If the CRCs match, I'm every bit as sure that the quality won't be affected as I am if you don't use C2 pointers, or you use burst mode for that matter. This does not mean with 100% certainty that the rips with matching CRCs are accurate, regardless of the configuration.

QUOTE (Sgt_Strider @ Sep 13 2007, 21:18)

Just for the record, I have the original Plextor Premium drive. It is supposively the best CDRW to have ever came out. I'm not talking about the Plextor Premium's successor, but the original!

Numbers Spoon gathered from AR submissions don't support this claim. Anyhow, I don't think you're going to run into many situations where the C2 setting will make a difference in accuracy when it comes to this drive.

QUOTE (Sgt_Strider @ Sep 13 2007, 21:18)

I don't have to enable FUA though right? I would think C2 and test and copy is more than adequate?

You don't have to enable FUA, but you'll find a significant change in speed between FUA + C2 and flushing + C2. Try it for yourself.

I'll check out the thread, but are you sure that if I enable C2 pointers with Test and Copy, it won't affect the quality of my rip?

If the CRCs match, I'm every bit as sure that the quality won't be affected as I am if you don't use C2 pointers, or you use burst mode for that matter. This does not mean with 100% certainty that the rips with matching CRCs are accurate, regardless of the configuration.

QUOTE (Sgt_Strider @ Sep 13 2007, 21:18)

Just for the record, I have the original Plextor Premium drive. It is supposively the best CDRW to have ever came out. I'm not talking about the Plextor Premium's successor, but the original!

Numbers Spoon gathered from AR submissions don't support this claim. Anyhow, I don't think you're going to run into many situations where the C2 setting will make a difference in accuracy when it comes to this drive.

QUOTE (Sgt_Strider @ Sep 13 2007, 21:18)

I don't have to enable FUA though right? I would think C2 and test and copy is more than adequate?

You don't have to enable FUA, but you'll find a significant change in speed between FUA + C2 and flushing + C2. Try it for yourself.

Where are the numbers that you quote Spoon to have reported?

I'm also going to post my EAC log here and maybe you can analyse it to tell me if there are any problems with my settings and if any other further changes are necessary:

You can safely check that your drive is capable of overreading into the lead-in/lead-out and everything else looks just fine.

As I said earlier, if AccurateRip cannot verify your tracks, I recommend you use T&C. I normally will press Shift + F5 to rip, check for the results and then choose the tracks that can't be verified and press F8 when necessary.

You can safely check that your drive is capable of overreading into the lead-in/lead-out and everything else looks just fine.

As I said earlier, if AccurateRip cannot verify your tracks, I recommend you use T&C. I normally will press Shift + F5 to rip, check for the results and then choose the tracks that can't be verified and press F8 when necessary.

No, I'm not using FUA.

Are you 100% sure that my original Plextor Premium drive is capable of overreading into the lead-in/lead-out? I don't want to enable any setting that might compromise the quality of the rip in the name of getting more speed. I do realize that I'm no expert in this area compared to you.

Are you 100% sure that my original Plextor Premium drive is capable of overreading into the lead-in/lead-out? I don't want to enable any setting that might compromise the quality of the rip in the name of getting more speed.

I wouldn't have said anything that I've said so far if I wasn't 100% sure. I'm trying my best to separate facts from fear, but if you prefer not to take my advice, that's fine too.

So, the only thing that will be missing are the 00 indices, so your player won't display negative times before tracks (if the original CD had them). But if you used the default settings of EAC, you wont miss any audio.

...and indices greater than 01, CD-TEXT, catalog and ISRC information as well as a variety of other flags. All of these things (including 00 indices) may or may not exist on the original disc.

In terms of only the audio data and assuming the standard method of handling the audio data that would be marked by a 00 index if gaps were detected, the only thing a CUE sheet may be able to recreate is the data before the beginning of the first track (but only if that data consists entirely of null samples); otherwise this information would be lost.

A question for Greynol I guess. I've had some great help from this thread. So thanks to everyone.

Since reading your posts I have been using Burst T&C and relying on Accuraterip.

Obviously sometimes accuraterip has no CRC.

When this happens I use a second drive (different make) configured for secure mode to check my rip. Basically I run a second test. I am trying to eliminate the consistent errors you have been enlightening people about (though i do not think that I have ever seen one!)

Is this a good strategy? Have you ever seen a different drive in a different mode throw up a consistent error?