Disc shows as not present in AccurateRip, then DOES after removing CD and reinserting

[joeyc410]

Hi all,

I've noticed a strange glitch that rarely (but still) occurs where I insert a disc into my drive, allow CD Ripper to load, and I see the gray X on the bottom of the page that indicates the album is not in the AR database. Depending on the album, I question whether or not it is likely that the album will be in the database. I have a few albums that, upon first insertion into my drive, originally come back as not in the database, but because that seems odd to me (given the popularity of the album), I decide to take the disc out, close CD Ripper, and try again after reopening the program. Upon my second try, the album begins showing as part of the database. I should state that this issue DOES NOT pertain to any particular album. I conclude this because why would a popular album show as not in AR when it in fact is?

My more important question is this - suppose I thought an album was not in the database, and it actually was, but because I was told by CD Ripper that it was not, I go ahead and rip it in secure mode. I get all green checks after many passes of ripping and can conclude that the program has ripped the disc without errors. Is the secure rip I just completed equal to the one in AR, IF the album actually is in AR, but is simply not showing that it is due to a glitch?

It feels like there may be an instance where the program can mislead me and I could potentially have no idea.

[sower]

Hey, I’ve noticed that too on occasion. From what I understand, a secure rip with all green checks should still be just as reliable, even if AccurateRip didn’t recognize the disc at first. It’s likely just a timing or recognition hiccup between the drive and the database. Re-inserting usually clears it up, like you said.

[garym]

secure rip is not identical to AR match, but close enough for me. Making up numbers, it is the idea that a secure rip result indicates that the rip is bit perfect with a 1 in a million chance it is not. But AR match, it is 1 in a trillion chance there is still an error. In both cases, the likelihood of a bad rip is very remote.

edit: and of course one can compare a rip later on to see if it has an AR match (PerfectTunes can do this, as well as foobar2000 or CueTools).