rip fails always on the last track

[https://www.google.com/accounts/o8/id?id=aitoawntwypllofbqls0mnr2qbdctzzzz2ik7_g]

Hi,

I'm running morituri on Ubuntu 11.10 and I'm using a Benq DVD DD DW1640 drive.
I always get an error on the last track (see attached log).

[https://www.google.com/accounts/o8/id?id=aitoawntwypllofbqls0mnr2qbdctzzzz2ik7_g]

Debug log

[https://www.google.com/accounts/o8/id?id=aitoawntwypllofbqls0mnr2qbdctzzzz2ik7_g]

Oh, just to be clear: I get this on every last track on every CD I tested so far.

[http://thomasvs.myopenid.com/]

Looking at your drive at  http://www.daefeatures.co.uk/search.php it looks like your drive is incapable of ripping LEADOUT overread. Given your high offset, it may be that your drive is incapable of ripping the last track correctly. Can you try and rip it with cdparanoia from the command line:

cdparanoia [x]

Replace [x] with the number of the last track

And paste the output of paranoia here ? I expect it to fail or mention that it's filling in the data with zeroes.

[https://www.google.com/accounts/o8/id?id=aitoawntwypllofbqls0mnr2qbdctzzzz2ik7_g]

Ok, you are right.
I ran "cdparanoia -v -O 618 9" where 9 is the last track on the CD. I have attached the output containing the errors.

Is there anything I can do about that except buying another drive that supports reading leadin or leadout depending on its offset?

[https://www.google.com/accounts/o8/id?id=aitoawntwypllofbqls0mnr2qbdctzzzz2ik7_g]

Log of cdparanoia read errors

[http://thomasvs.myopenid.com/]

Well, it depends on what you want. AFAIK your drive will be incapable of ripping the last track correctly; ie. with the proper offset. If that is important to you (it is to me, because I want to have bit-exact copies of my CD's) then you should replace the drive.

If it isn't, you can rip with offset 0 which should at least allow you to get all data off. However, AccurateRip? will not be useful since the offset is wrong for accurate rips.

[https://www.google.com/accounts/o8/id?id=aitoawntwypllofbqls0mnr2qbdctzzzz2ik7_g]

Well, I think I can change the bug status to invalid then as it's not a morituri issue.
You could probably catch those errors and display a meaningful error message but that's just cosmetics.

Thanks for your help! Will be back to morituri later with another drive.