Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Unexpected behavior from 'Paranoid' CD Ripping (Read 728 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Unexpected behavior from 'Paranoid' CD Ripping

I have been using foobar2000 for about 5 years, and I have witnessed how 'paranoid' works with CD ripping.  I have seen it actually refuse to create the final file if it couldn't guarantee a perfect, error corrected result.

So, I was very surprised recently when a 'paranoid' rip resulted in a completely glitched file.  Here's what happened:

1. Rip CD in Paranoid mode.
2. A few errors are found and "corrected":
    Secure mode: CRC mismatch, retrying.
    Secure mode: match found after 68 attempts.
    Secure mode: CRC mismatch, retrying.
    Secure mode: match found after 1 attempt.
    Encoder process still running, waiting...
    Encoder process terminated cleanly.
    Track converted with minor problems.
AND
     1 out of 1 tracks converted with minor problems.
     Source: "cdda://00E22D95" / index: 2
     Secure mode: CRC mismatch, retrying.
     Secure mode: CRC mismatch, retrying.

3. The track is audibly glitched/corrupted upon playback.

How could this happen??  This was a mid 80s Warner Bros CD with minor blemishes.