search

brasslock / rubyripper

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

All tracks option combined with single track unchecked = no rip #523

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
1) Please describe the steps to reproduce the situation:
a. Have "All Tracks" box checked 
b. Uncheck first track (I had track 1,2, 3 and 4 unchecked) 
c. Rip CD.

2) What is the expected output?
I expect it to start ripping from track 5 and forth. Why I had All Tracks 
checked is so that I didn't have to check each tracks boxes which saves time.

What do you see instead?
It just stays on ADVANCED TOC ANALYSIS and doesn't continue. At one one point 
it complained that it doesn't output WAV even though I have not chosen to 
output WAV.

3) What version of rubyripper are you using? On what operating system? The 
latest version of the gtk2 on Ubuntu 12.04 amd64.

4) Is this not already fixed with the latest & greatest code? See for
instructions the Source tab above.

I am no programmer so the source code says almost nada to me. Sorry.

5) Does the problem happen with all discs? If not, please attach
the output of cdparanoia -Q with a disc that gives trouble.

6) Please explain why this change is important for you. Also, how many
users would benefit from this change?

I guess a lot of users could scratch their head wondering why Rubyripper 
doesn't start ripping and not realizing what causes this.

7) Please provide any additional information below. The more usefull
information provided, the sooner the issue will be fixed.

When I uncheck All Tracks and just checked box by box until I have checked all 
tracks I want to rip it works just fine.

Note that ruby versions older than 1.9 are no longer supported. You are
advised to upgrade instead.

Original issue reported on code.google.com by icke...@gmail.com on 24 May 2012 at 4:48

GoogleCodeExporter commented 9 years ago 
The all tracks option is ignored when saving the tracks to rip. It's only there 
for convenience reasons. I can't reproduce the behaviour you described. An old 
ruby version would be a plausible explanation for this problem.

For now I close this issue, however I will reopen it if:
* you post your ruby version
* you start rubyripper from your terminal and post the final output.

Original comment by boukewou...@gmail.com on 31 Jul 2012 at 7:49