Please help me interpreting this EAC-log, Rip-results of a scratched CD |
  |
Please help me interpreting this EAC-log, Rip-results of a scratched CD |
 Nov 28 2012, 10:11
Post
#1
|
|
|
Group: Members Posts: 35 Joined: 12-July 05 From: Southtyrol Member No.: 23281  |
Few days ago I've bougth a used Iron Maiden Cd, it was not in a very good state of conservation, with many scratches. After some cleaning I tried to rip it with EAC, the resulting log says:
CODE Exact Audio Copy V1.0 beta 3 from 29. August 2011 EAC extraction logfile from 22. November 2012, 8:57 Iron Maiden / Killers Used drive : ATAPI DVD A DH16ABSH Adapter: 0 ID: 1 Read mode : Burst Read offset correction : 6 Overread into Lead-In and Lead-Out : No Fill up missing offset samples with silence : Yes Delete leading and trailing silent blocks : No Null samples used in CRC calculations : Yes Used interface : Native Win32 interface for Win NT & 2000 Used output format : User Defined Encoder Selected bitrate : 32 kBit/s Quality : High Add ID3 tag : No Command line compressor : C:\Program Files (x86)\foobar2000\flac.exe Additional command line options : -5 %source% TOC of the extracted CD Track | Start | Length | Start sector | End sector --------------------------------------------------------- 1 | 0:00.32 | 1:45.63 | 32 | 7969 2 | 1:46.20 | 2:54.30 | 7970 | 21049 3 | 4:40.50 | 4:18.22 | 21050 | 40421 4 | 8:58.72 | 3:22.73 | 40422 | 55644 5 | 12:21.70 | 3:07.05 | 55645 | 69674 6 | 15:29.00 | 3:52.32 | 69675 | 87106 7 | 19:21.32 | 5:00.65 | 87107 | 109671 8 | 24:22.22 | 6:12.20 | 109672 | 137591 9 | 30:34.42 | 3:20.05 | 137592 | 152596 10 | 33:54.47 | 4:48.50 | 152597 | 174246 Range status and errors Selected range Filename G:\Musik\Iron Maiden - 1981 - Killers\Iron Maiden - 1981 - Killers.wav Timing problem 0:00:07 Timing problem 0:00:12 - 0:00:14 Timing problem 0:00:16 - 0:00:17 Timing problem 0:03:43 Timing problem 0:04:36 Timing problem 0:04:45 - 0:04:48 Timing problem 0:04:57 - 0:05:00 Timing problem 0:05:02 - 0:05:08 Timing problem 0:05:51 Timing problem 0:06:06 Timing problem 0:06:16 Timing problem 0:06:18 Timing problem 0:06:21 Timing problem 0:06:25 - 0:06:26 Timing problem 0:06:36 - 0:06:37 Timing problem 0:06:39 Timing problem 0:06:41 Timing problem 0:06:43 Timing problem 0:06:45 - 0:06:49 Timing problem 0:06:51 Timing problem 0:06:58 - 0:06:59 Timing problem 0:07:30 Timing problem 0:08:54 Timing problem 0:09:29 - 0:09:33 Timing problem 0:09:39 - 0:09:55 Timing problem 0:09:59 Timing problem 0:10:03 - 0:10:13 Timing problem 0:10:15 Timing problem 0:10:21 Timing problem 0:10:24 Timing problem 0:10:30 - 0:10:31 Timing problem 0:10:36 Timing problem 0:11:57 Timing problem 0:11:59 - 0:12:05 Timing problem 0:12:07 - 0:12:08 Timing problem 0:12:11 Timing problem 0:12:13 - 0:12:21 Timing problem 0:12:26 - 0:12:29 Timing problem 0:13:11 - 0:13:32 Timing problem 0:13:45 - 0:13:57 Timing problem 0:14:01 Timing problem 0:14:03 - 0:14:07 Timing problem 0:14:09 - 0:14:12 Timing problem 0:14:34 Timing problem 0:15:18 Timing problem 0:15:22 - 0:15:34 Timing problem 0:15:36 - 0:15:44 Timing problem 0:15:46 - 0:15:49 Timing problem 0:15:55 Timing problem 0:15:57 - 0:15:58 Timing problem 0:16:00 - 0:16:01 Timing problem 0:16:03 - 0:16:04 Timing problem 0:16:07 - 0:16:10 Timing problem 0:16:15 - 0:16:21 Timing problem 0:16:24 Timing problem 0:16:30 Timing problem 0:16:32 - 0:16:42 Timing problem 0:16:48 - 0:16:49 Timing problem 0:16:51 Timing problem 0:16:58 Timing problem 0:17:36 - 0:17:46 Timing problem 0:18:29 Timing problem 0:18:31 - 0:18:32 Timing problem 0:18:58 - 0:19:05 Timing problem 0:19:11 - 0:19:12 Timing problem 0:19:15 Timing problem 0:19:20 Timing problem 0:19:22 Timing problem 0:19:42 Timing problem 0:19:46 Timing problem 0:19:56 Timing problem 0:19:58 - 0:20:01 Timing problem 0:20:43 - 0:20:48 Timing problem 0:20:50 - 0:20:51 Timing problem 0:20:53 Timing problem 0:21:27 Timing problem 0:22:38 Timing problem 0:22:50 - 0:22:52 Timing problem 0:22:54 - 0:22:55 Timing problem 0:22:57 Timing problem 0:23:08 Timing problem 0:23:16 - 0:23:17 Timing problem 0:23:19 Timing problem 0:23:21 - 0:23:23 Timing problem 0:23:27 Timing problem 0:23:29 Timing problem 0:23:31 Timing problem 0:23:35 - 0:23:36 Timing problem 0:23:39 - 0:23:41 Timing problem 0:24:23 Timing problem 0:24:27 Timing problem 0:24:34 Timing problem 0:24:39 Timing problem 0:25:01 Timing problem 0:25:04 - 0:25:06 Timing problem 0:25:08 Timing problem 0:26:21 Timing problem 0:26:26 Timing problem 0:26:30 - 0:26:31 Timing problem 0:28:06 Timing problem 0:28:21 Timing problem 0:28:23 Timing problem 0:28:27 Timing problem 0:28:38 - 0:28:43 Timing problem 0:29:26 - 0:29:31 Timing problem 0:29:33 Timing problem 0:29:35 Timing problem 0:29:37 - 0:29:38 Timing problem 0:29:41 - 0:29:43 Timing problem 0:29:46 - 0:29:58 Timing problem 0:30:00 - 0:30:05 Timing problem 0:30:08 - 0:30:11 Timing problem 0:30:13 - 0:30:15 Timing problem 0:30:17 - 0:30:35 Timing problem 0:31:18 - 0:31:19 Timing problem 0:31:21 - 0:31:22 Timing problem 0:31:26 - 0:31:27 Timing problem 0:31:32 - 0:31:34 Timing problem 0:31:36 - 0:31:37 Timing problem 0:32:19 Timing problem 0:32:24 Timing problem 0:32:44 Timing problem 0:33:42 - 0:38:42 Peak level 99.7 % Extraction speed 2.8 X Test CRC E435686A Copy CRC 46EA545C Copy finished No errors occurred AccurateRip summary Track 1 cannot be verified as accurate (confidence 70) [45915099], AccurateRip returned [AB545ECE] (AR v2) Track 2 cannot be verified as accurate (confidence 70) [43D94978], AccurateRip returned [03286E74] (AR v2) Track 3 cannot be verified as accurate (confidence 70) [70407142], AccurateRip returned [C1BD2C64] (AR v2) Track 4 cannot be verified as accurate (confidence 69) [C11EBAA2], AccurateRip returned [19C240DB] (AR v2) Track 5 cannot be verified as accurate (confidence 69) [7B6D6652], AccurateRip returned [16F79A4F] (AR v2) Track 6 cannot be verified as accurate (confidence 69) [FE39B5E1], AccurateRip returned [89378EE9] (AR v2) Track 7 cannot be verified as accurate (confidence 69) [BC05E306], AccurateRip returned [BB29522F] (AR v2) Track 8 cannot be verified as accurate (confidence 69) [576E524E], AccurateRip returned [49BBA1C1] (AR v2) Track 9 cannot be verified as accurate (confidence 69) [B35D814D], AccurateRip returned [4F5DCCDB] (AR v2) Track 10 cannot be verified as accurate (confidence 68) [87E2CEB4], AccurateRip returned [2F26BC22] (AR v2) No tracks could be verified as accurate You may have a different pressing from the one(s) in the database End of status report ---- CUETools DB Plugin V2.1.3 [CTDB TOCID: x0EG7SCcp_M0cPDj7jbwzYVQHns-] found, Submit result: discs with pregaps not supported in this protocol version [fe1a93dc] (162/162) No match Obviously there were problems in reading the data correctly (timing problems, mismatching crc, failed accuraterip verification), but how shall I interpret the information given by eac: "No errors occurred"? Many thanks, if someone could help me! Harald |
 |
 
