Re: Audio CDs on Titanium G4 Powerbook
Rob Pfile <Rob.Pfile@riverstonenet.com> writes:
> I dont know if anyone ever followed up to some questions in late
> april about how to get audio cd support working on the TiBook. I've
> done it, here's what i had to do:
Thanks!
> 2) you must pass the argument "hdc=scsi" to the kernel on boot to make
> the ide-scsi package sense the drive and install a driver for
> it. i'm not sure how it works if you've compiled ide-scsi as a module,
> maybe you can insmod it with this argument (?). if your
> dvdrom/cdrom shows up as a different hd (a,b,d, whatever; check
> dmesg), you need to use that name in the kernel argument.
Does anyone have a moment to explain exactly why this makes it work?
> 'eject' doesnt work anymore. to eject the disc, i need to use
> cdrecord: "sudo cdrecord dev=0,0,0 -eject" maybe if you adjust the
> permissions on someof the devices this will not need to be done as
> root.
Odd... wonder what causes this? Did you try strace'ing eject to see
what's up? Doesn't like the ioctl?
> there are endianness issues in general. you might have to experiment
> with the byte swapping features in cdparanoia, cdda2wav, lame,
> etc. related to this, audio cd reader 0.9 against xmms 1.2.3
> produces white noise, but the spectrum display is correct (!) i cant
> tell for sure where along the line the bytes are getting swapped;
> when cdrecord ejects the disk it seems to think the driver is
> swapping bytes. i hacked audio cd reader to swap the bytes it
> returns to xmms and that sounds OK. i think the right solution here
> is to convince the driver not to swap bytes, but i havent figured
> that out yet.
Be sure to file bugs!
> also, it appears that cdparanoia is not necessary for this drive,
> since it can apparently produce clean audio, which means that all of
> the 'paranoia' in cdparanoia is not needed. this would imply that
> cdda2wav is a fine choice for ripping, given that cdparanoia is such
> a resource hog. i was using cdda2wav until a couple of days ago when
> one of my CDs was producing mp3s of white noise. reading the source
> for cdda2wav, it looks like the endianness of the data coming off
> the drive is guessed by analyzing the data. apparently sometimes
> this fails. i dont see any ioctls() for the cdrom driver to swap
> bytes or to report the endianness, so i guess that might be the only
> way to tell.
File bugs;-)
Thankyou once again!
--
David N. Welton
Free Software: http://people.debian.org/~davidw/
Apache Tcl: http://tcl.apache.org/
Personal: http://www.efn.org/~davidw/
Work: http://www.innominate.com/
Reply to: