Great! Thanks Jay.
It probably ought to have an *overall* time tracking facility, and some
logging. And I need to update my cdrdao to permit slowing down; I'm
ripping some bad tracks. (Perhaps a way to run the parser and
re-rip on errors?) But it's a start.
Usage: ripcdg sc 8119
Have you tried ripping using "--read-subchan rw" rather than rw_raw, to
see if your drive supports cooked mode? I can't test it here but as Will
mentioned that should add error-correction to the mix.
Failing that, you could run the .cdgs through cdg2text and grep for
whatever it is that ait prints out for unsupported CD+G commands. That
should give an indication of the quality of the rip, but won't trap
errors that still result in valid CD+G command codes.
Kelvin.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Pykaraoke-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pykaraoke-discuss
