Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: No AccurateRip report in Eac log, help (Read 8065 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

No AccurateRip report in Eac log, help

I spent hours configuring EAC, checked on several guides, everything seems fine, but i still can't get AccurateRip report in log file. I do see it in separate window, but i need it in text file along with other info. I'm using V0.95 beta 4, and i don't even have option "Use this drive with AccurateRip" in offset / speed tab, but AccurateRip is still working, just not showing the report in log.

Here's the log, many thanks in advance, how do i get the AccurateRip report in this log, it's driving me nuts.. (everything seems ok, the HKEY registry value for CD-NoAccurateRip is also right)

Code: [Select]
EAC extraction logfile from 9. January 2014, 7:59 for CD
Various / Stockholm Ultimate Techno Frequencies No 1

Used drive  : Optiarc DVD RW AD-7203S  Adapter: 0  ID: 2
Read mode  : Secure with NO C2, accurate stream, NO disable cache
Read offset correction : 48
Overread into Lead-In and Lead-Out : No

Used output format : C:\Program Files\FLAC\flac.exe  (User Defined Encoder)
                    320 kBit/s
                    Additional command line options : -6 -V -T "ARTIST=%a" -T "TITLE=%t" -T "ALBUM=%g" -T "DATE=%y" -T "TRACKNUMBER=%n" -T "GENRE=%m" -T "COMMENT=%e" %s -o %d

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:\Om 2\01 - Andromatic - Pure Energy.wav

    Pre-gap length  0:00:02.00

    Peak level 100.0 %
    Track quality 100.0 %
    Test CRC 6DA3C000
    Copy CRC 6DA3C000
    Copy OK

Track  2
    Filename D:\Om 2\02 - Andromatic - Let the Spirit Move You.wav

    Pre-gap length  0:00:02.28

    Peak level 100.0 %
    Track quality 100.0 %
    Test CRC 63D1A23E
    Copy CRC 63D1A23E
    Copy OK

Track  3
    Filename D:\Om 2\03 - Cre8ors - Elevation.wav

    Pre-gap length  0:00:02.05

    Peak level 95.3 %
    Track quality 100.0 %
    Test CRC 45D0D26B
    Copy CRC 45D0D26B
    Copy OK

Track  4
    Filename D:\Om 2\04 - Trauma - Comin' up Good.wav

    Pre-gap length  0:00:01.35

    Peak level 100.0 %
    Track quality 100.0 %
    Test CRC 0AC4CC50
    Copy CRC 0AC4CC50
    Copy OK

Track  5
    Filename D:\Om 2\05 - Litium 6 - Search.wav

    Pre-gap length  0:00:02.12

    Peak level 100.0 %
    Track quality 99.9 %
    Test CRC FD568FE6
    Copy CRC FD568FE6
    Copy OK

Track  6
    Filename D:\Om 2\06 - Cerebus - Nechromancer.wav

    Pre-gap length  0:00:01.30

    Peak level 97.6 %
    Track quality 100.0 %
    Test CRC F87B9E1F
    Copy CRC F87B9E1F
    Copy OK

Track  7
    Filename D:\Om 2\07 - Source - Source.wav

    Pre-gap length  0:00:02.17

    Peak level 100.0 %
    Track quality 100.0 %
    Test CRC 9262CF57
    Copy CRC 9262CF57
    Copy OK

Track  8
    Filename D:\Om 2\08 - Source - Mental Resurrection.wav

    Pre-gap length  0:00:02.17

    Peak level 100.0 %
    Track quality 100.0 %
    Test CRC 5517F8C0
    Copy CRC 5517F8C0
    Copy OK

Track  9
    Filename D:\Om 2\09 - Source - Levitation.wav

    Pre-gap length  0:00:01.70

    Peak level 100.0 %
    Track quality 100.0 %
    Test CRC 0033C15B
    Copy CRC 0033C15B
    Copy OK

Track 10
    Filename D:\Om 2\10 - RND - Transform II.wav

    Pre-gap length  0:00:01.48

    Peak level 100.0 %
    Track quality 100.0 %
    Test CRC D9034278
    Copy CRC D9034278
    Copy OK

Track 11
    Filename D:\Om 2\11 - Spasm - Spasm.wav

    Pre-gap length  0:00:02.20

    Peak level 100.0 %
    Track quality 100.0 %
    Test CRC 8AB03749
    Copy CRC 8AB03749
    Copy OK

Track 12
    Filename D:\Om 2\12 - Hypernature - Mind and Body.wav

    Pre-gap length  0:00:02.40

    Peak level 99.9 %
    Track quality 100.0 %
    Test CRC 8CE7EC12
    Copy CRC 8CE7EC12
    Copy OK

Track 13
    Filename D:\Om 2\13 - Spacelab - Wet.wav

    Pre-gap length  0:00:01.38

    Peak level 97.1 %
    Track quality 100.0 %
    Test CRC 7F38CF15
    Copy CRC 7F38CF15
    Copy OK

No errors occured


End of status report

No AccurateRip report in Eac log, help

Reply #1
These are my settings


No AccurateRip report in Eac log, help

Reply #2
I'm using V0.95 beta 4

That's from 2006. AccurateRip logging wasn't really begun until 2007 in 0.99 prebeta 1, and according to WhatsNew.txt it wasn't working very well until 0.99 prebeta 4 in 2009. If you were using one of the 1.0 betas, you'd have AccurateRip v2 support as well. Why not just use the current version?

No AccurateRip report in Eac log, help

Reply #3
I'm using V0.95 beta 4

That's from 2006. AccurateRip logging wasn't really begun until 2007 in 0.99 prebeta 1, and according to WhatsNew.txt it wasn't working very well until 0.99 prebeta 4 in 2009. If you were using one of the 1.0 betas, you'd have AccurateRip v2 support as well. Why not just use the current version?


Thanks, i'm still running XP, so i can't use the current version, i will try with 0.99 prebeta 5, that seems the latest one available that will work with XP i guess.


No AccurateRip report in Eac log, help

Reply #5
That solved the problem regarding AccurateRip report, thanks, the only thing is that the ripping process with the same settings as before is much longer for some reason.


No AccurateRip report in Eac log, help

Reply #7
I have no idea what you are quoting.

Support was removed for Windows 2000 and older.  The program will run on Windows XP.

No AccurateRip report in Eac log, help

Reply #8
That solved the problem regarding AccurateRip report, thanks, the only thing is that the ripping process with the same settings as before is much longer for some reason.

Are you using the recommended approach...rip in burst mode (very fast) and if you get AccurateRip verification you are done. If you do not get verification then rip a second time in burst mode and compare checksums. If checksums match then you are done. If checksums do not match then try a secure mode.

Alternatively get a copy of dBpoweramp, which does all of this automatically.

No AccurateRip report in Eac log, help

Reply #9
That solved the problem regarding AccurateRip report, thanks, the only thing is that the ripping process with the same settings as before is much longer for some reason.

Are you using the recommended approach...rip in burst mode (very fast) and if you get AccurateRip verification you are done. If you do not get verification then rip a second time in burst mode and compare checksums. If checksums match then you are done. If checksums do not match then try a secure mode.

Alternatively get a copy of dBpoweramp, which does all of this automatically.


I didn't rip in burst mode, cause when i check the burst mode, the "Secure mode with following drive features (recommended)" gets unchecked, and i read that it should be checked, so that's why...
I will try for the next rip...but am a little confused as i read everywhere that this ^ should be enabled, and when it is, the burst mode is automatically disabled.

I'm usually using Dbpoweramp, but this was by request of one of my friends whos Eac nut, so he wanted me to make flac files for him in EAC, he said dbpoweramp is not as good as EAC, because
1) EAC reads Audio-CD in secure mode
2) EAC corrects errors when ripping
3) EAC creates ripping log, and you can check if there were errors when ripping

