illustrate
Products            Buy            Support Forum            Registrations            Professional            About           
 

Re Rip frame Errors

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • mville
    replied
    Re: Re Rip frame Errors

    Originally posted by selkov
    Ok so I let it run until it finished. It completed the rip but states insecure. Do I trust that to be as good as it gets or should I re-rip it in burst mode?
    There's no should about it. It really is up to you.

    I see no reason why you couldn't try all ripping methods, burst, secure and defective by design.

    Leave a comment:


  • selkov
    replied
    Re: Re Rip frame Errors

    Ok so I let it run until it finished. It completed the rip but states insecure. Do I trust that to be as good as it gets or should I re-rip it in burst mode?

    Leave a comment:


  • mville
    replied
    Re: Re Rip frame Errors

    Originally posted by selkov
    But that does not answer me. Should I wait for it to try or go to burst mode?
    It is not possible to know the answer prior to ripping as it is the ripping process that highlights any problems with a CD.

    Why not wait to see if CDRipper can recover from the frame errors and if not, you can try burst mode after. If you can't wait, don't and just try burst mode.

    However, a defective CD is defective whatever you do.
    Last edited by mville; August 16, 2015, 02:28 PM.

    Leave a comment:


  • selkov
    replied
    Re: Re Rip frame Errors

    But that does not answer me. Should I wait for it to try or go to burst mode?

    Leave a comment:


  • Spoon
    replied
    Re: Re Rip frame Errors

    For some discs it is not possible to recover from the ripping errors.

    Leave a comment:


  • selkov
    started a topic Re Rip frame Errors

    Re Rip frame Errors

    I have several discs that give me this error. I see on the forum that the solution is to remove c2 pointers.
    But if i have the time to wait am i better off waiting for the FRAMES to record instead?
Working...