[linux-audio-dev] cdparanoia fails / audiofile comparer

Hello. Anyone would like to develop cdparanoia further? I ripped a CD two times with the following results: (== PROGRESS == [ !-------| 159332 00 ] == :^D * ==) (== PROGRESS == [ + + + | 159332 00 ] == :^D * ==) The errors are explaned this way: - Jitter correction required + Unreported loss of streaming/other error in read ! Errors are getting through stage 1 but corrected in stage2 Which error is more severe: "+" or "!"? Is "+" corrected properly? The problem is that the channels of other ripping are swapped at the point where "!" is located (but "!" may not have caused it). I don't know which one of the rippings is incorrect (they both could be incorrect). The channels also have one sample offset after the swap. The second ripping has "+" before the "!" point, but both rippings are indentical up to the "!" point. Would that mean that "+" is a harmless error and that thus the second ripping is correct? And that we should rewrite only the algorithm handling the "!" errors? In addition to rewriting "!" handling (or "+" handling if that caused the channel swap), I would like get out a printed list of errors. The error list could then be used in an audio editor for marking the errors with red color (say). Also an audiofile comparer program would be great to have: a program which finds matching regions. Now it was easy to compare the regions up to the "!" point with md5sum program, but it was difficult to compare the end part due misaligning. I compared them visually at a few random points. In such a comparer program each matching sample would match bitwise for this application, but they could match with an error tolerance if the application is to compare an original audio and an edited audio which is affected by dither noise (say). So, such a comparer would reveal what edits were done in an audio editor -- I have needed such a program a few times earlier. Regards, Juhana