Abort when futile option / heavily scratched cds

[TechVsLife]

When cds are heavily scratched, it's not uncommon to get to something like "re-Rip 700 frames," which takes forever to get through (ripping speed goes down to x2.3)--and it fails at the end anyway. True, the user can manually abort, but he needs to be watching. Why not have an option: abort if re-ripping more than x frames, where user selects the x. Has anyone encountered success when more than a dozen or so frames had to be re-ripped?

Or am I doing something wrong here? (or is there already an option)

p.s. is there a better solution for scratches than SkipDr.? Works well sometimes, but requires some work, and a few times it fails badly.

[LtData]

Re: Abort when futile option / heavily scratched cds

When I get the "Re-Rip x frames" that normally means that XP dropped the optical drive down to PIO mode, so I need to fix it and then reboot.

However, a "maximum re-rip" or "rip for no more than x minutes" option might be in order.

[TechVsLife]

Re: Abort when futile option / heavily scratched cds

When I get the "Re-Rip x frames" that normally means that XP dropped the optical drive down to PIO mode, so I need to fix it and then reboot.

Thanks. What do you mean by "fix it"? On my system, it immediately switches back to "normal" operation when it goes to a track without scratches (for example, the next track on the CD it is ripping); otherwise, on tracks with scratches, I almost always see the "Re-Rip x frames" messages. (Does "Re-rip X frames" mean something is wrong about my hardware configuration? I thought it was the usual result of trying to read from a scratched track.)

[Spoon]

Re: Abort when futile option / heavily scratched cds

CD Ripper >> Options >> Secure Settings >> Abort after x unrecoerable frames

[TechVsLife]

Re: Abort when futile option / heavily scratched cds

Thanks. Actually, that setting didn't do what I wanted (or perhaps I just need to reboot?). I set it to 20, but it still kept trying to re-rip 120 frames. (perhaps it means 20 failed frames after trying to re-rip all, instead of abort if need to re-rip more than 20 frames?)

The point is that it's extremely unlikely the rip will succeed when it has determined that a large number of frames would need to re-ripped, therefore I prefer it just skip trying to re-rip in a futile effort.

[Spoon]

Re: Abort when futile option / heavily scratched cds

It would stop re-ripping after 20 failed frames, or 20 unrecoverable frames, set it to 3 or 4.

[LtData]

Re: Abort when futile option / heavily scratched cds

By "fix it" I mean set my IDE controller back to DMA mode, normally done by uninstalling the secondary IDE controller then reinstalling it.

[TechVsLife]

Re: Abort when futile option / heavily scratched cds

It would stop re-ripping after 20 failed frames, or 20 unrecoverable frames, set it to 3 or 4.

ok, I see how that works now. Is there any reason not to set it to 1? i.e. I don't want any mistakes in the rip (in the music), so if it already has one error that it can't correct, then why not stop it there? (I assume it has already re-tried on that frame as many times as you've set it to retry (on the other setting, "max re-reads," and given up.)

By "fix it" I mean set my IDE controller back to DMA mode, normally done by uninstalling the secondary IDE controller then reinstalling it.

Thanks it was already in DMA mode.

[TechVsLife]

Re: Abort when futile option / heavily scratched cds

I have one unexpected behavior now, probably because of my misunderstanding. I set "abort after unrecoverable frames" to 1, but now what happens is that, for example, after starting to re-rip 1000 frames, it will stop after about frame 200, (it aborted the re-rip), presumably because it has detected an unrecoverable frame. But it will then mark the track as secure (with an "i," not a check). I wanted it to fail, mark as unsecure--since it is. i.e. I thought abort would abort the whole track, but instead it aborts only the re-rip and marks it as secure.

ok, I see how that works now. Is there any reason not to set it to 1? i.e. I don't want any mistakes in the rip (in the music), so if it already has one error that it can't correct, then why not stop it there? (I assume it has already re-tried on that frame as many times as you've set it to retry (on the other setting, "max re-reads," and given up.)

[Spoon]

Re: Abort when futile option / heavily scratched cds

There is the option to mark track as error if unsecure, but I think you have found a bug (with the 1 unrecoverable frame, not marking it as insecure). Anyhow bug noted.

[TechVsLife]

Re: Abort when futile option / heavily scratched cds

Thanks. I did have that option selected, to mark track as error if unsecure. It still passes it as "SECURE" (with the "i" icon, not a checkmark).

(This seems to be a major bug, if the main point is to make a secure recording, then it shouldn't mark an obviously bad track as secure after the user says mark track as bad if not secure.)

***The problem does not appear after changing 1 to 5 ("abort after unrecoverable frames").

There is the option to mark track as error if unsecure, but I think you have found a bug (with the 1 unrecoverable frame, not marking it as insecure). Anyhow bug noted.

[Spoon]

Re: Abort when futile option / heavily scratched cds

setting 2 should not have the problem.

[TechVsLife]

Re: Abort when futile option / heavily scratched cds

thanks.