[Abcde-users] how to better cope with broken tracks?
Tom Roche
Tom_Roche at pobox.com
Wed Nov 4 00:21:47 GMT 2015
[Note
* some of the following condensed+added to https://wiki.debian.org/Ripping#ripping_audio_CDs_to_MP3s_with_abcde
* will do likewise @ http://abcde.einval.com/wiki/ if given an account.
]
Tom Roche http://lists.einval.com/pipermail/abcde-users/2015-November/000178.html
>> So my current questions are: 1. How can I correctly drive the ripper for usecase={one track fails, rest are good}?
Alan W. Kerr http://lists.einval.com/pipermail/abcde-users/2015-November/000179.html (reordered)
> abcde -h
doh! forgot to RTFCH! added that to https://wiki.debian.org/Ripping#ripping_audio_CDs_to_MP3s_with_abcde
Not sure why that works and driving `cdparanoia` from the config does not, but I suspect it's failure to handle non-0-but-non-error retval, so I made http://abcde.einval.com/bugzilla/show_bug.cgi?id=19 . I also noted a separate bug (or FR--YMMV) regarding current parsing of the commandline "trackspec" @ http://abcde.einval.com/bugzilla/show_bug.cgi?id=18 . (And added links @ https://wiki.debian.org/Ripping#handling_broken_tracks )
>> 3. If (there is) not (currently A Better Way to tell `abcde` [to continue ripping subsequenttracks after track failure]), should this be a feature request, or is this functionality out-of-scope for `abcde`?
> It would be useful to have a simple method to say "ripping taking too long: skip to next track".
Accordingly I made http://abcde.einval.com/bugzilla/show_bug.cgi?id=20 ; your comments on and votes for this FR are appreciated.
HTH, Tom Roche <Tom_Roche at pobox.com>
More information about the Abcde-users
mailing list