I have a Pantera CD, and one of the tracks is damaged.

EAC hits the error, and then gives a read error after trying to correct for absolutley ages, i cancelled it in the end.
CDex however, rips the track and reports no errors in full paranoia mode, it does slow down a bit around the area of the error though. It doesn't report jitter or anything.

The results from CDex are awful though, i have the skipping sample in .mpc format at 160K if anyone would like a listen, i can mail it or perhaps someone could host it?

The thing is, when i ran Linux, CDParanoia always reported errors on miror scratches, they were usually corrected though, i ran a different drive then, i wonder if the drive is to blame, or CDparanoia intergration into CDex?? It should have reported some form of error!!!! Sadly i don't have Linux installed at the moment to test it in that environment.

My drive is a JLMS 166S using CDex 1.50se

Either ways, i can't extract the track at all, so i'm a bit annoyed about that!!


Thoughts and ideas about why CDex didn't report an error?

Kristian

Off-topic: Wow, the same taste in music, ripping software and codec.

Well, i'm not so sure about CDex after this incident, i only chose the codec because it seems the most popular here, i'm a FLAC and Vorbis guy. Yep, the music is cool though!!!

Cheers,

Kristian

Same here, CDex doesn't reported any error on a bad CD. The errors are inaudible (test linked in the FAQ, drive didn't cache according to both Feurio and EAC)

Does anyone know if there's a compile of cdda paranoia for win32?

In CDex open the config menu and change the CD Speed to a lower setting if you have inputted something too fast, or set a limit that will allow for more accuracy in the ripping process.

I think the default CD Speed is set to 0 meaning your drive will rip as fast as possible, however if you were to set a limit to say perhaps 4 on bad tracks you may get better results, I know doing that works for me. The drawback is slower ripping although in some cases it does allow one to rip the track without audible errors.

Well, i tried CDex at speed one and four and the results appeared even worse, much more skipping, but yet again CDex reported no error at all.

Is there any way of seeing the console output of CDparanoia from within CDex?

Anyway, i am going to try and download Cygwin and see if i can run CDparanoia from there!? Or any other ideas, i'm only on 56K thought so this might take forever!!

Cheers,

KRistian

Is the CD "only" scratched on the data side ? If yes, try to polish/repair it (there are some threads around describing how to use e.g. Brasso or some polishing agents) ... after treating the CD, it is likely that you will get better sounding results when ripping this problematic track ...

BTW, I would always prefer EAC (Secure) over CDEx ... you can play with EAC routines a bit (read modes/speed settings) and see which one will lead to the best results (especially the slowdown on errors function can be turned off to speed up DAE a bit in some cases) ... after all, EAC can't do any miracles, but its error reporting is quite reliable, compared with CDEx ...

Feurio could be an alternative as a ripper, as well as Easy CDDA Extractor ...