Closed GoogleCodeExporter closed 9 years ago
Did you try different CDs and tried the same CDs for both versions?
Did you check that you have the correct CD drive listed in the settings shown?
I also have a disc where rubyripper just exits, but other CDs work fine.
(It is a disc with some very weird copy protection, which doesn't work with
cdparanoia anyways)
Original comment by goo...@JonnyJD.net
on 26 Nov 2009 at 6:44
I tried only a disc, but please read that I wrote that rubyripper version 0.5.5
does
not have any single problem ripping it; that's the reason why I didn't tested
other
discs.
The rip with the 0.5.5 version of ruby ripper worked perfectly; and I listened
to it
just today from the beginning to the end.
I have the feel that it's just a matter of user interface.
Uhm, idea. Is it possible that RR 0.5.7, founding a config file of 0.5.5 does
some
mess with it and thus behave in an unpredictable way?
Original comment by spe...@gmail.com
on 26 Nov 2009 at 6:49
I am getting this problem with 5.7 as well, although I can rip the disc just
fine with
the GUI.
The cli just says that it can't find any cddb info about the cd, asks if i want
to
change configuration settings, then exits.
Original comment by execra...@gmail.com
on 6 Dec 2009 at 8:27
I have tried multiple discs. on each disc it DOES find the CD info. everything
proceeds normally until the ripping. it gets to "expected file size for track
1 is
...." then the program exits. the drive is never accessed / spun up.
a directory has been created for the rip. an m3u playlist and a logfile is in
that
directory. the logfile ends at the word "STATUS" after the list of tracks.
in my case rubyripper was set to rip to flac.
Original comment by galtthed...@gmail.com
on 13 Jan 2010 at 5:31
My experience is exactly the same as galtthedestroyer's. The gui works fine,
the cli
does exactly as s/he described.
Original comment by eightmillion
on 23 Jan 2010 at 10:30
Can anyone reproduce this behaviour with latest git? See the wiki for
instructions.
Original comment by boukewou...@gmail.com
on 6 Feb 2010 at 11:42
My experience also the same than galtthedestroyer.
Both the 0.5.6 and the 0.5.7 releases have this issue.
The 0.5.5 works perfectly fine, though.
Original comment by sebastie...@ulaval.ca
on 27 Feb 2010 at 6:44
I can't reproduce this with latest code, I suppose it's fixed then. If anyone
can
reproduce this with latest git, feel free to request it to be reopened.
Original comment by boukewou...@gmail.com
on 24 Apr 2010 at 6:31
Original issue reported on code.google.com by
spe...@gmail.com
on 26 Nov 2009 at 2:28