CUERipper and Pioneer (PureRead)

[NotCommonUser]

Pioneer with newer drives has this PureRead option which can be enabled on the drive. When enabled, drive itself re-reads faulty part number of times and only if not so successful returns interpolated data or totally bails-out (depending on setting).
Now with cueripper when C2 errors are returned software automatically goes into retry mode getting x35 retries - this gets multiplied by automatic pureread re-reads and takes incredible amount of time.

My kind request is to make number of software re-reads on c2 error configurable, starting with 0, so that it can be set to 0 on pureread capable drives. Preferably it should be stored in the configuration file in the section for specific drives (like C2 mode).

[c72578]

@NotCommonUser Thanks for your report concerning PureRead capable drives.
What is the behavior, if you select C2 Error Mode None in CUERipper?

[NotCommonUser]

Hi.
Thank you for the suggestion.
I am running BDR-XD08 with Pureread3+ enabled in master mode (retry and report interpolated date if impossible to reread).

I have set C2 error mode to none and... it seems that i am getting intended behavior. Drive itself re-reads troubling parts. In my sample CD backup test i am getting "AR: rip not accurate (0/576), CTDB cannot be verified, insufficient quality". With C2 set to Mode296 copy takes forever but then i am getting better result with AR/CTDB with tracks which are still repairable.

Now, interestingly, with pureread totally disabled and c2 mode enabled (mode 296) i am getting same quality as with pureread enabled and c2 enabled. Just the cd backup takes 4 mins, not an hour. So weird. Looks like this pureread is more of marketing or there is something more that is needed to get the benefit...

So at the end i think that providing configuration parameter to set number of retries after c2 error would give more flexibility in setting up the application for bit more exotic configurations (like this pureread...).