new LAME version

[Andrew Lim]

hi all,

LAME is now at 3.98.2; any way to manually update iTunes-LAME with
this newer version?

thanks!

[Chris]

Sure there is.

1. Download LAME.
2. Compile it.
3. Install it.
4. Delete LAME from inside the package contents of iTunes-LAME.

And that's it. iTunes-LAME will then use the newest version of LAME.

If you don't understand how to do any of steps 1 thru 4, I can provide
more details.

[Andrew Lim]

hello,

1. so the LAME-inside-the-package-contents-of-iTunes-LAME is the 388KB
file without an extension, in Contents/Resources?
2. i downloaded the latest version of LAME, but have no idea how to
compile it. within the LAME zipped package i noticed two folders
called "mac" and "mac os x," but don't know how to proceed from there.

thanks for the promt response!

[Joel Nordell]

Yep-- the file "Contents/Resources/lame" is the lame encoder.  I would actually just rename it, rather than deleting it, in case something goes wrong.  To compile the new one, do something like this (in Terminal):

$ cd /tmp
$ tar zxf /path/to/my/downloaded/lame-398-2.tar.gz
$ cd lame-398-2
$ ./configure && make && sudo make install

Note, you'll need to have the Developer Tools installed.  (Oh, in case you haven't worked with the command line before, the $'s above represent the prompt -- don't type them.)

Joel

[Andrew Lim]

i see, thanks. how do i check if i have the developer tools installed?

On Sep 23, 11:27 am, "Joel Nordell" <joelnord...@gmail.com> wrote:
> Yep-- the file "Contents/Resources/lame" is the lame encoder.  I would
> actually just rename it, rather than deleting it, in case something goes
> wrong.  To compile the new one, do something like this (in Terminal):
>
> $ cd /tmp
> $ tar zxf /path/to/my/downloaded/lame-398-2.tar.gz
> $ cd lame-398-2
> $ ./configure && make && sudo make install
>
> Note, you'll need to have the Developer Tools installed.  (Oh, in case you
> haven't worked with the command line before, the $'s above represent the
> prompt -- don't type them.)
>
> Joel
>

[Joel Nordell]

Try typing "gcc -v" in Terminal.  If you have the developer tools installed, it will say something like this:

Using built-in specs.
Target: i686-apple-darwin9
Configured with: /var/tmp/gcc/gcc-5465~16/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=i686-apple-darwin9 --with-arch=apple --with-tune=generic --host=i686-apple-darwin9 --target=i686-apple-darwin9
Thread model: posix
gcc version 4.0.1 (Apple Inc. build 5465)

If it says something like this:

-bash: gcc: command not found

Then you don't have it.

Most likely, if you don't know whether you have it installed, you probably don't.  I think it is included on the Leopard DVD, otherwise you'll have to download it from Apple.

Joel

[Andrew Lim]

nope, no developer tools installed!

the only thing i found on the apple website, as far as downloading
them, is xcode. is that what i want?

andrew

On Sep 23, 12:36 pm, "Joel Nordell" <joelnord...@gmail.com> wrote:
> Try typing "gcc -v" in Terminal.  If you have the developer tools installed,
> it will say something like this:
>
> Using built-in specs.
> Target: i686-apple-darwin9
> Configured with: /var/tmp/gcc/gcc-5465~16/src/configure --disable-checking
> -enable-werror --prefix=/usr --mandir=/share/man
> --enable-languages=c,objc,c++,obj-c++
> --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/
> --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib
> --build=i686-apple-darwin9 --with-arch=apple --with-tune=generic
> --host=i686-apple-darwin9 --target=i686-apple-darwin9
> Thread model: posix
> gcc version 4.0.1 (Apple Inc. build 5465)
>
> If it says something like this:
>
> -bash: gcc: command not found
>
> Then you don't have it.
>
> Most likely, if you don't know whether you have it installed, you probably
> don't.  I think it is included on the Leopard DVD, otherwise you'll have to
> download it from Apple.
>
> Joel
>

[Chris]

Yep, XCode is the development package. It's also on the Leopard DVD
which is where I installed it from.

[Andrew Lim]

alright.

i installed xcode, and ran the terminal command you mentioned above.

terminal did a bunch of stuff, then at one point prompted me for my
system password, then did a bunch more stuff, then finished.

i expected to find the "lame" file somewhere, with no extension, but i
can't. i'm not sure what if any new files have been written, and i'm
also wondering if i should have run the command you gave me from the
"macosx" folder within "lame-398-2"?

[Chris]

Check in /usr/local/bin to satisfy your curiosity. However, you don't
need anything from there. Just leave it alone.

Keep following the initial 4 steps I gave you and it will work.

When you delete LAME from inside the package contents of iTunes-LAME,
it will automatically use the one you just installed (in /usr/local/
bin).

[Andrew Lim]

ahh, so that's where things go! awesome. thank you so much, chris!

now, a couple of follow-up questions...

1. is there an advantage to leaving the LAME codec in usr/local/bin,
instead of moving it back into the itunes-LAME package? does this
provide "global" access to other utilities/programs that may need LAME
(although i don't have any that do)?
2. how do i uninstall the few gigabytes of developer tools that i put
on?

[Andrew Lim]

nevermind about question 2; there are uninstall instructions in the
"About Xcode" .PDF that came with the download.

but i'm still curious about question 1!

[Chris]

Well, try typing LAME --version from a terminal window and you'll
notice that now LAME is in your path and is a command-line tool.
There probably are other apps that use the LAME install, although I'm
not sure of specifics. I think Audacity uses it. I know XLD has the
latest LAME built-in so it won't use it.

Maybe someone else knows of specific examples of apps that use the
LAME libraries installed?

I'd leave LAME where it belongs :)

[splacknuck]

Hi,

Chris wrote:
> Well, try typing LAME --version from a terminal window and you'll
> notice that now LAME is in your path and is a command-line tool.
>

> <snip>

>
> I'd leave LAME where it belongs :)

I just installed the new LAME and removed the lame-ressource from
iTunes-Lame. It's now using LAME 3.98.2 – excellent! Thanks for your
suggestion!

Just one more question: I have a LAME-framework I downloaded from [1]
and use for LAME-exports from QuickTime. When I manually start the
LAME-binary in /Library/Frameworks/LAME.framework/Versions/A, “LAME
32bits version 3.98.2 (http://www.mp3dev.org/)” is displayed in
terminal. Does that mean that my QuickTime-exports are using the
latest LAME as well? Unfortunately these exports do not have the LAME-
version comment.

Kind regards.

[1]: <http://karaoke.kjams.com/wiki/index.php/Lame>