Open GoogleCodeExporter opened 9 years ago
Corrected the cdparanoia log (which was empty).
Original comment by comradec...@gmail.com
on 17 Jun 2012 at 3:14
Attachments:
I believe that there are two pieces for a proper resolution to this:
1. Integration of CTDB will provide not only for accurate rip checking, but
also provides for repairing rips.
2. Another fix would require directly accessing libparanoia and doing ripping
directly using the C-interface to get detailed information about the number of
frames with errors. This would require a dependency on ruby-ffi, however.
Original comment by comradec...@gmail.com
on 23 Aug 2012 at 1:52
The following patch addresses point 2 by using the "-e" flag on cdparanoia and
then reading the output and counting instances of notable errors (like that
used in XLD logs). If rubyripper finds two matching rips, but cdparanoia
reported errors with the rips, the details from cdparanoia will be included in
the log, such as in the (also attached) log file.
I've yet to commit the patch to master, pending review of the code and properly
merging the patch with HEAD (the patch is relative to commit 8c38d19)
Original comment by comradec...@gmail.com
on 25 Aug 2012 at 9:57
Attachments:
Oops. Fixed empty patch.
Original comment by comradec...@gmail.com
on 25 Aug 2012 at 9:59
Attachments:
Original comment by boukewou...@gmail.com
on 9 Jan 2013 at 10:45
Original issue reported on code.google.com by
comradec...@gmail.com
on 17 Jun 2012 at 3:13Attachments: