View previous topic :: View next topic |
Author |
Message |
Drone1 Apprentice
Joined: 27 Sep 2005 Posts: 232 Location: United States of Texas
|
Posted: Sun Apr 02, 2006 8:57 pm Post subject: Audio CD rip SLOW! |
|
|
After searching these forums, checking available packages and package settings, cdrom settings, and pulling a few hairs out, I am posting.
I am unable to rip audio cd's at any convenient speed.
I have a:
P3 750, 512MB RAM, 20GB HD, CD-ROM F564E (52X speed) running the 2.6.13 gentoo kenel.
I have tried the following programs to rip an audio cd to mp3. (I'm using mp3's for my rio mp3 player)
abcde, ripperX, konqueror audiocd:, kaudiocreator, and a few other command tools that escape me right now.
ALL are EXTREMELY SLOW, and are clearly not working properly. In the case of konqueror audiocd:, which is running as I type, will transfer at anywhere from 1.0 Kb/s to 240 Kb/s and stall for random amounts of time at random intrevals. This behavior happens for any and all ripping/encoding programs I try. This 1 file will likely take the order of 2~ HOURS . UNACCEPTABLE!!!!
I have covered my bases ( I think) w/ cdparanoia, lame, cdrom dma settings (both enabled and not, no difference)....
top shows kio_audiocd peaking at 30% cpu usage. I am fairly sure its not the drive, because i can browse backed up data cd's without problem or speed.
I am at witts end here and will gladly accept any suggestions presented. |
|
Back to top |
|
|
kfiaciarka Veteran
Joined: 20 May 2005 Posts: 1498 Location: Dobre Miasto, Poland
|
Posted: Sun Apr 02, 2006 9:06 pm Post subject: |
|
|
Try using cdda2wav instead and see the diffrence. Also you may try cdmp3 - a commnad line ripper There was cdparanoia ebuild on bugzilla but for me it don't work:( I preffer cdda2wav It's faster. |
|
Back to top |
|
|
FormerSlacker Guru
Joined: 11 Mar 2003 Posts: 340 Location: Toronto, ON. Canada
|
Posted: Mon Apr 03, 2006 4:46 am Post subject: |
|
|
The Konqueror AudioCD kioslave works wonderfully, but it is way too slow for me. Grip works great though. |
|
Back to top |
|
|
Drone1 Apprentice
Joined: 27 Sep 2005 Posts: 232 Location: United States of Texas
|
Posted: Mon Apr 03, 2006 5:23 am Post subject: |
|
|
I went ahead and emerged cdmp3 and dl'ed the source for cdda2wav.
I could never get cdda2wav to finish 'Make'. Gave me a bunch of
Code: |
"/usr/src/linux/include/linux/****:##: warning: traditional C rejects ISO C style function definitions"
|
errors on various compiler files (?).
cdmp3 emerged fine and started to process the audio cd , but after letting it sit there for 2 hours, it never completed 1 file, and I ended killing the process.
The pattern that is being shown here isn't applicatin specific. Its system specific. I need to figure out 'what isn't working'!!!!
At this point I am not going to install any more applications as I don't see that helping.
How do I begin to track down what the 'REAL' issue is here??? |
|
Back to top |
|
|
BitJam Advocate
Joined: 12 Aug 2003 Posts: 2508 Location: Silver City, NM
|
Posted: Mon Apr 03, 2006 7:16 am Post subject: |
|
|
Use cdparanoia. I use a Perl program called "rip" (it's in portage) that is a convenient wrapper for cdparanoia and various encoders. If you use the -v option for rip, you will get a verbose output from cdparanoia that might give you a good idea if there are problems ripping cd's on your drive.
I have 2 cd drives. One of them takes just about forever to rip (literally hours) and some cd's would never finish. The cdparanoia output for this drive showed a multitude of problems and errors. There were always problems ripping with this drive, it never worked right.
I've got another cd drive and it rips just fine. The verbose cdparanoia output consistently shows no errors or problems.
IMO, if cdparanoia is having problems ripping cds on your cd drive, the only real solution is to get an different drive. |
|
Back to top |
|
|
kfiaciarka Veteran
Joined: 20 May 2005 Posts: 1498 Location: Dobre Miasto, Poland
|
Posted: Mon Apr 03, 2006 10:08 am Post subject: |
|
|
Cdda2wav is a part of cdrtools:)
Code: |
equery belongs cdda2wav
[ Searching for file(s) cdda2wav in *... ]
app-cdr/cdrtools-2.01-r3 (/usr/bin/cdda2wav)
|
|
|
Back to top |
|
|
Drone1 Apprentice
Joined: 27 Sep 2005 Posts: 232 Location: United States of Texas
|
Posted: Mon Apr 03, 2006 1:51 pm Post subject: |
|
|
Quote: |
kfiacarka,
Cdda2wav is a part of cdrtools:) |
Yes, I am well aware of that as it was obvious during the emerge!
BitJam,
At this point I'm thinking its the drive or the kernel, and leaning more towards the drive, as I was able to rip audio on a former drive some 3-4 months back. I haven't upgraded the kernel since then, so it would suggest the drive.
In that event, is there any way to test the drive to see if has I/O issues or just confirm the damn drive can function as I'm wanting?? Possibly 'cat' out a cd to .iso or something ??? Suggestions welcome ..... |
|
Back to top |
|
|
BitJam Advocate
Joined: 12 Aug 2003 Posts: 2508 Location: Silver City, NM
|
Posted: Mon Apr 03, 2006 5:34 pm Post subject: |
|
|
Use cdparanoia as I suggested above. IMO, that is the best way to check your drive. The docs on their web site are quite good. If you still don't believe me, read their FAQ.
There are non-trivial technical hurdles to reading a cd correctly. It is not nearly so easy as doing a "cat" or a "dd". The cdparanoia FAQ does a good job of explaining all of this. |
|
Back to top |
|
|
Cintra Advocate
Joined: 03 Apr 2004 Posts: 2111 Location: Norway
|
Posted: Mon Apr 03, 2006 5:39 pm Post subject: |
|
|
Might be an idea to check your disk with 'hdparm -tT /dev/hdx'.. _________________ "I am not bound to please thee with my answers" W.S. |
|
Back to top |
|
|
Drone1 Apprentice
Joined: 27 Sep 2005 Posts: 232 Location: United States of Texas
|
Posted: Wed Apr 05, 2006 3:40 am Post subject: |
|
|
This first hdparm can't be good.
Code: |
etc # hdparm -tT /dev/hdb
/dev/hdb:
read() failed: Input/output error
Timing buffered disk reads: read() failed: Input/output error
etc #
|
Here is a little more info on the drive.
Code: |
etc # hdparm -iIC /dev/hdb
/dev/hdb:
drive state is: active/idle
Model=OEM CD-ROM F564E, FwRev=1.15, SerialNo=
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no
* signifies the current active mode
ATAPI CD-ROM, with removable media
Model Number: OEM CD-ROM F564E
Serial Number:
Firmware Revision: 1.15
Standards:
Used: ATAPI for CD-ROMs, SFF-8020i, r2.5
Supported: CD-ROM ATAPI-2
Configuration:
DRQ response: 50us.
Packet size: 12 bytes
Capabilities:
LBA, IORDY(can be disabled)
DMA: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=227ns IORDY flow control=120ns
etc # cat /proc/ide/hdb/settings
name value min max mode
---- ----- --- --- ----
current_speed 66 0 70 rw
dsc_overlap 1 0 1 rw
init_speed 66 0 70 rw
io_32bit 0 0 3 rw
keepsettings 0 0 1 rw
nice1 1 0 1 rw
number 1 0 3 rw
pio_mode write-only 0 255 w
unmaskirq 0 0 1 rw
using_dma 1 0 1 rw
etc #
|
Although I'd like to solve this, I'm just about ready to toss it and put in another rom. |
|
Back to top |
|
|
BitJam Advocate
Joined: 12 Aug 2003 Posts: 2508 Location: Silver City, NM
|
Posted: Wed Apr 05, 2006 3:59 am Post subject: |
|
|
Drone1 wrote: | This first hdparm can't be good.
Code: |
etc # hdparm -tT /dev/hdb
/dev/hdb:
read() failed: Input/output error
Timing buffered disk reads: read() failed: Input/output error
etc #
|
|
I get that same output from that command on both my cdrom drives with and without an audio cd inserted. One of the drives rips just fine. |
|
Back to top |
|
|
micmac l33t
Joined: 28 Nov 2003 Posts: 996
|
Posted: Thu Apr 06, 2006 3:22 am Post subject: |
|
|
Try the -r3 ebuild of cdparanoia (currently still masked ~x86). It should work better. You need a kernel >= 2.6.15 for the patches to be applied. |
|
Back to top |
|
|
|