Audio CDs ripping
 

I have the lame decoder/encoder installed in /usr/bin/lame. I installed normalize too. It's in /usr/bin/normalize.

When i open the configuration menu of k3b it shows me that k3b found the normalize, but the lame doesn't appear in any line of the configuration list. And k3b cannot rip wav CD to MP3 files.

Is there a way of force k3b to find lame? the tcdecode program name line shows "not found"

Another trouble: KAudio Creator doesn't see /dev/cdrom or /mnt/cdrom nor /dev/cdrom2 or /mnt/cdrom2. Is there a way of force it to "see" the CD units? In some moment two days agor it saw the /dev/cdrom2. Suddenly it doesn't "see" the CD units.

Why will I live without rip CDs?


Greetings from Sao Paulo - Brazil


Ricardo

You can configure k3b to use lame under Settings > Configure k3b > Plugins > K3b External Audio Encoder. Add the device to the left-hand panel and configure it on the right side using the lame command line options. Mine has the following entries:

Name: Mp3 (lame)
Extension: mp3
Command: lame -h --tt %t --ta %a --tl %m --ty %y --tc %c - %f

For kaudiocreator, try this. In ~/.kde/share/config/kaudiocreatorrc make sure there's an entry like this:

[CD]
device=/dev/cdrom,/dev/cdrom2

I think that will tell it which devices it can use.

And finally, tcdecode is part of the transcode program package. Install that and you should get all of the other 'tc' entries as well.

HTH

Hi David! You wrote:
You can configure k3b to use lame under Settings > Configure k3b > Plugins > K3b External Audio Encoder. Add the device to the left-hand panel and configure it on the right side using the lame command line options. Mine has the following entries:

Name: Mp3 (lame)
Extension: mp3
Command: lame -h --tt %t --ta %a --tl %m --ty %y --tc %c - %f

I do just like you wrote and k3b begins to rip OK. It's very interesting that I alter nothing. When I open the "Settings > Configure k3b > Plugins > K3b External Audio Encoder" the values you suggest already stay there. I only click OK. Can you understand this crazy thing?

And then you wrote:

For kaudiocreator, try this. In ~/.kde/share/config/kaudiocreatorrc make sure there's an entry like this:

[CD]
device=/dev/cdrom,/dev/cdrom2

I think that will tell it which devices it can use.

I proceed the lateration just as you tell. It seems KAudioCreator now recognizes /dev/cdrom2 as /dev/cdrom/. As it doesn't open disks in any drive we can see your suggestion as a partial solution. When I began try to use KAudioCreator it reconized only de cdrom2. Suddenly it recognizes nothing. I'm afraid that this situation repeats

And finally, tcdecode is part of the transcode program package. Install that and you should get all of the other 'tc' entries as well

I can't understand what you mean. Transcode programa package? May you develop a little bit?

Than you very much, David

transcode is a suite of programs for video and audio encoding. In addition to the transcode program itself, there are several sub-programs, including tcdecode, tccat, and others. K3b can use these as plugins for dvd ripping. So if you install 'transcode', you'll also get all the other ones that begin with 'tc'.

As for the cd drives, I don't know what your problem is, but I get the feeling it's not kaudiocreator itself causing it, but something more basic. Are the /dev entries themselves changing, for example? Do any other cd-reading devices show the same behavior? What does your /etc/fstab file say?

Only KAudio Creator make this mistake with CDROMs.

Below a copy of /etc/fstab...

# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/hda6 / ext2 defaults 1 1
/dev/hdc /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0
/dev/hdd /mnt/cdrom2 auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec,users 0 0
none /mnt/floppy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0,iocharset=iso8859-1,sync,codepage=850 0 0
/dev/hda1 /mnt/windows ntfs umask=0,nls=iso8859-1,ro 0 0
none /proc proc defaults 0 0
/dev/hda5 swap swap defaults 0 0