| 1 |
There have been some problems in cdda2wav that could have been discovered much |
| 2 |
earlier if there was better feedback. |
| 3 |
|
| 4 |
A nasty problem is active since Spring 2014 or even since late 2013 if you did not |
| 5 |
use c2checks. So the problem (that depends on some compiler constraints) was really |
| 6 |
visible since Spring 2014 when (as a hacky fix against dumb drives) the c2check |
| 7 |
was removed from the paraopts=proof macro. |
| 8 |
|
| 9 |
Since the problem is not triggered by the Sun C-compiler, it was not detected |
| 10 |
while testing at that time. |
| 11 |
|
| 12 |
|
| 13 |
Since some years, there is unfortunately few feedback on cdrtools. But |
| 14 |
quality also depends on user feedback..... |
| 15 |
|
| 16 |
The effect is that cdda2wav flags errors even though there is no problem: |
| 17 |
|
| 18 |
100% track 21 recorded with audible hard errors |
| 19 |
100% track 22 recorded with audible hard errors |
| 20 |
|
| 21 |
|
| 22 |
There was a problem with an uninitalized variable in libparanoia in case of |
| 23 |
disabled C2 Checks. The problem was fixed two weeks ago and published in a |
| 24 |
preliminary copy of the schily tools: |
| 25 |
|
| 26 |
http://sourceforge.net/projects/schilytools/files/ |
| 27 |
|
| 28 |
schily-dist-pre3.tar.xz |
| 29 |
|
| 30 |
Since yesterday evening, the paraopts=proof macro again includes c2check and |
| 31 |
there is an automatic fallback to the "no c2" case when the drive does not |
| 32 |
support C2 Checks. Note that this was only tested with a single drive so far, |
| 33 |
so we need more tests here from people with different hardware. |
| 34 |
|
| 35 |
Please test and report. |
| 36 |
|
| 37 |
Jörg |
| 38 |
|
| 39 |
-- |
| 40 |
EMail:joerg@××××××.net (home) Jörg Schilling D-13353 Berlin |
| 41 |
joerg.schilling@××××××××××××××××.de (work) Blog: http://schily.blogspot.com/ |
| 42 |
URL: http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/' |
Archives