CD player and EAC fail on track 14 of CD-Extra -- what is wrong? Options

[guest0190]

I am trying to rip a soundtrack CD-Extra containing 21 tracks in a Red Book session and a few programs in a Yellow Book session after that. (At least that's how I think it works.)

My CD player is only able to play tracks one through fourteen, and while I haven't tried ripping it with EAC yet, gap detection fails using gap detection method A and C, and only gets to track 14 with gap detection method B. The gap detection is slow all the way, but appears to stop completely at track 14.

What could be the cause of this? Could it have anything to do with the data session?

I think other people have ripped this CD successfully. The disc is brand new and has no visible scratches, though I don't think that would cause this type of error.

I posted the same question on MyCE here: http://club.myce.com/f57/eac-cd-player-fai...74/#post2648134

[korth]

According to the FAQ, you should try setting 'Detection accuracy' to 'Inaccurate' if the disc hangs. Did you try that?

[guest0190]

Will do, but, with the risk of sounding foolish, will the inaccurate mode not give inaccurate results?

[korth]

It does the fewest rechecks so it is less accurate than the other settings but it also has a time limit so it won't hang.

[greynol]

EAC is having trouble with your specific drive. Try creating the sheet with a different one.

I'm done ranting about how silly it is to obsess about the accuracy of non-01 index locations (except to say that it is silly!). 01 index locations will always be accurate and don't even matter if you are ripping one track per file.

This post has been edited by greynol: Aug 9 2012, 01:06

[guest0190]

I tried it with an HP drive yesterday (my main one is an external Plextor) and the same problem occurred.

I tried again today and left it on for half an hour or so, and now the gap detection seems to have completed. Strange.

But I still can't play it further than track 14, and the fact that the gap detection halts after track 13 as well seems like a strange coincidence. Does anybody know why this is so?

greynol, just out of curiosity, why is it that you think creating cue sheets is silly? The only reason I'm really doing it is because it's part of my routine, but if I should ever lose the CD, it feels good being able to burn an identical copy.

Update:
EAC behaves very strangely when trying to rip the CD. It spins up, and then stops, spins up, and stops ... It's done this for minutes now and EAC has stopped responding.

This post has been edited by guest0190: Aug 9 2012, 15:32

[probedb]

It sounds like a dodgy disc that it's having trouble reading especially if it behaves the same on another drive. Have you tried copying the disc as a whole just to see what happens? Or maybe setting EAC not to go above a certain read speed whilst just ripping that track?

Also greynol didn't say he thought creating cue sheets was silly anywhere in his reply.

[pdq]

If, as you say, it fails to play on a CD player, then it is defective and you need to gat a replacement. CD producers may not guarantee the ability to rip the audio from their discs, but they certainly guarantee that they will play on a standard CD player.

[greynol]

CD producers [...] certainly guarantee that they will play on a standard CD player.

Yes and no.

In the past, at least some producers of CDs with DRM copy-protection did not guarantee playback on all CD players and made sure to indicate this by not including the "compact disc digital audio" logo at a minimum, or by stating so explicitly.

Good catch, BTW. I missed the part about players earlier.

This post has been edited by greynol: Aug 9 2012, 21:27

Reason for edit: DRM -> copy-protection and other wording.

[guest0190]

I tried it in an older player (as in from the 80s), and it played all the tracks I threw at it, including several above track 13. The only odd thing was it had to search for a long while before starting playback of track 12. Note that this player has been known to play damaged CDs that other players have refused (I suspect this has to do with more forgiving error correction, but as the clueless layperson I am deep down, I'm not sure), but as stated above, the CD plays more or less without problems, and there are no visible scratches on the disc.

I tried ripping it in Burst Mode, and it appeared to work initially. However, extraction was very slow, and the drive displayed the same "spin up -- stop" pattern as previously, though with longer intervals this time. Eventually EAC reported "Timing Error", but continued extraction. I stopped it manually.

Does this clear anything up?

[probedb]

Does this clear anything up?

Yes, your disc is screwed.

I'd say the only solutions are to either buy a new one or get a hold of the tracks you can't rip by some other means.

[guest0190]

Just out of curiosity, what exactly does 'timing error' mean?

[greynol]

Data took longer to return than what the program considered normal. Are you sure it said timing error and not timing problem?

It may seem like a minor detail, but I believe the term problem was chosen over the term error because data arriving late does not necessarily mean it arrived in error.

This post has been edited by greynol: Aug 10 2012, 18:19

[guest0190]

I tried ripping it again (still in Burst Mode, but after a reboot) and now it seems to work quickly and flawlessly. No timing error in sight. I'll wait and see if I can get an AccurateRip match.

Update:
All tracks accurately ripped, no errors occured. Gap detection is still excruciatingly slow, though.

I checked the log file of the previous ripping attempt, and sure enough, it said "timing problem: 0:00:00-0:00:56".

This post has been edited by guest0190: Aug 10 2012, 18:51