GithubHelp home page GithubHelp logo

Comments (5)

GoogleCodeExporter avatar GoogleCodeExporter commented on May 28, 2024
Have you tried it at a later time too? It can be that your drive is a bit 
overheated which will prevent a good rip. Also test with different, difficult 
to 
rip cd's. I haven't changed anything in the Secure rip class as far as I know, 
so 
any bugs this serious are totally unexpected.

Original comment by [email protected] on 21 Nov 2006 at 5:41

from rubyripper.

GoogleCodeExporter avatar GoogleCodeExporter commented on May 28, 2024
Ja, I tried it way late at night when it was cold in here.  I'll try with 
another
disc... thought you had changed something in the code.

Original comment by [email protected] on 21 Nov 2006 at 6:42

from rubyripper.

GoogleCodeExporter avatar GoogleCodeExporter commented on May 28, 2024
Ooops, I did find one error. But this only explains why there aren't any errors 
excluded in trial nr. 4 I think. I had skipped the wave_out() function if the 
amount of matches needed was the same or higher as the amount of trials. But I 
shouldn't forget to read the positions of the erronous positions.....

Fix for that will be in next revision. Perhaps it helps with your cd too. But 
this 
bug doesn't explain that it never corrects the trials thereafter I'll upload my 
latest code now, but I don't have any time to test it. So please report if it 
helps 
or gets any crashes whatsoever :)

Original comment by [email protected] on 21 Nov 2006 at 6:55

from rubyripper.

GoogleCodeExporter avatar GoogleCodeExporter commented on May 28, 2024
Ahh, this bug report was not in vain then ;)  I tried ripping the disc again 
using 2
matches on a different drive.  After 57 trials it is still stuck with one chunk 
that
doesn't match.  So I think the disc is at fault.  Shame since the whole thing 
is fine
except for one small bit.  Can't even see any visible flaw on the disc.

Original comment by [email protected] on 22 Nov 2006 at 3:29

from rubyripper.

GoogleCodeExporter avatar GoogleCodeExporter commented on May 28, 2024
Well, you can always set the max_tries to a value of say 15. Even if it has 
errors 
left, it will continue with the encoding process. The chance you'll hear an 
error 
in 1 or 2 chunks isn't that big.

Some discs apparently can't be repaired completely. It would be nice to see how 
EAC 
handles this disc.

Original comment by [email protected] on 22 Nov 2006 at 9:13

  • Changed state: Fixed

from rubyripper.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.