There have been some problems in cdda2wav that could have been discovered much
earlier if there was better feedback.
A nasty 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.....
The effect is that cdda2wav flags errors even though there is no problem:
100% track 21 recorded with audible hard errors
100% track 22 recorded with audible hard errors
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/
schily-dist-pre3.tar.xz
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.
Please test and report.
Jörg
--
EMail:jo...@schily.net (home) Jörg Schilling D-13353 Berlin
joerg.schill...@fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.org/private/
http://sourceforge.net/projects/schilytools/files/'
