Drive not working after upgrade from DMC13.0 to 13.1

[JWV]

I recently upgraded the CD Ripper from 13.0 to 13.1 and then 13.2. Whereas CD Ripper was working brilliantly in its initial version, it now won't rip anything from my LG GE20LU10 USB-drive with "secure ripping". I ripped many cd's but now can't rip any.
I didn't change any settings. The drive still works excellent with EAC. I can playback the music from the loaded cd's, even with the player in DbPoweramp. I manage to rip cd's in the "defective by design" mode without any problem. But the whole point of ripping with DbPoweramp is the secure mode, to check against Accuraterip and all.
DbPoweramp reads the contents of the CD just fine, it displays the artists, titles and finds the cover pictures. But when I press "Rip", is stalls. The drive spins up, lights blink for a while, but the progress bar remains at 0%. After a while, ripping stops and errors are displayed:

Error ripping to FLAC 'Track 1' to 'F:\Michael Jackson\Thriller\01 Wanna Be Startin' Somethin'.flac'
Unable to read CD, check CD disc (frame LBA 27 ripping 26 frames track end LBA 27260) [dRipper Secure::Rip]

Similar messages for each track, always ripping 26 frames. The discs are not the problem as I can rip them on my other machine with DbPoweramp and with EAC.

CD Ripper still works fine with the internal drive of my Fujitsu Siemens laptop, but I don't want to use that because it has a dirty lens (unrecoverable).
I tried wiping and re-installing DbPoweramp on my system, without any result. I tried other machines: same problem with this specific drive.

Did anything change from 13.0 to 13.1/13.2 that is preventing my CD Ripper from corresponding?

Please help, I have about 1,000 discs to go, using just one machine is hardly an option.

Thanks,
JW

[Spoon]

Re: Drive not working after upgrade from DMC13.0 to 13.1

C2 pointer support over firewire was added (so the block size of the c2 pointer request was lowered).

First off if c2 is checked, uncheck-it and see if ripping works (this would highlight c2 pointers as causing the issue).

[JWV]

Re: Drive not working after upgrade from DMC13.0 to 13.1

Thanks Spoon for the quick answer!

Unchecking C2 does the trick indeed. It now rips just fine.

Just to make sure (I can't make much of all the theories on C2 pointers): will ripping without C2 make my rips less secure? Is there any solution for this?

[bhoar]

Re: Drive not working after upgrade from DMC13.0 to 13.1

Did it stop working correctly with 13.1 or 13.2? If it worked with 13.1 but not 13.2, perhaps there was a regression...

C2 pointer support over firewire was added (so the block size of the c2 pointer request was lowered).

First off if c2 is checked, uncheck-it and see if ripping works (this would highlight c2 pointers as causing the issue).

C2 pointers or the larger transaction size required to support C2 pointers.

IIRC, you also added a routine in 13.1 to adaptively back-down the buffer size (number of frames per read) if errors were reported with the larger buffer (frame count). Perhaps this approach isn't working well with some drives and/or bridges?

I'm again diagnosing before looking at the patient here, but I do think a user-accessible option to cap the transaction sizes at 32KB per read (e.g. cap the frame count per read so that when C2 was enabled the read is still < 32KB) would be likely to clear up some of these issues. Likely...

-brendan

[JWV]

Re: Drive not working after upgrade from DMC13.0 to 13.1

13.0 was fine, problems started after installing 13.1