{?xml version="1.0" encoding="UTF-8"?}
{!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"}
{plist version="1.0"}
{dict}
{key}NSWindow Frame encoderWindow{/key}
{string}-1022 269 324 126 -1024 0 1024 768 {/string}
{key}dv com.apple.soundmgr._DV Sound Output Settings{/key}
{data}
fQAAAA==
{/data}
{key}encodingOptions{/key}
{array}
{string}--vcomment --abr 160 -h{/string}
{string}-h -b 160{/string}
{string}--alt-preset standard{/string}
{/array}
{/dict}
{/plist}


-N.B. geschweifte Klammern durch kleiner/grösser ersetzen

Der Link www.blacktree.com

Ja, Richtig, den local lame.
Hier infos und link zu einem "besseren" LAME


OSX: Modifying iTunes-LAME to use an Alternate LAME Installation

LAME has long been considered a premier encoder on any platform and compiles on OSX. The problem with using it to encode a large number of files is that it requires hand entry of ID tags. Although available for some time now, I recently discovered iTunes-LAME Encoder by Blacktree, Inc. This software installs as an iTunes script plug-in allowing iTunes to utilize LAME as its encoder. iTunes-LAME Encoder combines the convenience of iTunes' song management and ability to retrieve CD track names (unfortunately via Gracenote, see FreeDB for more on this) with LAME's higher quality and flexibility. Aside from a few minor issues (like the inability to hide its window), iTunes-LAME Encoder shines.

iTunes-LAME Encoder 2.0.2 utilizes an existing local LAME install or the LAME 3.92 included with the distribution. It expects a local LAME installation to reside in /usr/local/bin, which is the default place for make to install. As discussed in Utilizing an Alternative to /usr/local on OSX, there are other locations that an administrator might install projects compiled locally. Here we will see how to modify iTunes-LAME to utilize an LAME installation in a path other than /usr/local/bin.

iTunes-LAME contains an internal copy of LAME 3.92 that must be disabled before getting it to use a LAME binary out of its expected path. This copy is easily found by opening iTunes-LAME's package in the Finder by Right (Control) Clicking the iTunes-LAME icon and selecting 'Show Package Contents' from the resulting contextual menu. The path to the internally installed copy is /Users/[user_name]/Library/iTunes/Scripts/iTunes-LAME.app/Contents/Resources/lame. Deleting or renaming the binary are viable options. I choose to compress it in order to keep the copy on hand, without it taking up undue space. This is a simple matter of typing at a Terminal or xterm prompt gzip -9 /Users/[user_name]/Library/iTunes/Scripts/iTunes-LAME.app/Contents/Resources/lame. I then created a symbolic link to the local copy of LAME (3.93) in the same directory that iTunes-LAME stores its internal version:

ln -s /Users/Shared/bin/lame /Users/[user_name]/Library/iTunes/Scripts/iTunes-LAME.app/Contents/Resources

iTunes-LAME now uses the locally installed copy of LAME as if it was the internal version is ships with. The LAME version iTunes-LAME uses is easily verified by clicking the 'About' button in the iTunes-LAME window. The second line of text in the about dialog displays the version, in this case 'LAME v3.93.'

OSX: Modifying iTunes-LAME's Encoding Options List

iTunes-LAME Encoder 2.0.2 by Blacktree, Inc. working window has an 'Encoding Options' pop-up menu that allows selection and entry of either its default LAME encoding options, or those created by the end user. However, it doesn't allow one to delete or modify an existing option. This limitation is easily circumvented by editing the file iTunes-LAME uses to generate the menu. iTunes-LAME stores this data in a property list file with the following path:

/Users/[user_name]/Library/Preferences/com.blacktree.iTunes-LAME.plist

Edit the file using a text editor or a plist editor like Apple's Property List Editor. Each string entry under the key encodingOptions is a menu choice in iTunes-LAME's 'Encoding Options' which you can delete, modify, or create new entries. The following shows the software's two defaults and a line with my personal setting.





NSWindow Frame encoderWindow
-1022 269 324 126 -1024 0 1024 768
dv com.apple.soundmgr._DV Sound Output Settings

fQAAAA==

encodingOptions

--vcomment --abr 160 -h
-h -b 160
--alt-preset standard

benutzt i tunes nicht den amtlichen lame encoder? zumindest in den pods steckt lame technologie - beim decoder....

Mit einem schnelleren Rechner ?

Nein, im Ernst. iTunes konvertiert am schnellsten.
Ander encoder könnten jedoch bessere Qualitäten liefern;-)

die itunes konvertierung erscheint mir recht flott - ich kenne nur noch langsamere.
ansonsten hier vielleicht:

faktor 30 reicht nicht?

Ich habe oft CD mit iTunes konvertiert.
Mir scheint oft sehr langsam zu sein. Welche Alternative gibt es noch die aber schneller eine CD in mp3 konvertiert?