Where's the beef? Looking for info on a failed rip

[GoogleCodeExporter]

1) Please describe the steps to reproduce the situation:
a.insert cd
b.Start Ripper
c.try to rip problem giving track.

2) What is the expected output? What do you see instead?  The problem is that 
ripper shuts down seemingly in the middle of the 3rd trial.  It takes about 3 
or so minutes to get to that point each time then shuts down.

3) What version of rubyripper are you using? On what operating system? The
gtk2 of commandline interface? RR 0.6.1 on Ubuntu 10.10 updated from 10.04.  
GTK2 updated about 3 weeks ago from this post.

4) Is this not already fixed with the latest & greatest code? See for
instructions the Source tab above.  Using the latest greatest already.  I just 
don't understand why there is a log if there isn't anything useful in it.

5) Does the problem happen with all discs? If not, please attach
the output of cdparanoia -Q with a disc that gives trouble.  using the Q flag 
ruby just flashes back and forth at about 2Hz between an info message 
"cdparanoia doesn't output to wav files" or some such, and what i assume is the 
normal interface whilst selecting files to be ripped.  I'm ripping to .mp3 by 
the way.  Everything else works normally.

6) Please explain why this change is important for you. Also, how many
users would benefit from this change?  I'm not asking for a change so much as 
an explanation.  The program works fine as far as I can tell, just wanted a 
little more info if possible about that particular track.

Please provide any additional information below. The more usefull
information provided, the sooner the issue will be fixed.  Just looking for a 
more verbose log output.

Original issue reported on code.google.com by babygeni...@gmail.com on 16 Oct 2011 at 12:55

• Blocking: #556

Attachments:

• ripping.log

[GoogleCodeExporter]

This isn't very important, but you folks may want to look into it.  If I don't 
get any response I'll just count my blessings that this works as well as it 
does.

Original comment by babygeni...@gmail.com on 16 Oct 2011 at 12:57

[GoogleCodeExporter]

If you use the -Q option when ripping, then cdparanoia does the following: 
autosense drive, query disc and quit. That is according to cdparanoia --help. 
And it results no wav that is outputted, so this seems to be correctly detected.

I don't know why you pass this option. But I suggest removing it and giving it 
another spin.

Original comment by boukewou...@gmail.com on 16 Oct 2011 at 1:54

[GoogleCodeExporter]

I did that (pass -Q) because in the #5 thing to do it instructs me to.  If I 
don't do it then ripper eventually just shuts down not continuing beyond the 
problem track.  To be clear-When I do pass the flag nothing gets better.  I 
have to force the program to quit.  I only did it because it was a general 
suggestion in the submission format.  I just skip the problem track.  It isn't 
that good anyway.;

Original comment by babygeni...@gmail.com on 16 Oct 2011 at 7:47

[GoogleCodeExporter]

The -Q thing is not supposed to be passed in rubyripper itself. You should post 
the output of cdparanoia -Q when running this exact command in a terminal.

Anyway, the logfile is useless this way. So please upload the logfile when the 
passing parameters are empty.

Original comment by boukewou...@gmail.com on 16 Oct 2011 at 9:34

[GoogleCodeExporter]

There is no log file to speak of.  It just hangs.  Sorry.

Original comment by babygeni...@gmail.com on 17 Oct 2011 at 2:07

[GoogleCodeExporter]

Well, at least show the output when running rubyripper from a terminal 
(rubyripper_gtk2). By the way, it's not likely there is no log file, since it's 
already partly created before the ripping part.

If you can't provide any additional info I'll have to close this issue.

Original comment by boukewou...@gmail.com on 17 Oct 2011 at 5:04

[GoogleCodeExporter]

There really isn't anything useful in the log file. It reports no useful 
information as the program gets hung up as soon as it begins the track. The log 
file with the q flag at least prints out that it jeeps failing the test. Ilk 
let it reach 17 tries before I shit it down forcefully.  If th here were any 
thing more to provide than what I already have, I would gladly do so. I'm sure 
that my disc has something freaky with it. To be clear the program performed 
above av nd beyond. I'm very happy. I was just wondering if there was away to 
get a little more info out if the program about the bad track. I suppose that 
will come down the road. Thank you for your attention.

Original comment by babygeni...@gmail.com on 17 Oct 2011 at 9:34

[GoogleCodeExporter]

Original comment by boukewou...@gmail.com on 9 Jan 2013 at 10:51

• Now blocking: #556