Re: Preventing Secure Rip Aborts
Right, but dbpoweramp guide recommends setting the Secure rip to abort after 1 unrecoverable frame, 100 re-rips, or 10 minutes of rip time. Even after changing those options to 'no abort' it still aborts the rip and deletes the file.
I guess I am concerned that I am not getting as good a quality rips as I do with EAC. EAC will spend a lot of time doing error correction and only reports a few bad areas on tracks afterward. I guess this can be interpreted as EAC letting more errors through or it is better at error correction.
I may be left with unpleasant option of having to re-rip damaged tracks with EAC.
-
Re: Preventing Secure Rip Aborts
The secure rip should never abort unless you set an 'Abort After' option on the secure page.Leave a comment:
-
Re: Preventing Secure Rip Aborts
To clarify:
I want dbpoweramp to give me the best quality rip possible from damaged disks without aborting and deleting the entire rip. I would prefer to have the software do it's best job and then let me decide if the track is okay by listening to the portions that have errors. What options do I need to set in order to do this?Leave a comment:
-
Preventing Secure Rip Aborts
I have been using EAC and it would rip damaged tracks and report the errors instead of aborting. I could then listen to the suspicious portions to listen for artifacts. 99% of the time there were no audible problems so I could just ignore it.
I have Secure rip enabled and would like dbpoweramp to rip damaged tracks instead of just aborting. Dbpoweramp will just abort the rip and I get nothing. How do I get dbpoweramp to behave like EAC on damaged disks?
Leave a comment: