Q: What is the "(frame LBA x ripping 26 frames track end LBA y)" error?

[Porcus]

The below pasted error shows sometimes up on scratched CDs, and it seems to always be 26 frames. The ripper seems to abort during or at the end of an Ultra Secure pass -- I have not seen it occurring during Pass 1 or Pass 2 or during frame re-rip.

Sometimes it helps just giving it another attempt, sometimes it doesn't.


Versions: R13, "all betas I have tried" (including the current)
Drive: PX-230A. Edit: It sometimes makes ugly noises when this happens -- could it be worn out?


===


Track 1: ERROR Ripping LBA 32 to 22692 (5:02) in 2:17. Filename: g:\rerip\Ministry [1989] ~ The Mind Is a Terrible Thing to Taste ~ 6D0BCB09\Ministry [1989] ~ The Mind Is a Terrible Thing to Taste ~ 01 ~ Thieves.flac
Unable to read CD, check CD disc (frame LBA 2373 ripping 26 frames track end LBA 22692)

Track 2: ERROR Ripping LBA 22692 to 46705 (5:20) in 2:18. Filename: g:\rerip\Ministry [1989] ~ The Mind Is a Terrible Thing to Taste ~ 6D0BCB09\Ministry [1989] ~ The Mind Is a Terrible Thing to Taste ~ 02 ~ Burning Inside.flac
Unable to read CD, check CD disc (frame LBA 22979 ripping 26 frames track end LBA 46705)

[Spoon]

Re: Q: What is the "(frame LBA x ripping 26 frames track end LBA y)" error?

It means the CD is unreadable.

[bhoar]

Re: Q: What is the "(frame LBA x ripping 26 frames track end LBA y)" error?

It means the CD is unreadable.

Spoon - would a more precise answer be something along the lines of:

"the amount of continuous error data encountered is so large that the drive is unable to retain synchronization while reading and so the drive reports a serious failure and aborts the command"?

-brendan

[Porcus]

Re: Q: What is the "(frame LBA x ripping 26 frames track end LBA y)" error?

Well, it works in burst mode, so ...?

And why the "26"?

Edit: My laptops internal drive seems to support C2, so I tried.

Track 1 aborts with
** Reached Maximum 1 Unrecoverable Frames For This Track
Re-rip Frame: 14862 (00:03:17,720)

... OK, an unrecoverable frame, I can live with that -- but this one at least manages to start ripping individual frames!


while track 2 goes through as "Secure" with the following re-read frames:
Re-rip Frame: 26192 (00:00:46,653) matched 10 / 14 (c2 dropped 1)
Re-rip Frame: 26202 (00:00:46,786) matched 10 / 14 (c2 dropped 3)
Re-rip Frame: 26222 (00:00:47,053) matched 10 / 14 (c2 dropped 17)
Re-rip Frame: 26241 (00:00:47,306) matched 10 / 13
Re-rip Frame: 26242 (00:00:47,320) matched 10 / 14 (c2 dropped 11)
Re-rip Frame: 26252 (00:00:47,453) matched 10 / 14 (c2 dropped 13)
Re-rip Frame: 26271 (00:00:47,706) matched 10 / 14 (c2 dropped 76)
Re-rip Frame: 26281 (00:00:47,840) matched 10 / 14 (c2 dropped 4)
Re-rip Frame: 26282 (00:00:47,853) matched 10 / 14 (c2 dropped 1)
Re-rip Frame: 26291 (00:00:47,973) matched 10 / 14
Re-rip Frame: 26292 (00:00:47,986) matched 10 / 14 (c2 dropped 2)

... but different CRC each time. So 10 of 14 with many dropped CRCs is insufficient for a secure rip?

[Spoon]

Re: Q: What is the "(frame LBA x ripping 26 frames track end LBA y)" error?

We rip 26 frames at a time. In burst you could be lucky that the drive is reading the bad frame at a different location within the 26.

[Porcus]

Re: Q: What is the "(frame LBA x ripping 26 frames track end LBA y)" error?

Edit: It sometimes makes ugly noises when this happens -- could it be worn out?

#¤%@#¤%&§§ !!!!!

Oh well, compared to bhoar's issue in http://forum.dbpoweramp.com/showthread.php?t=16917 ...

[Porcus]

Re: Q: What is the "(frame LBA x ripping 26 frames track end LBA y)" error?

I am necromancing an old thread here, and this is probably a wishlist item.


Where there is one grave error, there are usually more errors, and burst ripping the entire track does nothing to correct these. For best possible result, I would wish dBpoweramp to -- at least have an option to --

- Ultra-Secure rip all frames which can be read,
and for frames where this is impossible:
- burst read (at least as long as I have not set dBpoweramp to use its own interpolation),
and if so:
- report in log as 'Error' and add e.g. 'Audible errors likely. xx frames interpolated by drive' (or 'by dBpoweramp', if this interpolation is chosen by user)


I assume this requires less coding than changing the 26-frames-at-the-time, or does ultra-secure read one frame at the time, so that it could be an option to actually try to ignore the error for as long as possible?