Hi Joe, Jake Moe wrote:
> On 01/13/11 20:48, J. Roeleveld wrote: >> On Thursday 13 January 2011 11:33:09 Jake Moe wrote: >>> On 01/13/11 18:12, J. Roeleveld wrote: [snip] >> Can you actually play that wav-file? Or is it just a collection of >> garbage? >> >> As far as I know, CD-Paranoia access the cd-drive a bit more directly >> then other tools. Eg. it approaches it like a CD-ROM, rather then >> CD-Audio. >> >> The error messages appear as soon as you put the CD into the drive? >> Am wondering if some auto-mounting tool is trying to access it and is >> causing problems here. >> Do you also get those messages when you disable all KDE/Gnome/X/... and >> related stuff? >> >> Personally, I tend to use cdparanoia and other tools to generate OGG or >> MP3 files and store them on a fileserver and play them from there. >> >> -- >> Joost >> > Yeah, the wav file played fine. At least, it started out fine; I only > listened to the first 15 - 30 seconds to make sure it sounded ok, and > then assumed the rest was fine, since nothing else had even gotten that > far. > > And yeah, the errors start as soon as I put the CD in the drive. What > automounting tool might I have in FVWM? I use a pretty basic config > (which is why I like FVWM, not many frills to muck things up :-P). My situation improved a bit after upgrading to the latest udev available. With 164-r1 I don't have these errors in the log anymore. Unfortunately when I try to rip the CD with KDE stuff, the process slows still down until it aborts. However, the situation improved with the CLI tools (even running from with KDE). Cdda2Wav takes now 2,5 mins for a 45min CD, cdparanoia takes nearly twice, but succeeds also. After reconfiguring abcde to take cdda2wav I can at least rip CDs into MP3s in a quite normal time. - Jörg