which i'm not sure is totally relevant..as i think dbpoweramp can do some of that, but i agreed to do it for him, hence all the hassle with setting up EAC

No AccurateRip report in Eac log, help

Reply #10
I have no idea what you are quoting.

Support was removed for Windows 2000 and older.  The program will run on Windows XP.


That's what i see when i get to download the latest version of EAC. I don't have Vista nor Windows 7 or 8, so i figured it doesn't run in XP othewise it would be mentioned as well (:

If not, it's a huge mistake by them, cause why would you mention Vista, Windows 7 & 8 as system requirements and not XP, if it runs in XP also? i don't understand..

No AccurateRip report in Eac log, help

Reply #11
1) EAC reads Audio-CD in secure mode

dBpoweramp has a secure mode that is arguably more secure than EAC.

2) EAC corrects errors when ripping

Technically it doesn't, except for synchronization errors.

3) EAC creates ripping log, and you can check if there were errors when ripping

...so does dBpoweramp

Your friend doesn't know what he's talking about.

No AccurateRip report in Eac log, help

Reply #12
That's what i see when i get to download the latest version of EAC.

Download from where?

This page makes no mention of system requirements for the latest version:
http://www.exactaudiocopy.de/en/index.php/resources/download

Neither does any other page on the official EAC website in any direct sense, other than what I told you already: support for Windows 2000 and older is dropped, implying that anything after 2000 will work.


No AccurateRip report in Eac log, help

Reply #13
That's what i see when i get to download the latest version of EAC.

Download from where?

This page makes no mention of system requirements for the latest version:
http://www.exactaudiocopy.de/en/index.php/resources/download

Neither does any other page on the official EAC website in any direct sense, other than what I told you already: support for Windows 2000 and older is dropped, implying that anything after 2000 will work.



Omg, i was taken to another page from Eac download page...if you click basically anywhere on that page, it opens a new window with Easy Audio Copy =)) that's where it stands about system requirements...i didn't pay attention, i thought that was the next step for downloading...

