ripping a cd fails regularly

[Timo Aaltonen]

Binary package hint: sound-juicer

After upgrading to gutsy earlier this week, sound-juicer has become quite unpredictable when ripping cd's. A disc can fail to start ripping (it's trying to, but can't seem to get going), but after eject/reinsert the same disc rips fine. I'm not sure if it's a problem in some library instead of s-j itself..

Grip works every time, but I'd prefer s-j for it's musicbrainz-support.

[Timo Aaltonen (tjaalton)]

I've noticed that it's easier to reproduce if I waited some time (a minute or two) before hitting the ripping button.

[Sebastien Bacher (seb128)]

Thank you for your bug. What version of Ubuntu do you use? Do you have any error on the command line if you start it there?

[Pedro Villavicencio (pedro)]

Are you still getting the issue? Would be nice if you may test it with our development version the Gutsy Gibbon you may grab a CD Image from here: http://www.ubuntu.com/testing/ thanks in advance.

[Timo Aaltonen (tjaalton)]

Yes, I'm running gutsy. Unfortunately, I can reproduce it only on this one machine, not on my laptop or at work. I need to try running it as another user..

[Pedro Villavicencio (pedro)]

Still an issue? This is probably because there's something broken in your drive, i don't think this is a sound-juicer problem.

[Timo Aaltonen (tjaalton)]

It could well be the drive (I'll test another one soon), but it still puzzles me why grip or cdparanoia (the cmdline version) doesn't have the same issue..

[Timo Aaltonen (tjaalton)]

Yep, worked with an older LG GSA-4163B (this drive was GSA-4167B). Now, the strange thing is that why doesn't grip or cdparanoia (cmdline program) have any problems with ripping? Sound-juicer should use libcdparanoia in the end..

[Timo Aaltonen (tjaalton)]

a gstreamer problem perhaps?

[Sebastien Bacher (seb128)]

could be a gstreamer problem, without a debug log not easy to say though

[Timo Aaltonen (tjaalton)]

I'm happy to announce that this bug is fixed in hardy. Don't know what exactly fixed it.. I've upgraded my mobo&cpu, but the cdrom drive is the same, so I don't think that hardware had anything to do with it.

oh the bliss