|
|
Nov 28 2012, 15:11
Post
#2
|
|
 Group: Members Posts: 289 Joined: 13-March 11 Member No.: 88969 |
From the EAC site:
QUOTE Question: When using burst mode, EAC also shows up timing problems, are these really errors or what? Answer: No, burst mode has no error detection nor error correction. If burst mode brings up a timing problem, the read command needed a lot of time, which could have several reasons, like loosing sync or trying to fix an read error. Of course this is a really poor “error detection” and should not be taken as serious indication. Did you try using a 'secure' mode? -------------------- korth
|
|
|
|
|
Nov 28 2012, 19:28
Post
#3
|
|
 Group: Members Posts: 1516 Joined: 30-November 06 Member No.: 38207 |
QUOTE (harto69 @ Nov 28 2012, 10:11)  Iron Maiden / Killers Well I don't think Killers was ever re-released with that pesky copy protection. -------------------- geocities.com/hydrogenaudio: http://goo.gl/tqYZj
|
|
|
|
|
Nov 28 2012, 19:35
Post
#4
|
|
|
Group: Members Posts: 11 Joined: 31-October 12 Member No.: 104212 |
QUOTE (korth @ Nov 28 2012, 15:11) From the EAC site: QUOTE Question: When using burst mode, EAC also shows up timing problems, are these really errors or what? Answer: No, burst mode has no error detection nor error correction. If burst mode brings up a timing problem, the read command needed a lot of time, which could have several reasons, like loosing sync or trying to fix an read error. Of course this is a really poor “error detection” and should not be taken as serious indication. Did you try using a 'secure' mode? 2nd that. |
|
|
|
|
Nov 29 2012, 08:03
Post
#5
|
|
|
Group: Members Posts: 35 Joined: 12-July 05 From: Southtyrol Member No.: 23281 |
Clearly my fault, I had to think about that!
Tried to rip the CD in secure mode, it took more than three hours for ripping 10 minutes of the album, then I aborted the operation. I suppose the Cd is so damaged, that an accurate reading is impossible. Thanks fpr your kind help! Harald |
|
|
|
|
Nov 29 2012, 13:33
Post
#6
|
|
|
Group: Members Posts: 171 Joined: 1-October 04 Member No.: 17420 |
|
|
|
|
|
|
Lo-Fi Version | Time is now: 20th June 2013 - 09:16 |
