The de facto standard for audio podcasts is the ubiquitous MP3. Is this a fair situation? Can YOU actually tell the difference yourself? * structured storage will write encoded output files into a directory structure defined by the “outdirTemplate” property below.Amongst the podcasting fraternity the debate over “what is the best MP3 encoder to use for podcasts” has raged for a quite while, although the general consensus seems to have swung in one particular direction. – flat structure will directly write encoded output files into the destination directory * flat structure is enabled by default for all playlists except “Library” and “Bibliothek” (Library in german version of iTunes) + supports flat and structured storage modes: (even audio in video files, Apple Lossless Files and direct ripping from Audio CD) + supports reencoding every media type supported by Quicktime and iTunes + automatically determines location of oggenc and mov123 (at least it tries to) + merged several changes from the original iTunes-LAME script 1.0.4b ITunesAlternativeEncoders1.2.zip (OS X Universal) + optimized universal binaries of mov123 and aoTuV (beta 4.51 / Release 1) enhanced Ogg Vorbis Encoder bundled ITunesAlternativeEncoders1.3.zip (OS X Universal) + Universal binary of Ogg Vorbis Encoder updated to aoTuV beta 5 ITunesAlternativeEncoders1.4.zip (OS X Universal) Ideally set this to the number of CPUs or cores in your system. + support for splitting encoding up into multiple “threads” to take advantage of multiple CPUs / coresĪdjust property threadCount to a value higher than 1 to enable support. + Fixed some tag encoding issues in the Ogg Vorbis script:Īll tags will now be encoded in UTF-8, so Umlauts and other special characters will work okay. Once you’ve changed the properties, save the script. Rule of thumb is threadCount = number of CPUs / cores. )įor instance change this to 2 if you want to stress your dual-core or dual-CPU system. While this is optimal on single-core single-CPU systems, this doesn’t make perfect use of that multi-core/multi-CPU beast on or under your desk. The thread count is set to 1 by default, which will spawn only one encoding process. Property threadCount : 1 - number of “threads” to split the encoding into, use this to take advantage of multiple CPUs / cores Copy the “Utilities” directory along with both scripts to your /Users/ is your account name. You’ll need to get it from the usual sources: RareWares or Fink Installation The sourcecodes are available here, here and here.ĭue to legal and patent restrictions I can’t supply a compiled universal binary of LAME. Both are optimized for G4 and Intel Core. This file includes statically compiled Universal binaries of the aoTuV (beta 5) enhanced version of oggenc and mov123. ITunesAlternativeEncoders1.5.zip (OS X Universal) This means you can take advantage of your dual-core / quad-core / multi-CPU system when encoding large amounts of files. Version 1.4 introduced a feature to split up the encoding process into simultaneously running parts, which essentially is a form of multithreading. Since version 1.2 compilations are correctly handled too. All this can be customized by means of editing some simple options in the scripts. The “flat” mode writes the output files directly to the destination directory, whereas the “structured” mode writes those encoded files ordered in subdirectories similar to the way iTunes does when it is managing music files. It also adds support for structured and flat storage. This includes Apple Lossless, AAC, Audio-CDs and standard MP3! Even audio tracks in video files can be re-encoded to Ogg Vorbis/MP3. So, why is it different from similar scripts? It offers support for all audio filetypes supported by iTunes and Quicktime due to the use of “mov123” by the slimserver project. The iTunes Alternative Encoders pack includes two AppleScripts for iTunes that allow to (re-)encode almost any audio file to either Ogg Vorbis using oggenc or MP3 using LAME.
0 Comments
Leave a Reply. |