Can't get my audio cds to read.. HOW CAN I RIP THEM?

theAntic · 07-11-2004, 05:07 PM

Ok, so I downloaded the LAME tar.gz file from KDE's site, and am looking at the INSTALL text file that it came bundled with..... it's not making any sense to me. How do I install the file encoding feature to allow Kaudio to rip into .mp3? Do I simply add the extension (ie. --enable-mp3rtp) to the end of the % ./configure command, or do I add it after the the % make install command? Or is there some other way to load it that I just don't know about?

Here's the INSTALL text below:

Quote:

=======================================================================
Compile time options
=======================================================================
There are serveral targets which can be built from this
source code:

lame, lame.exe The command line encoder

mp3x A GTK based graphical MP3 frame analyzer. For debugging,
development, and studing MP3 frames produced by any
encoder.

lame_enc.dll a Windows DLL used by many GUIs which support lame.
(Can only be compiled by MSVC???)

lame.acm a Windows ACM codec which can be used by
many windows programs, and any directshow program.
See MSVC project files in ACM directory.
Right click on lame.inf to install.

lame_enc.dshow a Windows direct show filter for lame. Potentially has
more flexability than the ACM codec, but code needs some
work. See MSVC project files in dshow directory

libmp3lame.a the static encoding library used by all platforms, required
by all the above targets.

libmp3lame.so shared version of libmp3lame.a for *NIX platforms

The following compile time options can be used. For libmp3lame.a
and lame_enc.dll, none are required. On non-unix systems,
these options must be set in config.h or in the IDE.
On unix systems, they are set via ./configure.

#define HAVE_MPGLIB compile in mpglib's mp3 *decoding* capibility
#define HAVE_VORBIS compile in Vorbis decoding capibility
(you need libvorbis already built)
#define NOANALYSIS do not compile in hooks used by the
MP3 frame analyzer.

Options for the command line encoder:
#define LIBSNDFILE to use Erik de Castro Lopo's libsndfile
for input.
#define BRHIST to allow the optional display of the VBR histogram

=======================================================================
Building the software on *NIX platforms using configure:
=======================================================================
Run the following commands:

% ./configure
% make
% make install

For a complete list of options, try "./configure --help"
Some of the more usefull options:

For the encoding library:

--enable-mp3x Build the mp3 frame analyzer, 'mp3x'

--enable-mp3rtp Build the encode-to-RTP program, 'mp3rtp'
(broken as of August 2001)

For the LAME front end encoder:

--with-fileio=lame Use lame's internal file io routines [default]
=sndfile Use Erik de Castro Lopo's libsndfile
(Supports many more input formats, but no stdin possible currently)

--with-sndfile-prefix=DIR Alternate location for libsndfile
(if --with-fileio=sndfile)

--enable-brhist Include the VBR bitrate histogram feature
(default:yes if any ncurses/termcap available)"

Other usefull configure options:

--enable-debug Build a debug version

--enable-expopt Enable some more optimizations flags for
the compiler, may or may not produce
faster code

--prefix = PATH default is /usr/local
(LAME currently installs:
/usr/local/bin/lame
/usr/local/lib/libmp3lame.a
/usr/local/lib/libmp3lame.so
/usr/local/include/lame.h

--with-vorbis Enable Ogg Vorbis decoding support
--with-vorbis-prefix = PATH specify where to find Vorbis libs

Some more advanced ways to influence the build procedure
(experienced users only, use it at your own risk):

- If you want to use some custom defines for building (e.g. some out
of the file "DEFINES") use:

* bourne shell or compatible (ash, bash, zsh, ...):
CONFIG_DEFS="-Dmy_define" ./configure

* C shell or compatible (csh, tcsh, ...):
setenv CONFIG_DEFS "-Dmy_define"
./configure

- If you want to use some additional options for the compiler:

* bourne shell or compatible (ash, bash, zsh, ...):
CFLAGS="--my_flag" ./configure

* C shell or compatible (csh, tcsh, ...):
setenv CFLAGS "--my_flag"
./configure

Or some combination of the above.

Note:
If configure detects the presents of "nasm" some additional speed
improvements get compiled in (additional assembler code to detect
and use multimedia extensions of the used processor).

THANKS!

PS. How do you implement these commands? Typing % ./configure--help into the Run Command box just threw an error on me.

whansard · 07-12-2004, 12:38 AM

you don't have to do any of that hard stuff. just ./configure then make then make install. When the other program tries to run lame, it will then be able to. and you would have needed a space between configure and --help. ./configure --help. but you don't need that.