Hydrogenaudio Forums > foobar 0.9 vs EAC Secure rip

Full Version: foobar 0.9 vs EAC Secure rip

Hydrogenaudio Forums > CD-R and Audio Hardware > CD Hardware/Software

Synthetic Soul

Sep 23 2005, 14:46

I guess most of you will know that foobar will now rip CDs using offset correction, and also using a test and copy-like security system (Edit: see this post for an explanation).

I've yet to see any comparisons between EAC Secure rips and those performed by foobar, so I'm starting this thread.

The following are stats from my two drives at home - a Plextor PX-W5224A and a Lite-On SOHW-832S.

As yet the tests are for one CD only, but I intend to post further tests, and also test on my drive at work. My previous limited test was performed on the drive at work, and discrepancies occurred, so I'm interested to perform a more thorough test on that drive. It is possible that the earlier beta version of foobar tested may have been an influence.

Edit: FYI I am using 0.9 beta 8. I only discovered beta 9 was out yesterday, but I intend to stick to 8 for these tests at the moment.

foobar filenames are of the format:

foo-<drive speed>-<security>-<drive>.wav

drive speed : limited | unlimited
security : disabled | standard | paranoid
drive : makel of drive

EAC filenames are of the format:

eac-<drive>.wav

EAC rip is in secure mode

MD5s of all files:

3adf5ccf2220532a367ffaf031dd56b3 *eac-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *eac-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-paranoid-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-paranoid-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-plextor.wav

EAC log:

CODE

EAC extraction logfile from 23. September 2005, 18:06 for CD
Unknown Artist / Unknown Title

Used drive  : PLEXTOR CD-R   PX-W5224A   Adapter: 1  ID: 0
Read mode   : Secure with C2, accurate stream, disable cache
Read offset correction : 30
Overread into Lead-In and Lead-Out : Yes

Used output format : Internal WAV Routines
                     44.100 Hz; 16 Bit; Stereo

Other options      : 
    Fill up missing offset samples with silence : Yes
    Delete leading and trailing silent blocks : No
    Installed external ASPI interface


Range status and errors
Selected range
     Filename E:\Testing\foobar\eac-plextor.wav

     Peak level 99.9 %
     Range quality 100.0 %
     CRC D26D6311
     Copy OK

No errors occured

End of status report

------------------------------------------------------------

EAC extraction logfile from 23. September 2005, 21:23 for CD
Unknown Artist / Unknown Title

Used drive  : LITE-ON DVDRW SOHW-832S   Adapter: 1  ID: 1
Read mode   : Secure with C2, accurate stream, disable cache
Read offset correction : 12
Overread into Lead-In and Lead-Out : No

Used output format : Internal WAV Routines
                     44.100 Hz; 16 Bit; Stereo

Other options      : 
    Fill up missing offset samples with silence : Yes
    Delete leading and trailing silent blocks : No
    Installed external ASPI interface


Range status and errors
Selected range
     Filename E:\Testing\foobar\eac-liteon.wav

     Peak level 99.9 %
     Range quality 100.0 %
     CRC D26D6311
     Copy OK

No errors occured

End of status report

As you can see all rips were an exact match. This was a little surprising following the rips I had attempted earlier at work - but obviously very pleasing.

Until I can test again at work here are the bit-compare results from those rips:

CODE

Comparing:
file path: "file://C:\DOS\testing\eac.wav" / index: 0
file path: "file://C:\DOS\testing\standard.wav" / index: 0
differences found: 136 sample(s), starting at 581.7864 second(s), peak: 3.051758e-005 at 581.7864 second(s), 1ch
Finished successfully.

Comparing:
file path: "file://C:\DOS\testing\eac.wav" / index: 0
file path: "file://C:\DOS\testing\paranoid.wav" / index: 0
differences found: 1527037 sample(s), starting at 564.3864 second(s), peak: 1.998016 at 567.5842 second(s), 1ch
Finished successfully.

Comparing:
file path: "file://C:\DOS\testing\paranoid.wav" / index: 0
file path: "file://C:\DOS\testing\standard.wav" / index: 0
differences found: 1526901 sample(s), starting at 564.3864 second(s), peak: 1.998016 at 567.5842 second(s), 1ch

Finished successfully.

NB: Length: 9:41.826 (581.826s)

I think that the drive speed was unlimited with the above rips. I look forward to performing the formal test on the drive, to see the results.

Perhaps I'm being over cautious (paranoid) here - perhaps everyone will just end up posting matching MD5 checksums (if anyone bothers), but I thought it would be good if people could test on various drives using various settings, to prove whether foobar could replace EAC as some users' ripper of choice - or at worst a damn fine alternative (e.g.: CDs that EAC doesn't like for some reason (TRACK1 INDEX 0)).

My next test at home will involve a known troublesome CD.

Shade[ST]

Sep 23 2005, 15:48

QUOTE(Synthetic Soul @ Sep 23 2005, 02:46 PM)

Perhaps I'm being over cautious (paranoid) here - perhaps everyone will just end up posting matching MD5 checksums (if anyone bothers), but I thought it would be good if people could test on various drives using various settings, to prove whether foobar could replace EAC as some users' ripper of choice - or at worst a damn fine alternative (e.g.: CDs that EAC doesn't like for some reason (TRACK1 INDEX 0)).

IMHO it should be the opposite : you could use foobar2000's ripper, instead of EAC burst, for CDs that have difficulty when very scratched. By the way, try one test with a scratched CD, you should see a difference in results.

Synthetic Soul

Sep 23 2005, 16:22

I'm not really sure that's the opposite. I use EAC's secure mode, and EAC currently (it's on the todo list supposedly) doesn't have test and copy for image files. Therefore my preferred choice would be EAC secure, then foobar test and copy, then EAC test and copy (tracks).

Can you elaborate regarding the scratched disc? Are you suggesting the foobar results would be better?

I will try a scratched (or more accurately, badly scratched) CD myself.

Shade[ST]

Sep 23 2005, 16:27

a scratched CD with eac will report supposedly better data than foobar, due to rescanning until CRC match. However, if a CD is irrecupable, you're better off skipping the error blocks, and filling them with silence instead. -- something both foobar and eac can do, in burst mode. (or secure for that matter, but it's slower)

