Hi, please do not use [email protected] anymore, there is nobody really listening and the only traffic seems to be spam since Debian attacked cdrtools.
Please rather use [email protected], this is where people are listening and answering. Volker Kuhlmann <[email protected]> wrote: > Trying to digitise audio CDs with cdda2wav from cdrtools 3.01 I only > get: > > 100% track 21 recorded with audible hard errors > 100% track 22 recorded with audible hard errors > 100% track 23 recorded with audible hard errors (0.1% problem sectors) > > I.e. every track is reported with "recorded with audible hard errors" as > best result. The same happens with 3.01a25. All on about 5 different > drives. This problem is active since Spring 2014 or even since late 2013 if you did not use c2checks. So the problem (that depends on some compiler constraints) was really visible since Spring 2014 when (as a hacky fix against dumb drives) the c2check was removed from the paraopts=proof macro. Since the problem is not triggered by the Sun C-compiler, it was not detected while testing at that time. Since some years, there is unfortunately few feedback on cdrtools. But quality also depends on user feedback..... > With cdda2wav 3.01a15, on the same drive as above example, the result > is: > > 100% track 11 recorded successfully > 100% track 12 recorded successfully > 100% track 16 recorded with minor problems > 100% track 18 recorded with minor problems (0.3% problem sectors) > 100% track 19 recorded successfully > 100% track 20 recorded with minor problems (0.3% problem sectors) > 100% track 21 recorded with minor problems > 100% track 22 recorded successfully > 100% track 23 recorded with medium problems (5.4% problem sectors) > > I.e. a mix of success and some (usually minor) problems. > > Between 3.01a15 and 3.01a25 is this change: > > --- cdrtools-3.01a15/cdda2wav/cdda2wav.c 2013-05-31 08:56:43.000000000 > +1200 > +++ cdrtools-3.01a25/cdda2wav/cdda2wav.c 2014-03-04 11:57:08.000000000 > +1300 > - if (para_stat->readerrs) { > + if (para_stat->readerrs || > para_stat->c2badsecs) { > fprintf(outfp, > _(" with audible hard errors")); > > Which suggests the error detection has become better. However, if every > CD and every track is read with "audible hard errors" then either the > process is flawed, all drives are not really useful, or the software is > either flawed or not so useful - I don't quite believe all pressed CDs > are that bad everywhere. > > Is there a problem in the software? > If the software is indeed operating correctly, what are good drives to > use for digitising an audio CD collection? There was a problem with an uninitalized variable in libparanoia in case of disabled C2 Checks. The problem was fixed two weeks ago and published in a preliminary copy of the schily tools: http://sourceforge.net/projects/schilytools/files/ Since yesterday evening, the paraopts=proof macro again includes c2check and there is an automatic fallback to the "no c2" case when the drive does not support C2 Checks. Note that this was only tested with a single drive so far, so we need more tests here from people with different hardware. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' ------------------------------------------------------------------------------ _______________________________________________ Cdrtools-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cdrtools-support
