http://bugzilla.novell.com/show_bug.cgi?id=561524 http://bugzilla.novell.com/show_bug.cgi?id=561524#c9 Tejun Heo <teheo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |DHWalker@ucdavis.edu --- Comment #9 from Tejun Heo <teheo@novell.com> 2009-12-13 06:05:50 UTC --- Oh, I thought there was cdparanoia for windows. For some reason, I recall using it on windows years ago but I might be just imagining things. CD recording and audio ripping don't have much to do with the rest of the system. All that OS and driver do is providing a communication channel between the optical drive and the application which performs the operation. The application is responsible for programming the device and performing the operations. In the end, when you're looking at two ripping programs resulting in different behavior, the best thing you can do would be dumping what command sequence each program is using and trying to find out what's causing the difference. I'm a driver guy and don't really have much clue about audio ripping. I think you probably have the best chance with bringing it up to the upstream projects. That said, while reading cdda2wav man page, two options seem like they could be relevant - -P and -n. Can you please try the followings? * Try different -n settings. The value the program is using by default is 55. Can you please try 128, 64, 32 and 16 and see if anything makes difference. * Try -P 0. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.