exception caused by missing file because of 0 seconds trial

[GoogleCodeExporter]

Here's the backtrace:
/usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1947:in `initialize': No such file or 
directory - /.../temp_sr0/track2_1.wav (Errno::ENOENT)
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1947:in `new'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1947:in `block in analyzeFiles'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1946:in `times'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1946:in `analyzeFiles'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1865:in `main'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1824:in `ripTrack'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1796:in `block in ripTracks'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1792:in `each'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1792:in `ripTracks'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:1786:in `initialize'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:2489:in `new'
    from /usr/lib64/ruby/site_ruby/1.9.1/rr_lib.rb:2489:in `startRip'
    from /usr/bin/rrip_gui:305:in `block in do_rip'

And that's the part from ripping.log:
Rippen des Tracks 2 gestartet, Versuch #1 (0 Sekunden)
Rippen des Tracks 2 gestartet, Versuch #2 (47 Sekunden)
Rippen des Tracks 2 gestartet, Versuch #3 (39 Sekunden)
Analysiere Datei auf nicht übereinstimmende Teilstücke

And that's the responsible part of the code:
files = Array.new
@reqMatchesAll.times do |time|
    files << File.new(@settings['Out'].getTempFile(track, time + 1), 'r')
end

Somehow I suddenly keep getting this problem fairly often but irregularly.

Probably there should be a check beforehand whether the file for that pass 
exists or otherwise the exception should be caught. I'm not familiar with ruby 
so I can't create a patch. But it should be fairly trivial.

Original issue reported on code.google.com by futur.a...@googlemail.com on 11 Sep 2011 at 6:32

• Blocking: #556

[GoogleCodeExporter]

It seems like the first trial fails. The real question however is, why does it 
fail? Do you pass any exotic parameters to cdparanoia? Does it also happen with 
default settings?

Original comment by boukewou...@gmail.com on 17 Oct 2011 at 7:37

[GoogleCodeExporter]

No, afaik I don't. Here are my settings just in case:
http://pastebin.com/jJYcFZHj

Original comment by futur.a...@googlemail.com on 17 Oct 2011 at 8:46

[GoogleCodeExporter]

Strange indeed, your configuration for cdparanoia should not be a problem.

Two questions though:
* There isn't any info in the terminal after printing the cdparanoia command?
* Perhaps the directory temp_sr0 isn't removed properly? Can you still 
reproduce the problem if cleaning this directory manually?

Original comment by boukewou...@gmail.com on 26 Oct 2011 at 7:59

[GoogleCodeExporter]

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

• Now blocking: #556