AtaqueEG

Sep 24 2005, 11:22

QUOTE(Synthetic Soul @ Sep 23 2005, 02:46 PM)

I guess most of you will know that foobar will now rip CDs using offset correction, and also using a test and copy-like security system (maybe later I can find the link where Peter briefly describes the logic behind foobar's rip).

Where is foobar2000's ripper? I can't seem to find it. I'm guessing that you are using the latest beta from the official site?

picmixer

Sep 24 2005, 11:32

Yep 0.9 beta. There are new drive and security settings in the "play audio cd" dialogue.

Then simply use the converter to rip the cd.

evereux

Sep 24 2005, 12:31

To rip with 0.9 beta.

For the settings: Go to Components > Play Audio CD > Select your drive > Drive Settings > and you can then choose your security level.

To rip the CD: Highlight all your tracks > Right Click > Convert > Convert to > Choose Format > Choose Location.

Are there any plans to generate a log file, or am I missing something? CRC values for the files within the log file would be very nice.

Fandango

Sep 24 2005, 12:35

This test is certainly necessery, but I see no reason why I should dump EAC, not even foobar's stricter cue sheet handling made me do that.

Synthetic Soul

Sep 24 2005, 13:34

QUOTE(evereux @ Sep 24 2005, 07:31 PM)

Are there any plans to generate a log file, or am I missing something? CRC values for the files within the log file would be very nice.

Not that I'm aware of - but I agree it would be good.

I ripped all WAVE files to one directory and then create the MD5 digest using my batch file (which uses FSUM).

Synthetic Soul

Sep 25 2005, 12:05

I'm not having much luck finding a difficult disc to test. I think I may have to make one. My idea at the moment is to copy the previous test disc and scratch it - that should give me some additional maxims.

It seems to me the best (only useful?) test disc will be one that has recoverable errors (i.e.: errors that don't result in sync errors) - to test the error recovery of both.

I have started tests with REM's "Green" and The Cult's "Love" - both of which I re-ripped when I got my Plextor as I knew I'd had problems when originally ripped with my Toshiba.

Unfortunately both discs have a minor TRACK 1 INDEX 0 track ("pregap") - curiously both TRACK 1 INDEX 1 values are 00:00:33. I guess this was enough to trouble my Toshiba, but not the LiteOn or Plextor. More importantly it makes them unsuitable for an EAC vs foobar comparison as foobar currently only recognises INDEX 1 values (so the WAVEs will always be unequal even on a perfect rip).

Here's the results anyway, in the continued absense of anything particularly useful:

REM - Green:

3d4345ed37f11170ad72353b0d66b923 *eac-liteon.wav
3d4345ed37f11170ad72353b0d66b923 *eac-plextor.wav
6218b023353db17aad6a73737ea93fb4 *eac-toshiba.wav
9ec150ccd51d2e3c8020e18e6d8056c1 *foo-limited-disabled-liteon.wav
9ec150ccd51d2e3c8020e18e6d8056c1 *foo-limited-paranoid-liteon.wav
9ec150ccd51d2e3c8020e18e6d8056c1 *foo-limited-standard-liteon.wav
9ec150ccd51d2e3c8020e18e6d8056c1 *foo-unlimited-disabled-liteon.wav
9ec150ccd51d2e3c8020e18e6d8056c1 *foo-unlimited-standard-liteon.wav

The Cult - Love:

29cc3412d6227a34031efdaece249691 *eac-liteon.wav
d63b0109535f3fa019d71af9eb621acb *foo-limited-paranoid-liteon.wav
d63b0109535f3fa019d71af9eb621acb *foo-unlimited-disabled-liteon.wav

I'll test the first disc at work tomorrow on the crappy Samsung there, and create an errored version to test as soon as I have time.

Please feel free to post your own tests.

Peter

Sep 25 2005, 12:13

"Standard" mode already requires two identical CRCs on each block to pass (it will keep rereading and error out if it can't get consistent results after 128 reads; also see console output). "Paranoid" mode is pretty much the same, except it wants four identical CRCs instead; it's absolute overkill and should not be used on anything else than really badly damaged discs such as recent wave of EMI releases (I managed to get an audible glitch with two identical CRCs on Goldfrapp - Supernature on LG GSA-4163; EAC secure mode would entirely refuse to rip it on two different setups).

AtaqueEG

Sep 25 2005, 12:20

QUOTE(zZzZzZz @ Sep 25 2005, 12:13 PM)

Is there plans to have it output a log?

Peter

Sep 25 2005, 12:28

QUOTE(AtaqueEG @ Sep 25 2005, 08:20 PM)

Is there plans to have it output a log?

Possibly, but there are complications with doing that from architectural point of view. Unless writing info to console (interrupted by playback messages etc) as well as creating separate log for each ripped track is sufficient for you.

Synthetic Soul

Sep 26 2005, 03:01

Argh! My test CD keeps going from perfectly readable to totally unreadable!

Anyone know of a good way to create (recoverable) read errors on a CD without killing it?

I'm scratching with a bent paper clip at the moment and it goes perfect, still perfect, still perfect, unrecognisable.

As an alternative I will try some restoration on the ones I've totally killed thus far. I'll buy some Brasso this evening at Sainsburys... I have a Cure CD that has sync errors so I've been waiting to have a pop at that one as well. Edit: I just got some at ChavSave at lunchtime but then realised that it won't work on a CD-R! Ah well, hopefully it will retore my Cure CD. Any ideas how to restore a scratched CD-R?

Ho hum.

I'm perhaps not the best choice to be starting a testing thread.

Edit: I think my main problem must be corrupting the TOC, so maybe I'll concentrate more on the outer edge of the data...

Synthetic Soul

Sep 26 2005, 03:21

QUOTE(Synthetic Soul @ Sep 23 2005, 09:46 PM)

My previous limited test was performed on the drive at work, and discrepancies occurred, so I'm interested to perform a more thorough test on that drive. It is possible that the earlier beta version of foobar tested may have been an influence.
<snip>
I look forward to performing the formal test on the drive, to see the results.

The first test did raise some discrepancies, so I decided to run each setup 5 times. Here are the results:

3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung-5.wav
3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung.wav

7cfc5a09786604963b428a8f4166fb37 *foo-limited-disabled-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-samsung-5.wav
a7f5a352c22ac4a44f23086fcb29d87e *foo-limited-disabled-samsung.wav

3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung-5.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung.wav

3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung-5.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung.wav

3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung-5.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung.wav

d82232a4bdda3be4db706a5ce19a7d16 *foo-unlimited-paranoid-samsung-2.wav
5abd069a6cfe48392d89abfb8e7de35d *foo-unlimited-paranoid-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-paranoid-samsung-4.wav
c03b49c3be51f6c55cfbb5121590cbb6 *foo-unlimited-paranoid-samsung-5.wav
c03b49c3be51f6c55cfbb5121590cbb6 *foo-unlimited-paranoid-samsung.wav

3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-samsung-5.wav
4764efd0904d1fb3c2fc6b39e682e9bb *foo-unlimited-standard-samsung.wav

I'm not sure that this is proving anything other than the drive is unreliable.

It's tending toward the fact that limited standard/paranoid is safer, but also unlimited disabled.

Mo0zOoH

Sep 26 2005, 03:33

QUOTE(zZzZzZz @ Sep 25 2005, 09:28 PM)

Unless writing info to console (interrupted by playback messages etc) as well as creating separate log for each ripped track is sufficient for you.

Maybe it is an option to pass that data to a simple parser in order to refine the extraction-relevant information?

evereux

Sep 26 2005, 05:35

I ran some tests myself. The disc I used I have previously managed to get consistent extractions (after error recovery) with Plextools in the past and I've not touched the disc since. I'm wondering whether or not the fact that I ripped the disc with other apps first had an effect on the disc by heating it up.
I'll pop it in the fridge and try again later.

Foobar2000, Plextools and EAC comparison.

evereux

Sep 26 2005, 05:37

QUOTE(zZzZzZz @ Sep 25 2005, 06:13 PM)

I managed to get an audible glitch with two identical CRCs on Goldfrapp - Supernature on LG GSA-4163; EAC secure mode would entirely refuse to rip it on two different setups.

Were they two seperate rips or do you mean Foobar2000 managed to find two identical CRCs during the ripping process?

Peter

Sep 26 2005, 05:44

QUOTE(evereux @ Sep 26 2005, 01:37 PM)

Were they two seperate rips or do you mean Foobar2000 managed to find two identical CRCs during the ripping process?

Two identical CRCs during single ripping pass. I *did* get a lot of CRC mismatches (rereads) during the process, so it can't be a drive cache issue - unless the drive has done something really weird.

evereux

Sep 26 2005, 05:47

QUOTE(zZzZzZz @ Sep 26 2005, 11:44 AM)

QUOTE(evereux @ Sep 26 2005, 01:37 PM)

Were they two seperate rips or do you mean Foobar2000 managed to find two identical CRCs during the ripping process?

Two identical CRCs during single ripping pass. I *did* get a lot of CRC mismatches (rereads) during the process, so it can't be a drive cache issue - unless the drive has done something really weird.

If I understand what Foobar200 is reporting correctly, the same happened to me above. Something weird is happening, for sure.

edit: for the record a PX-708A (I'll edit my page shortly, I forgot to add that).

Peter

Sep 26 2005, 06:13

Well, I guess there are always very low but non-zero chances of getting same glitched output on bad CD twice. We need C2 support, and I don't have docs or free time for it at the moment.

spoon

Sep 26 2005, 06:21

>very low but non-zero chances of getting same glitched output on bad CD twice

That is just it, no one has scientific data to prove it one way or the other, it could be 1:25 of bad rips (where an error got through because of an repeated bad datablock), 1:6, or 1:1000, thing is no-one knows.

evereux

Sep 26 2005, 06:27

Perhaps a simple test and copy function is enough? C2 doesn't always seem to be reliable either.

edit: I've just ripped the troublesome track 8 on my CD 8 times. Each time Foobar2000 reported that the error recovery was successful, but every file had a different CRC. I'd say some form of test and copy is essential, with EAC aswell as Foobar.

Synthetic Soul

Sep 26 2005, 09:33

QUOTE(evereux @ Sep 26 2005, 12:35 PM)

Foobar2000, Plextools and EAC comparison.

I totally missed this post.

Thanks for the info.

I'm beginning to wonder what conclusions can be made - except that each app has it's own way of ensuring security, and none are infallible.

Edit: That said, I'm not expecting results to be the same on badly scratched tracks. When multiple reads are done I guess it's down to each app to decide how to handle the data it has managed to retrieve from the block in those reads.

Currently I am interested in testing CDs that cause EAC's secure mode error recovery and foobar's standard/paranoid check to kick in, but don't result in read or sync errors (i.e.: recoverable errors). If foobar and EAC can both agree on the data from recoverable errors then I think that's a real boon for foobar.

Peter

Sep 26 2005, 09:39

QUOTE(evereux @ Sep 26 2005, 02:27 PM)

Secure mode was meant to be equivalent of T&C (T&C on per-4MB-block basis, to allow streamed read without caching interfering with rereads), with additional rereads in case of bad CRC until at least two identical results from each sector are read. If you get no read error reports in console, the rip should be as safe as burst mode T&C with no mismatches - assuming the 4MB block read trick works as expected (some drives have more cache than that and actually use it for audio?).
Perhaps something to more aggressively avoid cache is necessary (larger block read size?).

ToS_Maverick

Sep 26 2005, 09:47

i made a test with my 2 "special" Blind Guardian CDs...

the discs are from the album "Live", which was released in 2003 with a nasty copy-protection. EAC can read CD1 in secure mode, though it's very slow. CD2 is unreadable in secure mode. It would take 2 hours for EAC to extract it, so i gave up.

now, that foobar supports secure extration, i wanted to give it a try, to finally backup the second disk to wavpack. I used Secure and Unlimited.

My drive is a LG GSA-4120B, offset +667.

here are my results, i calulated them with MD5summer (http://www.md5summer.org):

eab296397f944d2cc91dec3ab7323fa2 *Blind Guardian - Live CD1 - LG foobar.wav
eab296397f944d2cc91dec3ab7323fa2 *Blind Guardian - Live CD1 - LG Secure.wav
eab296397f944d2cc91dec3ab7323fa2 *Blind Guardian - Live CD1 - LG Secure 2.wav
fa807756b4203781671cf5a45447eba5 *Blind Guardian - Live CD1 - LG Sync.wav
b82ce676220e83a2cb564d213fc86abc *Blind Guardian - Live CD2 - LG Burst.wav
9b6c63e8dd7b5695b7c674157dd0dd01 *Blind Guardian - Live CD2 - LG foobar.wav
bf143d3e63f692511b5bb1864d5545e3 *Blind Guardian - Live CD2 - LG Sync 1.wav
9b6c63e8dd7b5695b7c674157dd0dd01 *Blind Guardian - Live CD2 - LG Sync 2.wav
a8645b89003d2df122ad9f3b6c47c74f *Blind Guardian - Live CD2 - LG Sync 3.wav
39ec0f7973f81c32a66a6234766120f2 *Blind Guardian - Live CD2 - LG Sync 4.wav

foobar seems to extract correctly, as the MD5 is the same with secure mode on CD1.

on CD2, it seems as if i got a lucky try with sync 2 (EAC in synchronization mode).

an interesting deatail might be, that wavpack outputs following MD5s for the foobar extractions:

CD1: b97916c7c62c7abd052dd56fc1e4e591
CD2: d3af9b64a02916bbf0c049eac577f346

i don't know why wavpack displays the "wrong" MD5, after compressing and decoding, the files are the same.

Synthetic Soul

Sep 26 2005, 10:03

QUOTE(ToS_Maverick @ Sep 26 2005, 04:47 PM)

an interesting deatail might be, that wavpack outputs following MD5s for the foobar extractions:

CD1: b97916c7c62c7abd052dd56fc1e4e591
CD2: d3af9b64a02916bbf0c049eac577f346

i don't know why wavpack displays the "wrong" MD5, after compressing and decoding, the files are the same.

Thanks for your input.

WavPack stores the MD5 of the raw audio data (i.e.: excluding the file header). Nothing to worry about.

Shade[ST]

Sep 26 2005, 12:06

One of my drives has 8MB of cache.. What can we do in that case? Is there any way to tell foobar my cache size?

rehgf

Sep 26 2005, 12:26

QUOTE(zZzZzZz @ Sep 25 2005, 08:28 PM)

QUOTE(AtaqueEG @ Sep 25 2005, 08:20 PM)

Is there plans to have it output a log?

Separate log info for each track would actually make lots of sense, particularly when some tracks are re-ripped because of glitches. That is a good idea of yours.

Could the files be tagged with the log data, like "LOG=Ripped using foobar2000 0.9b\ Paranoid Secure... etc" metadata fields in APEv2 tags? This would have a side effect of eliminating .log files and make sure every ripped file always contains its own correct log.

For those of us who are used to log files, a playlist menu option for exportation of metadata to a log file could then be added, or simply scripted using foobar's customizable "copy" command. This would leave foobar's architecture intact and provide the desired functionality.

Synthetic Soul

Sep 27 2005, 15:29

I found a track (All Along the Watchtower, no less) that has recoverable errors.

EAC is content after one bar in secure mode.

dfbd610f46c29bb2daa604f342766db8 *eac-liteon-2.wav
a14e182b014cd9f25424b4ba29d61495 *eac-liteon-3.wav
f97ae89101d7d814b61905a811658de3 *eac-liteon.wav

f97ae89101d7d814b61905a811658de3 *foo-limited-disabled-liteon-2.wav
09ffa16631e9865d94e90d6dbf94796a *foo-limited-disabled-liteon-3.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-disabled-liteon.wav

f97ae89101d7d814b61905a811658de3 *foo-limited-paranoid-liteon-2.wav
09ffa16631e9865d94e90d6dbf94796a *foo-limited-paranoid-liteon-3.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-paranoid-liteon.wav

f97ae89101d7d814b61905a811658de3 *foo-limited-standard-liteon-2.wav
09ffa16631e9865d94e90d6dbf94796a *foo-limited-standard-liteon-3.wav
09ffa16631e9865d94e90d6dbf94796a *foo-limited-standard-liteon.wav

220ff51f631fd1d617c2ded9a86e9c46 *foo-unlimited-disabled-liteon-2.wav
220ff51f631fd1d617c2ded9a86e9c46 *foo-unlimited-disabled-liteon-3.wav
ed096329e5f3b7869dc74a6e67c68812 *foo-unlimited-disabled-liteon.wav

dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-paranoid-liteon-2.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-paranoid-liteon-3.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-paranoid-liteon.wav

4762f160e5f92d6bda5e6bd8c285a85e *foo-unlimited-standard-liteon-2.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-standard-liteon-3.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-standard-liteon.wav

foobar console output

CODE

foo-limited-paranoid-liteon
===========================
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1783/1784
secure mode: rereading successful
=
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1781/1784
reread #2, matches so far: 1783/1784
reread #3, matches so far: 1783/1784
secure mode: rereading successful
=
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1781/1784
reread #2, matches so far: 1782/1784
reread #3, matches so far: 1783/1784
secure mode: rereading successful


foo-unlimited-paranoid-liteon
=============================
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1780/1784
reread #2, matches so far: 1782/1784
secure mode: rereading successful
=
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1778/1784
secure mode: rereading successful
=
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1778/1784
secure mode: rereading successful


foo-limited-standard-liteon
===========================
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1783/1784
secure mode: rereading successful
=
(no mismatches reported)
=
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1782/1784
secure mode: rereading successful


foo-unlimited-standard-liteon
=============================
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1782/1784
secure mode: rereading successful
=
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1783/1784
secure mode: rereading successful
=
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1780/1784
secure mode: rereading successful

Tomorrow I'll try it in my Plextor, to see if I can find what the MD5 should be, or at least what my Plextor thinks it should be. I may re-test with a cooler drive also.

Edit, or "tomorrow is now here": OK, here are a few results from the Plextor (I think I'll get some more), and also a 4th run on the LiteOn, on a cooler drive:

4c2c1f7b330fb3979587c5c3be1b335a *eac-plextor.wav
4c2c1f7b330fb3979587c5c3be1b335a *eac-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-paranoid-plextor.wav
9e2f928f6f02986adfaa1918e754bf7e *foo-unlimited-disabled-plextor.wav

dfbd610f46c29bb2daa604f342766db8 *eac-liteon-4.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-disabled-liteon-4.wav
57d920846b666e3619c159ea6475128c *foo-limited-paranoid-liteon-4.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-standard-liteon-4.wav
220ff51f631fd1d617c2ded9a86e9c46 *foo-unlimited-disabled-liteon-4.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-paranoid-liteon-4.wav
e8ace34a8ff6ae4f25479f816e371dc4 *foo-unlimited-standard-liteon-4.wav

It's looking like Plextor thinks the correct MD5 is 4c2c1f7b330fb3979587c5c3be1b335a, which was not achieved once on the LiteOn...

I'm tempted to say the winner on the LiteOn is dfbd610f46c29bb2daa604f342766db8. This has been achieved in all four runs in foobar with unlimited paranoid, and EAC twice out of four. I actually did a "test" in EAC right at the beginning of the test. The test CRC matched that of eac-liteon.wav, the first test on EAC - so I could say that this was achieved 3/5 times in EAC.

All in all not very conclusive though.

I thought, if EAC reported the copy to be OK, that you had a secure rip. This is obviously not the case, and only goes to prove why Test & Copy is used.

I've had enough of inconclusive results. After I've done some more Plextor runs to try to get some sort of conclusion I think I'll quit the business.

Edit: Oh, also some listening tests on the questionable part.

Edit, or "now it's the next day": OK, here are the results for All Along the Watchtower on my Plextor:

4c2c1f7b330fb3979587c5c3be1b335a *eac-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *eac-plextor.wav

4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-disabled-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-disabled-plextor.wav

4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-paranoid-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-paranoid-plextor.wav

4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-standard-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-standard-plextor.wav

4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-disabled-plextor-2.wav
9e2f928f6f02986adfaa1918e754bf7e *foo-unlimited-disabled-plextor.wav

4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-paranoid-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-paranoid-plextor.wav

4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-standard-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-standard-plextor.wav

Listening Test

Unsuccessful. According to bit-compare with the WAVEs tested there is between 57 and 128 different samples in the files. I've examined a couple in Audacity and cannot see any glitch, let alone hear it. Examination of two files in a HEX editor showed only 7 (non-successive) bytes differing.

Synthetic Soul

Sep 29 2005, 03:30

Conclusions

Considering the limited testing and dubious results these conclusions should be taken with a pinch of salt (except 1). However, I feel, after the work I have put in, some conclusions are necessary - even if it is to spark discussion.

Don't lend your CDs to your brother while travelling Europe. I can only assume he's to blame for my scratched Cure and Jimi CDs.
No ripper is infallible. Even EAC returns differing results depending on the drive. File this one under "nothing in life is perfect".
foobar's ripper in standard and paranoid mode is on par with EAC's error correction. In fact, with the Jimi test on my LiteOn, the results from foobar with unlimited-secure and unlimited-paranoid attained a better success rate than EAC (3:4 over 3:5) - unlimited-paranoid achieved 1:1 (4/4). As both applications have got things right, and got things wrong, I find it difficult to state which one is the better. However foobar's inclusion of offset correction and a Test & Copy system is a definite improvement over 0.8.3, and should be commended.
Limiting the drive speed is not necessarily better. If my dodgy conclusion for the "correct" MD5 for the LiteOn is correct, the best results were achieved, on that drive, with unlimited-standard and unlimited-paranoid. Also, with the pristine CD on the dodgy Samsung drive, unlimited-disabled was more consistent than limited-disabled. It looks like there may be something to be said for testing whether your drive prefers it or not.
The Samsung SD-616E drive at work is unreliable. My Plextor PX-W5224A is better at reading discs in any situation than the LiteOn or Samsung.
I'm not cut out for formal tests. I don't have the patience.

Edit: I expect to continue to use EAC to rip my CDs, mainly as I'm comfortable with it. However, if I could not use EAC for some reason, I would be quite happy to use foobar's limited-standard or limited-paranoid mode with my Plextor - being paranoid I would probably use limited-paranoid. Actually, this may depend on the quality of the CD. Limited-standard would be fine for a newer CD.

I guess a speed test may also be worth doing, for those people who seem obsessed by doing everything as fast as possible. I find it difficult to say whether limited-standard or limited-paranoid would be faster or slower than EAC. I seem to remember even limited ripping on the Plextor being very quick.

Collated Results (Clearer Format)

=========================================================================
Test CD (tracks 4 to 6 from Bloc Party - Silent Alarm) [no errors on CD]
=========================================================================

LITEON
3adf5ccf2220532a367ffaf031dd56b3 *eac-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-paranoid-liteon.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-liteon.wav

PLEXTOR
3adf5ccf2220532a367ffaf031dd56b3 *eac-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-paranoid-plextor.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-plextor.wav

SAMSUNG
3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung-5.wav
3adf5ccf2220532a367ffaf031dd56b3 *eac-samsung.wav
7cfc5a09786604963b428a8f4166fb37 *foo-limited-disabled-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-disabled-samsung-5.wav
a7f5a352c22ac4a44f23086fcb29d87e *foo-limited-disabled-samsung.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung-5.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-paranoid-samsung.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung-5.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-limited-standard-samsung.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung-5.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-disabled-samsung.wav
d82232a4bdda3be4db706a5ce19a7d16 *foo-unlimited-paranoid-samsung-2.wav
5abd069a6cfe48392d89abfb8e7de35d *foo-unlimited-paranoid-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-paranoid-samsung-4.wav
c03b49c3be51f6c55cfbb5121590cbb6 *foo-unlimited-paranoid-samsung-5.wav
c03b49c3be51f6c55cfbb5121590cbb6 *foo-unlimited-paranoid-samsung.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-samsung-2.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-samsung-3.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-samsung-4.wav
3adf5ccf2220532a367ffaf031dd56b3 *foo-unlimited-standard-samsung-5.wav
4764efd0904d1fb3c2fc6b39e682e9bb *foo-unlimited-standard-samsung.wav

NOTE1: On the Samsung drive, EAC and foobar limited-paranoid/limited-standard/unlimited-disabled all produced conclusive results.

===========================================================================
Jimi Hendrix - All Along The Watchtower [recoverable errors (x2) on track]
===========================================================================

LITEON
dfbd610f46c29bb2daa604f342766db8 *eac-liteon-2.wav
a14e182b014cd9f25424b4ba29d61495 *eac-liteon-3.wav
dfbd610f46c29bb2daa604f342766db8 *eac-liteon-4.wav
f97ae89101d7d814b61905a811658de3 *eac-liteon.wav
dfbd610f46c29bb2daa604f342766db8 [undocumented "Test" (F8)]
f97ae89101d7d814b61905a811658de3 *foo-limited-disabled-liteon-2.wav
09ffa16631e9865d94e90d6dbf94796a *foo-limited-disabled-liteon-3.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-disabled-liteon-4.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-disabled-liteon.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-paranoid-liteon-2.wav
09ffa16631e9865d94e90d6dbf94796a *foo-limited-paranoid-liteon-3.wav
57d920846b666e3619c159ea6475128c *foo-limited-paranoid-liteon-4.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-paranoid-liteon.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-standard-liteon-2.wav
09ffa16631e9865d94e90d6dbf94796a *foo-limited-standard-liteon-3.wav
f97ae89101d7d814b61905a811658de3 *foo-limited-standard-liteon-4.wav
09ffa16631e9865d94e90d6dbf94796a *foo-limited-standard-liteon.wav
220ff51f631fd1d617c2ded9a86e9c46 *foo-unlimited-disabled-liteon-2.wav
220ff51f631fd1d617c2ded9a86e9c46 *foo-unlimited-disabled-liteon-3.wav
220ff51f631fd1d617c2ded9a86e9c46 *foo-unlimited-disabled-liteon-4.wav
ed096329e5f3b7869dc74a6e67c68812 *foo-unlimited-disabled-liteon.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-paranoid-liteon-2.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-paranoid-liteon-3.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-paranoid-liteon-4.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-paranoid-liteon.wav
4762f160e5f92d6bda5e6bd8c285a85e *foo-unlimited-standard-liteon-2.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-standard-liteon-3.wav
e8ace34a8ff6ae4f25479f816e371dc4 *foo-unlimited-standard-liteon-4.wav
dfbd610f46c29bb2daa604f342766db8 *foo-unlimited-standard-liteon.wav

NOTE1: I deem dfbd610f46c29bb2daa604f342766db8 to be the "correct" result for the LiteOn. Not only was it produced the most times, but also with the most trustworthy modes, these being EAC and foobar unlimited-paranoid/unlimited-standard.
NOTE2: f97ae89101d7d814b61905a811658de3 is a curious partner, and may actually be the "correct" result - which would really confuse matters.

PLEXTOR
4c2c1f7b330fb3979587c5c3be1b335a *eac-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *eac-plextor.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-disabled-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-disabled-plextor.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-paranoid-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-paranoid-plextor.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-standard-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-limited-standard-plextor.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-disabled-plextor-2.wav
9e2f928f6f02986adfaa1918e754bf7e *foo-unlimited-disabled-plextor.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-paranoid-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-paranoid-plextor.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-standard-plextor-2.wav
4c2c1f7b330fb3979587c5c3be1b335a *foo-unlimited-standard-plextor.wav

NOTE1: The Plextor reports no errors on the CD.
NOTE2: The mismatched MD5 can only be put down to a glitch. I would always use at least standard security anyway. The fact that the Plextor MD5 and the winning LiteOn MD5 do not match, and that the LiteOn never achieved an MD5 matching the Plextor in all 29 tests, only proves that you can't always trust what your drive says.

AtaqueEG

Sep 29 2005, 20:26

This is excellent!

Congratulations to Peter for his wonderful (and correctly implemented idea) new development for foobar2000

And thanks to you, Synthetic Soul, for your time and patience.

It is good to have an alternative on ripping

krazy

Sep 29 2005, 22:33

I conducted a test of foobar 0.9b9's new ripping capability with respect to error detection & correction. The CD used was one which I have had considerable problems with in the past. It is badly scratched and in the past several attempts using EAC's secure mode has been required to successfully rip the CD.
Drive has (from EAC): Accurate Stream, No Cache, No C2.
I ripped in foobar using unlimited drive speed in each of the three modes: disabled, secure, and paranoid. I ripped in EAC using Secure mode verified by AccurateRip. The results shown are only those tracks which did not produce identical md5 hashes in all rips (thanks for the script Synthetic Soul

):

Track 7:
foo-unlimited-disabled: 538df4df83a6fa3a19d82a2329d8fb81
foo-unlimited-secure: 96cb4895b72779d580a5c93f75666c70
foo-unlimited-paranoid: 96cb4895b72779d580a5c93f75666c70
eac-secure-accurate: 96cb4895b72779d580a5c93f75666c70

Track 12:
foo-unlimited-disabled: 2bf60c83f669024b27074e2911fc044e
foo-unlimited-secure: 085538635b06ea6cd035104c5f6f4798
foo-unlimited-paranoid: 7e218d767c5c8810006d54d27ebbafd9
eac-secure-accurate: 7e218d767c5c8810006d54d27ebbafd9

Track 13:
foo-unlimited-disabled: 40107f4c4133c513d69d59946b51250e
foo-unlimited-secure: 240bc6ceaf14ea96f5d06d8795f03a13
foo-unlimited-paranoid: 240bc6ceaf14ea96f5d06d8795f03a13
eac-secure-accurate: 240bc6ceaf14ea96f5d06d8795f03a13

As you can see, fb2k's secure mode failed to detect an error on track 12. However paranoid mode agreed with EAC and so in this limited test and for this drive I'm satisfied that paranoid is as accurate as EAC. It should be noted that secure ripped almost twice as fast a paranoid mode.

Logs:
foo-unlimited-disabled:

CODE

cd access error, attempting to reread
reread successful
cd access error, attempting to reread
reread successful
Total encoding time: 3:40.625, 20.09x realtime

foo-unlimited-secure:

CODE

secure mode: CRC mismatch, retrying
reread #1, matches so far: 1773/1784
reread #2, matches so far: 1780/1784
reread #3, matches so far: 1780/1784
reread #4, matches so far: 1780/1784
reread #5, matches so far: 1780/1784
reread #6, matches so far: 1780/1784
reread #7, matches so far: 1780/1784
reread #8, matches so far: 1780/1784
reread #9, matches so far: 1782/1784
reread #10, matches so far: 1782/1784
reread #11, matches so far: 1782/1784
reread #12, matches so far: 1782/1784
secure mode: rereading successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1783/1784
secure mode: rereading successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1783/1784
secure mode: rereading successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1722/1784
reread #2, matches so far: 1744/1784
reread #3, matches so far: 1756/1784
reread #4, matches so far: 1761/1784
reread #5, matches so far: 1762/1784
reread #6, matches so far: 1770/1784
reread #7, matches so far: 1774/1784
reread #8, matches so far: 1774/1784
reread #9, matches so far: 1774/1784
reread #10, matches so far: 1775/1784
reread #11, matches so far: 1775/1784
reread #12, matches so far: 1775/1784
reread #13, matches so far: 1775/1784
reread #14, matches so far: 1777/1784
reread #15, matches so far: 1778/1784
reread #16, matches so far: 1780/1784
reread #17, matches so far: 1782/1784
reread #18, matches so far: 1782/1784
reread #19, matches so far: 1782/1784
reread #20, matches so far: 1782/1784
reread #21, matches so far: 1782/1784
reread #22, matches so far: 1782/1784
reread #23, matches so far: 1782/1784
reread #24, matches so far: 1782/1784
reread #25, matches so far: 1782/1784
reread #26, matches so far: 1783/1784
reread #27, matches so far: 1783/1784
reread #28, matches so far: 1783/1784
reread #29, matches so far: 1783/1784
reread #30, matches so far: 1783/1784
reread #31, matches so far: 1783/1784
reread #32, matches so far: 1783/1784
reread #33, matches so far: 1783/1784
reread #34, matches so far: 1783/1784
reread #35, matches so far: 1783/1784
reread #36, matches so far: 1783/1784
reread #37, matches so far: 1783/1784
reread #38, matches so far: 1783/1784
reread #39, matches so far: 1783/1784
reread #40, matches so far: 1783/1784
reread #41, matches so far: 1783/1784
reread #42, matches so far: 1783/1784
reread #43, matches so far: 1783/1784
reread #44, matches so far: 1783/1784
reread #45, matches so far: 1783/1784
reread #46, matches so far: 1783/1784
reread #47, matches so far: 1783/1784
reread #48, matches so far: 1783/1784
reread #49, matches so far: 1783/1784
secure mode: rereading successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1783/1784
secure mode: rereading successful
cd access error, attempting to reread
reread successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1777/1784
secure mode: rereading successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 696/698
secure mode: rereading successful
Total encoding time: 9:25.078, 7.84x realtime

foo-unlimited-paranoid:

CODE

secure mode: CRC mismatch, retrying
reread #1, matches so far: 1770/1784
reread #2, matches so far: 1773/1784
reread #3, matches so far: 1774/1784
reread #4, matches so far: 1778/1784
reread #5, matches so far: 1779/1784
reread #6, matches so far: 1779/1784
reread #7, matches so far: 1779/1784
reread #8, matches so far: 1779/1784
reread #9, matches so far: 1781/1784
reread #10, matches so far: 1781/1784
reread #11, matches so far: 1781/1784
reread #12, matches so far: 1781/1784
reread #13, matches so far: 1781/1784
reread #14, matches so far: 1781/1784
reread #15, matches so far: 1781/1784
reread #16, matches so far: 1781/1784
reread #17, matches so far: 1781/1784
reread #18, matches so far: 1781/1784
reread #19, matches so far: 1781/1784
reread #20, matches so far: 1781/1784
reread #21, matches so far: 1781/1784
reread #22, matches so far: 1781/1784
reread #23, matches so far: 1781/1784
reread #24, matches so far: 1781/1784
reread #25, matches so far: 1781/1784
reread #26, matches so far: 1781/1784
reread #27, matches so far: 1781/1784
reread #28, matches so far: 1781/1784
reread #29, matches so far: 1781/1784
reread #30, matches so far: 1782/1784
reread #31, matches so far: 1782/1784
reread #32, matches so far: 1782/1784
reread #33, matches so far: 1782/1784
reread #34, matches so far: 1782/1784
reread #35, matches so far: 1782/1784
reread #36, matches so far: 1782/1784
reread #37, matches so far: 1782/1784
reread #38, matches so far: 1782/1784
reread #39, matches so far: 1782/1784
reread #40, matches so far: 1782/1784
reread #41, matches so far: 1782/1784
reread #42, matches so far: 1782/1784
reread #43, matches so far: 1782/1784
secure mode: rereading successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1777/1784
secure mode: rereading successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1699/1784
reread #2, matches so far: 1720/1784
reread #3, matches so far: 1734/1784
reread #4, matches so far: 1740/1784
reread #5, matches so far: 1749/1784
reread #6, matches so far: 1755/1784
reread #7, matches so far: 1761/1784
reread #8, matches so far: 1764/1784
reread #9, matches so far: 1766/1784
reread #10, matches so far: 1771/1784
cd access error, attempting to reread
reread successful
reread #11, matches so far: 1771/1784
reread #12, matches so far: 1771/1784
reread #13, matches so far: 1772/1784
reread #14, matches so far: 1775/1784
reread #15, matches so far: 1778/1784
reread #16, matches so far: 1778/1784
reread #17, matches so far: 1778/1784
reread #18, matches so far: 1779/1784
reread #19, matches so far: 1779/1784
reread #20, matches so far: 1780/1784
reread #21, matches so far: 1780/1784
reread #22, matches so far: 1780/1784
reread #23, matches so far: 1780/1784
reread #24, matches so far: 1780/1784
reread #25, matches so far: 1780/1784
reread #26, matches so far: 1780/1784
reread #27, matches so far: 1780/1784
reread #28, matches so far: 1780/1784
reread #29, matches so far: 1780/1784
reread #30, matches so far: 1780/1784
reread #31, matches so far: 1780/1784
reread #32, matches so far: 1780/1784
reread #33, matches so far: 1780/1784
reread #34, matches so far: 1780/1784
reread #35, matches so far: 1780/1784
reread #36, matches so far: 1780/1784
reread #37, matches so far: 1780/1784
reread #38, matches so far: 1780/1784
reread #39, matches so far: 1781/1784
reread #40, matches so far: 1781/1784
reread #41, matches so far: 1782/1784
reread #42, matches so far: 1783/1784
secure mode: rereading successful
cd access error, attempting to reread
reread successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1782/1784
secure mode: rereading successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 696/698
secure mode: rereading successful
secure mode: CRC mismatch, retrying
reread #1, matches so far: 1782/1784
secure mode: rereading successful
Total encoding time: 17:39.031, 4.18x realtime

eac-secure-accurate:

CODE

EAC extraction logfile from 30. September 2005, 11:37 for CD
Daft Punk / Homework

Used drive  : CyberDrvCW038D CD-R/RW   Adapter: 1  ID: 0
Read mode   : Secure with NO C2, accurate stream, NO disable cache
Read offset correction : 733
Overread into Lead-In and Lead-Out : No

Used output format : Internal WAV Routines
                     44.100 Hz; 16 Bit; Stereo

Other options      : 
    Fill up missing offset samples with silence : Yes
    Delete leading and trailing silent blocks : No
    Installed external ASPI interface


Track  1
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 01 - Daftendirekt.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC 775C6528
     Copy OK

Track  2
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 02 - Wdpk 83.7 fm.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC BE1AA997
     Copy OK

Track  3
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 03 - Revolution 909.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC 14042BB1
     Copy OK

Track  4
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 04 - Da Funk.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC F2590C56
     Copy OK

Track  5
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 05 - Phoenix.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC 14934653
     Copy OK

Track  6
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 06 - Fresh.wav

     Peak level 100.0 %
     Track quality 99.9 %
     Copy CRC 8C6B27CD
     Copy OK

Track  7
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 07 - Around The World.wav

     Peak level 100.0 %
     Track quality 99.9 %
     Copy CRC 672C01FE
     Copy OK

Track  8
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 08 - Rollin' & Scratchin'.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC AEDB2CE0
     Copy OK

Track  9
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 09 - Teachers.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC D39D786E
     Copy OK

Track 10
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 10 - High Fidelity.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC 7F771BFD
     Copy OK

Track 11
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 11 - Rock'n Roll.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC C3E0945E
     Copy OK

Track 12
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 12 - Oh Yeah.wav

     Peak level 100.0 %
     Track quality 99.5 %
     Copy CRC 56083591
     Copy OK

Track 13
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 13 - Burnin'.wav

     Peak level 100.0 %
     Track quality 99.9 %
     Copy CRC 4B4BBD5B
     Copy OK

Track 14
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 14 - Ino Silver Club.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC 9168E0A1
     Copy OK

Track 15
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 15 - Alive.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC 9F6CE455
     Copy OK

Track 16
     Filename D:\New Music\Daft Punk\(1996) Homework\Daft Punk - 16 - Funk Ad.wav

     Peak level 100.0 %
     Track quality 100.0 %
     Copy CRC BB623FBD
     Copy OK

No errors occured


End of status report

Also, my drive had considerable trouble with the "limit drive speed" option when error correction was disabled in foobar. It would get part way into the first track before slowing down to about .3x realtime. I cancelled and didn't try with secure or paranoid modes.

Synthetic Soul

Sep 30 2005, 04:50

Thanks for the support and additional data. The more data the better.

The only other point I would raise in krazy's test is that EAC also had the most problem with track 12 - the track which unlimited-standard failed on - rating that track's quality as 99.5%, rather than the 99.9% achieved by tracks 7 and 13. So there is some definite correlation between the results.

I need to try to remember some other discs that have caused me problems with EAC. I know my Captain Beefheart Safe as Milk reports errors - there may be some tracks on that disc that have only recoverable errors (I know there are some unrecoverable ones

NEMO7538

Nov 30 2005, 15:38

Shouldn't EAC cache be disabled?

AtaqueEG

Nov 30 2005, 17:52

QUOTE(NEMO7538 @ Nov 30 2005, 03:38 PM)

Shouldn't EAC cache be disabled?

Depends on the drive.

Do you have that drive?

digidistortions

Dec 7 2005, 14:47

I ripped a CD using Exact Audio Copy and foobar2000 and the first 13 tracks were identical (tested using "shntool cmp -s"). The last tracks, however, were different. When I ran "shntool cmp -s" on them it told me, "Contents of these files are identical (up to the first 8972472 bytes of WAVE data)." When I ran "shntool info" on them it gave me this info:

EAC
data size: 8972472 bytes
chunk size: 8972508 bytes
total size (chunk size + 8): 8972516 bytes
...
sector misalignment: 1944 bytes

foobar2000
data size: 8972880 bytes
chunk size: 8972916 bytes
total size (chunk size + 8): 8972924 bytes
...
sector misalignment: 0 bytes

What could cause those differences in "sector misallignment" values? And which is the better behavior, EAC's or FB2k's?

marioosz

Dec 18 2005, 06:22

Synthetic Soul are you sure you set read offsets for all the driver correctly?
One CRC for A drivie and another for B drive may sugest an offset problem IMHO.

Synthetic Soul

Dec 18 2005, 06:36

The MD5 hash (3adf5ccf2220532a367ffaf031dd56b3) matches for all drives for the pristine test CD*, so I believe so.

* Excluding some dodgy Samsung results.

Gretchen_Ross

Mar 25 2006, 21:44

bump!!

Are there any options in V0.9 that I should know about. IE - is there anyway to export a log file during a Rip.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.