Some More C2 Error Pointer, AccurateRip, and USB Ripping Questions

[RetroBurner]

Good evening! I have several questions about C2 Error Pointers, AccurateRip, and ripping discs over USB as opposed to SATA.

1) I recently purchased a BD-RE BH14NS48 (supposedly the most reliable drive according to AccurateRip). I loaded a Marker Test CD, a CD with a bunch of scratches, and a regular CD to test C2 Pointer support. All of these discs immediately report that C2 error pointers are supported without spending any time reading the disc. I am assuming that this means that C2 error pointers are NOT actually supported. Is this a correct assumption?

2) If C2 error pointers are not supported by this drive, how important are they for CD ripping? Would I be better off using my ASUS DRW-24B1ST a CD drive instead, which has an identical offset to my "new" drive and DOES support C2 error pointers?

3) Do I need to use 8 KB C2 pointer transfers over USB 3.0? I assume that if they are needed for Firewire connections, they would also be needed for USB 3.0, but would like confirmation.

4) What is the recommended number of Ultra Secure passes for drives with verified C2 pointer support? What about for drives that DO NOT have C2 pointer support?

5) If C2 error pointers are not actually supported by a drive but are turned on in the CD Ripper Options, how would that effect the accuracy of the CD rip? dbPoweramp is telling me that I was able to get accurate rips on my BD-RE BH14NS48, and doing post-ripping AccurateRip testing in PerfectTunes seems to support that assessment, but is this an accurate conclusion?

6) Are there any other pieces of software besides dbPoweramp that can test if C2 error pointers are supported by a given CD/DVD/BD drive?

7) Is there a way to upload my AccurateRip results for the discs that I have ripped after ripping has been completed (i.e. without AccurateRip turned on at the time of digital audio extraction)?

8) I am unable to rip some discs with any of my external CD/DVD/BD drives. They just come up as "Error" in dbPoweramp. However, I have a ASUS DRW-24B1ST inside an older computer with a SATA connection that can rip these discs just fine. Why am I unable to rip these discs over USB? Would it be prudent to always have a machine with SATA connections for ripping instead of relying on computers connected to external disc rippers via USB 3?

Thank you very much in advance for your assistance!

[Spoon]

1. Insert a pristine disc, it should run a long time and not find C2 for a long time, or at all.
2. C2 helps, it is difficult to say how much in comparison without
3. Not normally
4. ultra secure is there to try to find bad rips with tracks which are not in AccurateRip, there is a detection hole, with c2 that hole is smaller, but still there
5. If the test detected C2 but when ripping does not, it suggests it is working.

7. no
8. Perhaps the drive needs a powered USB hub? error means the drive is giving no data at all

[RetroBurner]

1. Insert a pristine disc, it should run a long time and not find C2 for a long time, or at all.

It just instantly says “C2 Support Detected” no matter what disc I put in (pristine or not).

3. Not normally

Does it do any harm to leave the 8KB C2 Error Pointers on over USB 3.0?

5. If the test detected C2 but when ripping does not, it suggests it is working.

Where can I see where the ripper confirms that C2 works? Is it in the post-ripping logs?

8. Perhaps the drive needs a powered USB hub? error means the drive is giving no data at all

The drive is powered via an external AC adapter. I was able to rip many, many discs successfully off of this drive - there’s just 3 discs that won’t rip that generate “Error” results.

[Spoon]

It is unlikely c2 is working then, it should not flag it up when no errors.

I would not leave that 8kb option on.

If you rip in secure and have detailed logs, it will say something like c2 error dropped (24/27) meaning c2 was detected and the frame dropped on 24 re-rips out of 27

[RetroBurner]

It is unlikely c2 is working then, it should not flag it up when no errors.

I would not leave that 8kb option on.

If you rip in secure and have detailed logs, it will say something like c2 error dropped (24/27) meaning c2 was detected and the frame dropped on 24 re-rips out of 27

Ok. Would you recommend that I re-rip everything that I did with the 8 KB option on?

[Spoon]

Not if accuraterip has verified it