Many "frame errors" on perfect new CD's - what's the deal?

[tuprox]

I have a lot of Cd's that are in pristine condition and I thought that they would rip easily but that doesn't seem to be the case. After the first or second pass of ripping, I get 200-800 frames that need attention and this takes A LOT of time. I don't understand this. I don't have any other rippers that claim to have problems like this and I want to know what makes this software detect these "defects" that make them need to be re-read. I think I would get faster results in Burst mode, but is the quality as good?

Also, what does it mean when a track is ripped, it re-does the needed frames and it receives a red X and marked "insecure"?

I just can't get past all these errors I receive with CD that may be older, but they have just sat in their case and never used. How can they not be read perfectly? I don't think it is the ROM drive because all 3 of them are new and work fine with some CD's. These are all classical CD's that have been in a collection for years and all of them are failing the second pass ripping with hundreds of frames that need to be looked at.

What is going on here?



The above is an example of ripping in secure mode. I changed to burst mode and re-ripped everything but the first 5 entries in burst mode (I was going to take a screen shot, but it ejected before I could take one) and it looked something like this, with the "innacurate (21)" or (23). What does that mean, there are 21 or 23 errors?


Now I often get rips like this:

Where they are all "accurate" and then there is a "secure"

I really wisher there was a place on this site where everything was laid out and it was explained what everything meant. Is there a reason they don't do this?

[dbfan]

Re: Many "frame errors" on perfect new CD's - what's the deal?

Either change your cd drive, or disable c2 pointers if they are enabled.

[Porcus]

Re: Many "frame errors" on perfect new CD's - what's the deal?

With that many frames to re-read, the drive likely submits bogus C2 info with false error messages. In that case, solution as ********* points out.

A couple of other things:

- The Saint-Saëns with the Inaccurates: If you are using version 13 or earlier, or have not enabled cross-pressing verification, you might get 'Inaccurate' even when there are other pressings with the same audio (but the bitstream moved some milliseconds to the left or right), if none with your particular pressing have been submitted yet.
But likely this is the same C2 issue that causes it.

- The final screanshot: this is what would happen if the 12 Nessun Dorma track has not yet been submitted - if there is nothing to compare against, then there cannot be any 'Accurate'. However, it looks very strange to see 9 submissions of the others but none of this particular drive. I cannot explain that.