search

brasslock / rubyripper

Automatically exported from code.google.com/p/rubyripper
1 stars 0 forks source link

ripper stops at 58.7% #406

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.any codec
2.rip to file or rip tracks
3.any number of matches, erroneous matches

What is the expected output? What do you see instead?
In the past I  have used RR to rip various cd's without incident. The
software stops everytime, on everydisc, on external or internal writers
with any codec 

1) What version of rubyripper are you using? On what operating system?
-> most current release as of today .deb (february 25, 2010)

2) Are you using the gtk2 or the commandline interface?
-> gtk2

3) Is the problem gone with the default settings? If so, please attach your
settings file ($HOME/.rubyripper/settings).
->It doesn't appear to be, but I included it as well.

4) Does the problem only happen on a specific disc? If so, please attach
the output of cdparanoia -Q. Also the freedb output would be nice if it may
be related to it.
-> All disks, even previously written, known good discs.

Please provide any additional information below.
This is frustrating as it is a great ripper that corrects for less than
perfect discs. I don't know what has happened. I have installed/uninstalled
RR via synaptic, apt-get and installed with a .deb from your site.

Original issue reported on code.google.com by Robert.L...@gmail.com on 25 Feb 2010 at 7:33

Attachments:

GoogleCodeExporter commented 9 years ago 
More info:
I am using Ubuntu 9.10 with the most current updates.

Here is the rip log for a disc that wouldn't rip beyond a certain track.

Original comment by Robert.L...@gmail.com on 26 Feb 2010 at 1:35

Attachments:

GoogleCodeExporter commented 9 years ago 
I found a RR that completed a known good cd. This cd did have problems that rr 
was
not able to resolve. However it dealt with it successfully. Log is included and 
is
named KWrr

RR is a great program. However I am not sure why this is labelled as an 
enhancement
when it is a bug.

Original comment by Robert.L...@gmail.com on 27 Feb 2010 at 12:20

Attachments:

GoogleCodeExporter commented 9 years ago 
You might find that updating to latest git solves your problem. Since last 
rubyripper 
release an important release of ruby has taken place which breaks some of the 
'old' 
syntax.

Original comment by boukewou...@gmail.com on 27 Feb 2010 at 2:21

GoogleCodeExporter commented 9 years ago 
I'm a bit confused. What would git have to do with RR failing?

Original comment by Robert.L...@gmail.com on 28 Feb 2010 at 7:47

GoogleCodeExporter commented 9 years ago 
See the git Wiki page to get latest & greatest code (which is managed by git).

Original comment by boukewou...@gmail.com on 24 Apr 2010 at 12:22

GoogleCodeExporter commented 9 years ago 
For now, updating to latest git should fix your problem. A real fix would be a 
new 
rubyripper release. This has to wait a little longer though, for I want to have 
the 
cuesheet thing ready by then without any known problems.

Original comment by boukewou...@gmail.com on 17 May 2010 at 9:43