Sometimes when I rip tracks with dbPoweramp, they contain errors. What is happening is that after six attempts to rip a dodgy track (as per my settings), and then re-ripping the problematic sector, it eventually fails, and puts a little red cross on the interface, with the legend "error". I wouldn't mind, except that it doesn't leave me with any music on the resultant file.

Instead of leaving a file with the odd bit of clipping, it leaves a file a few KB's in size and of zero length, time-wise. In order not to muck about with my settings, I then have to open up another audio ripper to rip the track once more in burst mode.

Now, I like a secure rip as much as the next man (or woman), but if a CD has errors that cannot be recovered, I would still like to have every track, even with the odd pop. And seeing as I've ripped the tracks in question multiple times in secure mode, it seems pointless to then have to rip it on final time in burst mode, when there was probably a more accurate rip already on my hard drive.

Is this a bug, or is there a setting to ensure that dbPoweramp does not trash files with errors?

There is an option on the secure page to treat insecure rips as errors, make sure this is not checked.

If the CD drive is returning an error, then the cd must be very damaged (cd drives normally return something, but occationally will refuse to rip certain sectors completely), if this is happening then secure ripper will end at that point.

Thanks. That seems to have done the trick. I had actually changed that before, but didn't realised that I never saved my settings before swapping to another configuration.