Open vguttmann opened 2 years ago
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
To help make it easier for us to investigate your issue, please follow the contributing instructions.
I did try to rip it using cdparanoia directly, and only get a few pluses on track 9.
As per cdparanoia FAQ (https://xiph.org/paranoia/faq.html#corr), those are most definitely harmless and should have no audible defects.
You can also try using the --keep-going flag. That won't solve the bad track, but it will allow it to rip the later tracks.
I have a CD that seems to have a bad track or something, and when trying to rip it, whipper finds that track 9 is faulty, tries to rip it multiple times, and then gives up completely.
Here is the output:
I know that it would be a good idea to let the user know that something is amiss, but stopping the rip entirely when encountering a faulty track while ripping the first 8 tracks seems like bad behavior to me. I'd prefer if faulty tracks were just skipped, since whipper rips and outputs every track up until the faulty one. whipper.log.gz
also, it seems like the string formatting in the error message isn't quite right 🙃
I'm using it on Manjaro (from Manjaro repos), version 0.10.0