Question about the color of text for CRC

[jspaul]

Hello everyone.

Could someone please tell me what the difference is in the color of the text for CRC after I rip a CD?

For example, some of the text is black, some is red, and some is green.

All tracks have ripped securely and have AccurateRip.

Thanks.

[LtData]

From the CD ripper help file:
CRC shows the checksum calculated from the last rip, ripping twice and the CRC numbers will show in Green if matches the previous rip CRC, or in Red if miss-matches. Miss-matching CRCs are a sure sign that one of the rips had errors.I think the CRC is black if the track has only been ripped once.

[jspaul]

Thanks. That is explains it perfectly. A couple times I had bad rips so I cleaned the CD and ripped again, the CRC would be red but it said the rip was good. The red must mean the prior rip was bad.

[Spoon]

Red means it is a miss-match with previous, last or current rip could be bad. Green is a match.

[pls1]

But as per the help file: "the green i indicates that frames had to be re-ripped, possibly an undetected error has slipped through"

Perhaps the i should be orange.

Phil

[Spoon]

Depends on drive, a drive with good c2, I would trust.

[pls1]

Depends on drive, a drive with good c2, I would trust.

Now that I've got C2 working reliably and have consistent workflow logs, if I find an error that slips through (since I'm re-ripping all tracks with such an error message on different drives) I'll let you know. Also, when I get to 100 re-ripping on a second drive due to frame re-ripping I'll post my results.

Phil

[artisan002]

Red means it is a miss-match with previous, last or current rip could be bad. Green is a match.

Ah, okay! I always wondered but was never concerned enough to ask about it. Very cool.

[artisan002]

Depends on drive, a drive with good c2, I would trust.

This raises a question I'm bound to run into even more: Given what you've said about seemingly severe inconsistency/inequality of C2 implementation across the range of optical drives, is it really something we should trust? Well, that or is there a list of drives that we can confirm handle it correctly?

[Spoon]

No drives implement C2 that it can be trusted 100%, there is a mathematical hole on c2, at a guess I would say it is around 1% (1% missed error) on spotting an error across a whole disc.

[artisan002]

No drives implement C2 that it can be trusted 100%, there is a mathematical hole on c2, at a guess I would say it is around 1% (1% missed error) on spotting an error across a whole disc.

1% error rate seems fantastic to me. Now to figure out who makes a drive that can get that accurate.