Anyone have a clue why my CD is so slow?

[Jenda]

My CD drive is incredibly slow. When I try to extract a CD using GnomeBaker, it takes from 40 to 120 minutes. Burning is quite normal. Soundjuicer tells me the extraction speed starts at 3x, later dropping even lower than 1x.
DMA is on, if you ask. It is a 46x (or so) Liteon DVD-R drive.

Any ideas?

[Jenda]

Oh, and two more things:
1.
Ubuntu 5.04
2.
I didn't feel like making a new thread for this: I downloaded most of the multimedia codecs, but since I'll have broadband soon I thought I'd wait with the biggest ones. Can anyone tell me what exactly w32codecs, ffmpeg and mjpegtools are for?

Thanks,
Jenda

[adiment]

maybe the drive is slowly starting to go? Unless it's the OS's problem? Maybe try a firmware update...

[Aloone_Jonez]

Is this a Mac or is it an x86?

Perhapps it's the driver, does it perform as expected under Mac OS, or Windows?

[WMD]

GnomeBaker is probably using libcdparanoia with all the error checking turned on.  Don't know how you would change this in that program.  K3B makes it pretty easy to do so.

[KernelPanic]

Your ripping backend will be cdparanoia, you will get faster results with cdda2wav but lose error checking and jitter correction and stuff.
To be fair, Lite-on drives tend to be pretty shit hot at DAE so you may do well with cdda2wav.

Try the program grip as it allows you to play with settings and backends until you are happy.

Also, before someone comes and says, "My Windows boxen rip CDs at One-Million times". Fuck you!
A fair comparison between Windows and Linux ripping is between EAC and cdparanoia respectively.

Additionally you may need to set the correct read speed for your drive;
man hdparm
man eject

[mobrien_12]

What if you use a command line tool like cdparanoia?

Is still so slow?

[Jenda]

Is this a Mac or is it an x86?

OK... I use a pentium IV.

Maybe try a firmware update...

How would I do that?

Perhapps it's the driver, does it perform as expected under Mac OS, or Windows?

I would say it preformed fine under win98

Lite-on drives tend to be pretty shit hot at DAE so you may do well with cdda2wav.

Do you think I should use my other drive, Sony CD-R, instead? It seems to me to be just as slow.

Now Goobox seems to be capable of ripping the CDs quite decently (10 minutes on the Sony for 43 minutes of music), but it sometimes stops for no apparent reason just at the beginning of a track. I managed to rip a  whole CD except for two tracks in less than 20 min. (on the Lite-on) and then the remaining two in Sound Juicer in about four minutes. But this is just nonsense. I will try cdparanoia tomorrow, it's getting late now. Just skimming through the text the terminal spat out after typing cdparanoia: wtf are little endians and big endians doing there??? Aren't they the t  
wo lilliputan nations from "Gulliver's Travels"?

-c --force-cdrom-little-endian  : force treating drive as little endian
  -C --force-cdrom-big-endian     : force treating drive as big endian

Thanks for all your suggestions

[onsecondthought=decidedtotryoutcdparanoia]And can I make cdparanoia extract to oggs?[/onsecondthought]

[KernelPanic]

paranoia will extract to WAV. You use oggenc to go to Vorbis.
Or just use grip to automate the whole process and write ID3 tags.

Aside:
1) When I said 'shit hot' I meant very good.
2) Many Sony drives are Liteon drives internally, just more expensive...

[KernelPanic]

wtf are little endians and big endians doing there??? Aren't they the t  
wo lilliputan nations from "Gulliver's Travels"?

Yes, aren't hackers funny?

Just replace the eggs with numbers and it makes sense.
little endian = least significant bit first
big endian = most significant bit first

Little endian rules the roost in x86 land and a standard MS PCM WAV is little endian too.

[Jenda]

Funny bastards...
KernelPanic@microsuck:-$ oggenc
(processing)                                             [fail]
error: wrong number of arguments
needed: "how to transform more files at the same time?"
needed: "how to specify output filenames?"
someone@microsuck:-$ _

[KernelPanic]

Oggenc works on one file at a time and automatically uses the same filename:

$ oggenc -q 7 Jazz.wav

Would create the file Jazz.wav.ogg at Vorbis quality 7.

To perform the same action on all of your WAV files in a directory you would use a shell script.
eg:

Code: [Select]


#!/bin/bash
# wav2ogg
for i in *.wav
do
oggenc -q 7 $i
done

Again, since you don't appear to have checked the manpage of oggenc, I suggest you try grip for future endeavors.
RTFM, don't expect handholding.

[WMD]

Quality 7?  Jeez...isn't quality 5 128kbps?  With OGG's quality, that should be enough.

[WMD]

Quality 7?  Jeez...isn't quality 5 128kbps?  With OGG's quality, that should be enough.

No, quality 5 is 88kbps, quality 7 is 121.  Check your facts first!

[Jenda]

No, quality 5 is 88kbps, quality 7 is 121.  Check your facts first!

 Huh...

Oggenc works on one file at a time and automatically uses the same filename:

$ oggenc -q 7 Jazz.wav

Would create the file Jazz.wav.ogg at Vorbis quality 7.

To perform the same action on all of your WAV files in a directory you would use a shell script.
eg:
Code:

#!/bin/bash # wav2ogg for i in *.wav do oggenc -q 7 $i done

Ok. Thanks a bunch, KernelPanic.

Now just for the record, is the manpage what comes up when you type

Code: [Select]

oggenc --help