No AccurateRip report in Eac log, help

Reply #14
Ripping guides will naturally disagree on settings and procedures. If you are making your rips for someone else, they probably have some preferences that are based on what someone has told them, and an incomplete understanding of what rippers do. Their sense of what settings and rippers are best may also be influenced by the guides produced by well-meaning but overly bureaucratic file-sharing communities. IMHO, you should figure out what's best for you, and you should educate your friend, because he's wrong on several points.

Logging can vary from ripper to ripper, but those with secure mode all support writing some kind of log indicating which tracks ripped with & without error.

EAC, CUERipper, dBPoweramp, and several other rippers all have "secure" modes, which simply mean there is some kind of error detection & re-read-based correction during ripping. They each do it slightly differently, so their efficiency and ease-of-use varies, but in my experience, the end results are the same, as far as what errors are detected and how well they are corrected.

Error detection is tricky. The drive, if directed to do so by the ripper, may do its own error detection and optional correction, using "C2" checksums (of a sort) encoded on the CD. However, drives vary wildly in how well they support this feature. Aside from that, the ripper can check to see if the data is consistent with other reads of the same CD. Consistency isn't guaranteed to be a measure of correctness, but it's the best we can do.

One way of testing consistency is by using AccurateRip and CTDB, which are external databases allowing us to compare a checksum of our rip's audio data with checksums of rips made by others. These comparisons are done on a per-track or per-disc basis. Another way is by simply reading from each sector on the disc at least twice and seeing if the sector audio-data checksums match. A variation of this is EAC's "test & copy", where each sector is read once, but in two passes, the first one being just to get track checksums to compare to the actual rip done in the 2nd pass.

A checksum mismatch from our own re-reads, or a C2 pointer to data that the drive may not have corrected, indicates a possible error. A "secure" ripper can try to correct this maybe-error by repeatedly reading the suspicious spots until there's a match. Of course, it's possible this isn't correcting anything, but rather just reads the same bad data twice, but again, it's the best we can do, and it is why the external databases are helpful.

"Burst" mode is what all ordinary rippers use, and is basically just reading data from the CD in big chunks, and may or may not involve checking it for consistency (depends on the ripper, I think). Burst mode is unlikely to result in error-free reads if the CD is scratched/dirty/defective, but it is very fast, and with a good drive should work well on clean discs. Some drives (like mine) have a lot of trouble reading error-free in burst mode, even at low speed, for unknown reasons, so I always have to use secure mode.

So you can see why pdq suggested the strategy he did... however, it's just one possibility. If you know the disc is scratched, then doing 1 full-disc burst rip, followed by a burst re-rip of tracks with errors (or another full-disc rip, if you're doing an image rip), and then doing a secure rip after all of that sure seems a bit much! This is where e.g. dBPoweramp's error detection & correction strategy is superior to EAC's, IIRC.

No AccurateRip report in Eac log, help

Reply #15
What?!? There is a ripper that is actually better than EAC?

What nonsense!   

No AccurateRip report in Eac log, help

Reply #16
What nonsense!   

I don't know if you're being sarcastic, but both dBpowerAMP on Windows and XLD on OS X are _much_ better than EAC.

EDIT: By better, I mean more user-friendly and easier to set up while yielding results just as accurate as EAC.

No AccurateRip report in Eac log, help

Reply #17
Secure ripping is a holy grail obsession for some people (and is/was generally accepted on HA), but IME it's not fit for purpose. It was the best we had before AccurateRip, but people need to let go of out of date ideas.


If you trust "secure" ripping, both EAC and dBpa will happily tell you rips are "secure" when in fact they are totally wrong. They only need to go wrong in the same way often enough to match whatever statistics you asked for.

I've seen this issue on a little less than 1% of my rips: one track is obviously damaged, because it's the only one to fail AccurateRip checking, but with typical settings it can still be ripped "securely". Listen to the rip, and the fault is sometimes audible. AccurateRip was correct, "secure" ripping was misleading.

Re-ripping (either immediately, and/or after attempting a physical repair) can be useful to get an AccurateRip match, but I'm now convinced that AccurateRip fail + "secure" rip match is a bad result. So what's the point of a "secure" rip? Better than nothing, but not as "secure" as many people seem to think.


Also, it may just be the condition of the CDs I rip (mostly flawless, occasionally wrecked) or my drives, but when AccurateRip says no, thrashing around re-ripping for minutes trying to get the same result sector by sector doesn't usually seem to deliver any better audible result than the first or second faulty burst rip. Sometimes it's worse, with muted audio in the burst rip replaced by "secure" but clearly garbage audio at the end of the process.

I know it must work for some people some times on some CDs in some drives, and if your CD isn't in AccurateRip you don't have much choice (apart from CueTools later), but using it as the default ripping method in 2014 is misguided IMO.

(I am far from being an expert in this area. I just speak from a little experience.)

Cheers,
David.