Download iTunes-LAME Encoder for Mac - Bridges the gap between iTunes and the LAME encoder. MacUpdate Mac MP3 Software Downloads

Members

[login]

Developers

[login]

Add a File +

iTunes-LAME Encoder bridges the gap between iTunes and the LAME command line encoder. It joins the simple interface of iTunes with the higher quality of the LAME encoder.

Version 2.0.9-34:

ID3v1 Tags
Working Unicode support

OTHER PEOPLE SUGGEST

SoX Wrap (votes: 1 )

Suggest something else:

HUZZAM Better with tags, but slower:

I'm glad to see they've worked out the tagging issues. Now all the tags seem to make it to the encoded files, though some Unicode still gets mangled (accented Greek characters, so far, in my experience). Still, a definite improvement over 2.0.8, which just lost ~75% of tags!

I do notice, though, that this version runs at about 40% the speed of 2.0.8 on my Core 2 Duo 2gHz Macbook. I thought maybe I had a PowerPC version, but Activity Monitor shows it as Intel. I used to get around 12x encoding with "--preset standard", and now I'm at 4.5x. Any ideas?
(Version 2.0.9-34)

SHOCK J This no longer works for me in iTunes 7.5 and Leopard on MacBook Pro. Not sure if it's an iTunes issue or a Leopard issue. Anyone got this working in these conditions?
(Version 2.0.9-34)

Replies:

Dec 1 2007

SHOCK J I got it working. I had a separate install of the LAME framework installed and I think it was conflicting with this one. As soon as I removed the extra framework, this encoder started working.
(Version 2.0.9-34)

Dec 25 2007

MDEWAKANTON I too had this trouble updating iTunes to 7.5 under Tiger 10.4.9 and could solve it in a different way (Import with LAME didn't show up in Scripts menu): Show package contents > Contents > Resources > Import with LAME....scpt, I put a copy of this script in iTunes Scripts folder and then it correctly showed up in menu and launched iTunes-LAME Encoder.

Hope this helps.
(Version 2.0.9-34)

CBX322 SUPERB!!! Finally this version of iTunes-Lame is working flawlessly with iTunes > 7.02. No lost tags anymore, no need to rewrite tags. Tags are already written as v2.4. Still recognizes own compiled lame binary. Just perfect. Works in Tiger and Leopard. Thank you so much!
(Version 2.0.9-34)

CBX322 Are the tagging issues solved? (lost tag information with version 2.08 and iTunes > 7.02)
(Version 2.0.9-34)

ITBJORN where can I find the script that helps me open it from inside iTunes?
(Version 2.0.9-34)

Replies:

Oct 27 2007

JEAN-LOUP You need to copy the app into ~/Library/iTunes/Scripts/ folder (~ means your Library folder, not the one at the root, but should work too)

If the Scripts folder does not exist, create it

And you access iTunes-LAME encoder from the scipt menu inside iTunes : Import with LAME�
(Version 2.0.9-34)

Oct 28 2007

ITBJORN Did what you said, and nothing new shows in the sripts menu.
(Version 2.0.9-34)

Oct 28 2007

DZP There was never a script to launch the iTunes-Lame application, it used to be that placing the application in the ~/Library/iTunes/Scripts/ folder, it would be accessible from iTunes' script menubar item and "just work". This has changed since a few iTunes releases. You can no longer (with the current iTunes version at least) access an .app directly from the script menu, but a simple workaround is to write your own script as follows :

- Open Script Editor ( /Applications/Applescript/Script Editor ).

- Paste the following line :

tell application "iTunes-LAME" to launch

- Save the script as "iTunes-LAME" with File Format: Script.

- Place your new script in ~/Library/iTunes/Scripts/ and it'll show up in the iTunes' script menubar item. Clicking it will launch the iTunes-LAME application.

Note that the iTunes-LAME application itself can be left in the /Scripts/ folder or you can place it in your /Applications/ folder. Now it "just works" again. ;-)
(Version 2.0.9-34)

Oct 28 2007

ITBJORN Thanks a lot!
(Version 2.0.9-34)

OSXPOWERBOOK iTunes-LAME is a fantastic program, but several months ago it started giving me problems. Would not import all of the tracks, or wouldn't put all the information (ID tags) into the tracks that would actually import.

I think because iTunes seems to have an update every couple of weeks, it has changed enough that there are now compatability bugs with the last version of iTune-LAME... if it were brought up to date with the LATEST version of iTunes, the problem would probably be resolved.

I MISS using LAME!
(Version 2.0.9b4)

MARKOH http://sbooth.org/Max/

you won't need anything else. I once used to use iTunes-LAME... when it used to work.
(Version 2.0.9b4)

CANOEBERRY I used iTunes-LAME for years but I am having trouble for the first time. The AIF tracks have all the track information in them, including now, for the first time, Album Art.

I am having trouble when the mp3 files are created, the ID3 tags are not making into most of the tracks. So the Album field is often blank, for example.

My current theory that I cannot quite test at the moment is that the album art in the AIF file (which is a new feature of iTunes) is causing problems.

Anybody else experienced this problem?
(Version 2.0.8)

G8TGOD Okay, I'm convinced. I had heard that the mp3 encoder for iTunes was not very good, and that LAME was essential. But I figured people were just being overly picky. Not so. I have one CD that is just not bearable using the iTunes encoder, even at 192.

But have you ever tried to use LAME? Not exactly user friendly. The iTunes-LAME script is simple and it works; it's great!

One question: this says it's v. 2.0.8, but when I open the script, it says v. 2.0.7. Am I missing something here?
(Version 2.0.8)

AKA This is an essential script. I would gladly donate to keep the author in business and to see updates incorporating the latest preferred LAME builds.

In the meantime, for those wishing to use iTunes-LAME 2.0.8 with LAME 3.97b2 (preferred build as of this writing), see:

http://alpharuin.blogspot.com/2006/01/guide-itunes-lame-correct-way.html
(Version 2.0.8)