<style type="text/css">
<!--
body { font-family: "Times New Roman", Times, serif; color: #000000; background-color: #FFFFFF; }
+ p { text-align: justify; }
tt, pre, code { font-family: Courier New, Courier, mono; background-color: #EDF3F7; padding: 1px; }
h1:not(:first-child) { margin-top: 2.25em; }
h2 { margin-top: 2.0em; }
<li><a href="#third-party-software"><span class="toc-section-number">2.1</span> Third-party Software</a></li>
<li><a href="#license-terms"><span class="toc-section-number">2.2</span> License Terms</a></li>
</ul></li>
-<li><a href="#install-instructions"><span class="toc-section-number">3</span> Install Instructions</a><ul>
-<li><a href="#install-the-lamexp-software"><span class="toc-section-number">3.1</span> Install the LameXP Software</a><ul>
-<li><a href="#setup-program"><span class="toc-section-number">3.1.1</span> Setup Program</a></li>
-<li><a href="#zip-package"><span class="toc-section-number">3.1.2</span> ZIP Package</a></li>
+<li><a href="#anti-virus-notes"><span class="toc-section-number">3</span> Anti-Virus Notes</a><ul>
+<li><a href="#reporting-false-positives"><span class="toc-section-number">3.1</span> Reporting False Positives</a></li>
+<li><a href="#anti-virus-conclusions"><span class="toc-section-number">3.2</span> Anti-Virus Conclusions</a></li>
</ul></li>
-<li><a href="#portable-mode"><span class="toc-section-number">3.2</span> Portable Mode</a><ul>
-<li><a href="#enable-the-portable-mode"><span class="toc-section-number">3.2.1</span> Enable the Portable Mode</a></li>
-<li><a href="#disable-the-portable-mode"><span class="toc-section-number">3.2.2</span> Disable the Portable Mode</a></li>
+<li><a href="#install-instructions"><span class="toc-section-number">4</span> Install Instructions</a><ul>
+<li><a href="#install-the-lamexp-software"><span class="toc-section-number">4.1</span> Install the LameXP Software</a><ul>
+<li><a href="#setup-program"><span class="toc-section-number">4.1.1</span> Setup Program</a></li>
+<li><a href="#zip-package"><span class="toc-section-number">4.1.2</span> ZIP Package</a></li>
</ul></li>
-<li><a href="#
install-the-aac-encoder"><span class="toc-section-number">3.3</span> Install the AAC Encoder</a><ul>
-<li><a href="#nero-digital-aac-encoder"><span class="toc-section-number">3.3.1</span> Nero Digital AAC Encoder</a></li>
-<li><a href="#qaac-apple-aac-encoder"><span class="toc-section-number">3.3.2</span> QAAC (Apple AAC) Encoder</a></li>
+<li><a href="#
portable-mode"><span class="toc-section-number">4.2</span> Portable Mode</a><ul>
+<li><a href="#enable-the-portable-mode"><span class="toc-section-number">4.2.1</span> Enable the Portable Mode</a></li>
+<li><a href="#disable-the-portable-mode"><span class="toc-section-number">4.2.2</span> Disable the Portable Mode</a></li>
</ul></li>
+<li><a href="#install-the-aac-encoder"><span class="toc-section-number">4.3</span> Install the AAC Encoder</a><ul>
+<li><a href="#nero-digital-aac-encoder"><span class="toc-section-number">4.3.1</span> Nero Digital AAC Encoder</a></li>
+<li><a href="#qaac-apple-aac-encoder"><span class="toc-section-number">4.3.2</span> QAAC (Apple AAC) Encoder</a></li>
</ul></li>
-<li><a href="#tutorial-step-by-step-guide"><span class="toc-section-number">4</span> Tutorial (Step-by-Step Guide)</a><ul>
-<li><a href="#source-files"><span class="toc-section-number">4.1</span> Source Files</a></li>
-<li><a href="#output-directory"><span class="toc-section-number">4.2</span> Output Directory</a></li>
-<li><a href="#compression-settings"><span class="toc-section-number">4.3</span> Compression Settings</a></li>
-<li><a href="#processing"><span class="toc-section-number">4.4</span> Processing</a></li>
</ul></li>
-<li><a href="#
help-support"><span class="toc-section-number">5</span> Help & Support</a><ul>
-<li><a href="#download-mirrors"><span class="toc-section-number">5.1</span> Download Mirrors</a></li>
-<li><a href="#diagnostic-output"><span class="toc-section-number">5.2</span> Diagnostic Output</a></li>
-<li><a href="#bugtracker"><span class="toc-section-number">5.3</span> Bugtracker</a></li>
-<li><a href="#support-forum"><span class="toc-section-number">5.4</span> Support Forum</a></li>
+<li><a href="#
tutorial-step-by-step-guide"><span class="toc-section-number">5</span> Tutorial (Step-by-Step Guide)</a><ul>
+<li><a href="#source-files"><span class="toc-section-number">5.1</span> Source Files</a></li>
+<li><a href="#output-directory"><span class="toc-section-number">5.2</span> Output Directory</a></li>
+<li><a href="#compression-settings"><span class="toc-section-number">5.3</span> Compression Settings</a></li>
+<li><a href="#file-processing"><span class="toc-section-number">5.4</span> File Processing</a></li>
</ul></li>
-<li><a href="#developer-center"><span class="toc-section-number">6</span> Developer Center</a><ul>
-<li><a href="#source-code-access"><span class="toc-section-number">6.1</span> Source Code Access</a></li>
-<li><a href="#build-prerequisites"><span class="toc-section-number">6.2</span> Build Prerequisites</a></li>
-<li><a href="#qt-as-static-libraries"><span class="toc-section-number">6.3</span> Qt as Static Libraries</a></li>
+<li><a href="#help-support"><span class="toc-section-number">6</span> Help & Support</a><ul>
+<li><a href="#download-mirrors"><span class="toc-section-number">6.1</span> Download Mirrors</a></li>
+<li><a href="#diagnostic-output"><span class="toc-section-number">6.2</span> Diagnostic Output</a></li>
+<li><a href="#bugtracker"><span class="toc-section-number">6.3</span> Bugtracker</a></li>
+<li><a href="#support-forum"><span class="toc-section-number">6.4</span> Support Forum</a></li>
</ul></li>
-<li><a href="#f.a.q.-frequently-asked-questions"><span class="toc-section-number">7</span> F.A.Q. (Frequently Asked Questions)</a></li>
+<li><a href="#developer-center"><span class="toc-section-number">7</span> Developer Center</a><ul>
+<li><a href="#source-code-access"><span class="toc-section-number">7.1</span> Source Code Access</a></li>
+<li><a href="#build-prerequisites"><span class="toc-section-number">7.2</span> Build Prerequisites</a></li>
+<li><a href="#qt-as-static-libraries"><span class="toc-section-number">7.3</span> Qt as Static Libraries</a></li>
+</ul></li>
+<li><a href="#f.a.q.-frequently-asked-questions"><span class="toc-section-number">8</span> F.A.Q. (Frequently Asked Questions)</a></li>
</ul>
</nav>
<h1 id="introduction"><span class="header-section-number">1</span> Introduction</h1>
along with this program; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</code></pre>
<p> <br /><strong>Addendum:</strong> When distributing binaries of the LameXP software, it is <em>strictly forbidden</em> to bundle the LameXP program files and/or the LameXP installation program with any kind of <em>Adware</em>, <em>Spyware</em> or <em>PUP (potentially unwanted program)</em>, including, but not limited to, any downloaders, dialers, browser toolbars/extensions or restricted shareware/demo programs. It is, however, perfectly legitimate to bundle LameXP with other <em>OpenSource</em> programs, according to the OSI (Open Source Initiative). Finally, it is also legitimate to bundle LameXP with <em>commercial software</em>, as long as that software does <em>not</em> meet the criteria of <em>Adware</em>, <em>Spyware</em> or <em>PUP</em>. If you bundle the LameXP software with another software, you are <em>required</em> to make sure that the user is provided with an easy way to install and start the LameXP software separately from that other software.</p>
-<h1 id="install-instructions"><span class="header-section-number">3</span> Install Instructions</h1>
+<h1 id="anti-virus-notes"><span class="header-section-number">3</span> Anti-Virus Notes</h1>
+<p>Occasionally, it may happen that your anti-virus software <em>mistakenly</em> detects <a href="http://en.wikipedia.org/wiki/Malware">malware</a> (virus, trojan horse, worm, etc.) while you are trying to run the LameXP application or the LameXP setup program. This is called a <a href="http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives"><strong>false positive</strong></a> and the file actually is <strong>not</strong> malware. Instead, this is an error (bug) in your particular anti-virus software! In case that you encounter this kind problem, we highly recommend using <a href="http://www.virustotal.com/">VirusTotal.com</a>, <a href="http://www.virscan.org/">Virscan.org</a> or a similar web-service to check the file in question with <em>multiple</em> anti-virus engines. Unless the vast majority of the anti-virus engines detect malware, it can be assumed that the file is really harmless. However, please take care with <em>heuristic</em> scan results, such as "suspicious", "generic" or "packed". Those results are <strong>not</strong> confirmed malware detections – they are highly speculative and (almost certainly) can be ignored safely!</p>
+<p>Defective anti-virus software is an ongoing annoyance! For example, anti-virus programs tend to suspect installers (or uninstallers) created with <a href="http://nsis.sourceforge.net/">NSIS</a> – which includes the LameXP setup program. But, of course, installers created with NSIS are perfectly legitimate. Thus, if your anti-virus program complains about the LameXP setup program, please ignore the <em>nonsensical</em> warning! Furthermore, it seems that some anti-virus programs accuse <em>all</em> "packed" executables of being malware. Nonetheless, using so-called "executable packers", e.g. <a href="http://upx.sourceforge.net/">UPX</a>, is perfectly legitimate. Executable packers are commonly used by legitimate software, including numerous OpenSource projects – and so does LameXP. Thus, if your anti-virus program complains about the LameXP program file, because it has been "packed" by UPX, please ignore the <em>nonsensical</em> warning!</p>
+<p>Last but not least: Always keep in mind that LameXP is <em>free software</em>, i.e. the <em>source codes</em> of LameXP are freely available to everybody! Thus, in case that you do <em>not</em> trust the provided <em>binaries</em> of LameXP, you may scrutinize the LameXP <em>source codes</em> and then build your own binaries…</p>
+<h2 id="reporting-false-positives"><span class="header-section-number">3.1</span> Reporting False Positives</h2>
+<p>An important fact to consider is, that, for the developer of a legitimate application, it is <em>impossible</em> to know <strong>why</strong> a specific anti-virus software may be <em>misinterpreting</em> his or her application as malware. That is because anti-virus programs generally are <em>proprietary</em> (ClosedSource) software – anti-virus companies don <em>not</em> publish their source codes or reveal their algorithms. Moreover, a zillion of <em>different</em> anti-virus programs exist nowadays. For these reasons, the application developer can <em>not</em> know what is going on "behind the scenes" in a particular anti-virus software. Consequently, any assumptions on the reasons that are causing the <a href="http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives"><strong>false positive</strong></a> would be nothing but pure speculation! Even worse, anti-virus software is updated frequently, so the reasons why the anti-virus software is <em>misinterpreting</em> the application as malware may change constantly!</p>
+<p>At this point, it should be clear that implementing <em>workarounds</em> for defective anti-virus software is <strong>not</strong> a viable option for application developers. Instead, since the <a href="http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives"><strong>false positive</strong></a> is an error (bug) in the particular <em>anti-virus software</em>, it can be fixed <em>only</em> by the developer of the anti-virus software. Therefore, it is important that <em>you</em>, the (paying) customer of the anti-virus company, contact the support team of the anti-virus company and report the problem to them! Most anti-virus companies provide ways to report <em>false positives</em> in a standardized way, e.g. by means of a <a href="http://en.wikipedia.org/wiki/Form_%28HTML%29">webform</a>. However, it is <em>not</em> possible to list them all here. So please refer to the anti-virus developer's web-site. Also, when reporting <em>false positives</em>, please be self-confident: As a paying customer, you can demand that <em>false positives</em> get fixed in a timely manner. Otherwise, get your money back!</p>
+<h2 id="anti-virus-conclusions"><span class="header-section-number">3.2</span> Anti-Virus Conclusions</h2>
+<ul>
+<li><p>IN CASE YOU HAVE A CONFIRMED INFECTION, RE-DOWNLOAD THE FILE FROM ONE OF THE <em>OFFICIAL</em> MIRRORS!</p></li>
+<li><p>DO NOT SEND US VIRUS REPORTS, UNLESS YOU HAVE VERIFIED THE INFECTION WITH MULTIPLE ANTI-VIRUS ENGINES!</p></li>
+<li><p>PLEASE REPORT "FALSE POSITIVES" TO THE DEVELOPER OF YOUR ANTI-VIRUS SOFTWARE. WE CANNOT FIX THEM!</p></li>
+<li><p>THERE ARE PLENTY OF ANTI-VIRUS PROGRAMS TO CHOOSE FROM. YOU DON'T NEED TO STICK WITH A NEUROTIC ONE!</p></li>
+</ul>
+<h1 id="install-instructions"><span class="header-section-number">4</span> Install Instructions</h1>
<p>This chapter explains how to install the LameXP software on your computer. If LameXP has already been installed on your computer, you may skip this chapter.</p>
-<h2 id="install-the-lamexp-software"><span class="header-section-number">3.1</span> Install the LameXP Software</h2>
+<h2 id="install-the-lamexp-software"><span class="header-section-number">4.1</span> Install the LameXP Software</h2>
<p>Distribution packages of the LameXP software is provided in two different flavours: a self-running <strong>setup program</strong> and a <strong>ZIP package</strong>. For regular users, using the <em>setup program</em> is highly recommended!</p>
-<h3 id="setup-program"><span class="header-section-number">3.1.1</span> Setup Program</h3>
+<h3 id="setup-program"><span class="header-section-number">4.1.1</span> Setup Program</h3>
<p>In order to start the installation process, simply double-click on the downloaded LameXP <strong>setup program</strong>, e.g. <code>LameXP.yyyy-mm-dd.Release-Static.Build-xxxx.exe</code>.</p>
<p><em>Note:</em> Shortly after launching the setup program, an <a href="http://en.wikipedia.org/wiki/User_Account_Control">UAC</a> (User Access Control) dialogue may appear. This is a standard Windows security feature, so don't worry! You have to choose "Yes", if you wish to continue the installation process.</p>
<p><img src="img/lamexp/setup_1a.png" alt="Figure" /></p>
<p> <br />Congratulation, LameXP has been installed successfully on your computer!</p>
<p><em>Note:</em> If you keep the "Run LameXP …" option enabled and click on the "Finish" button, the LameXP software will be launched immediately.</p>
<p><img src="img/lamexp/setup_1c.png" alt="Figure" /></p>
-<h3 id="zip-package"><span class="header-section-number">3.1.2</span> ZIP Package</h3>
+<h3 id="zip-package"><span class="header-section-number">4.1.2</span> ZIP Package</h3>
<p>If you decided for the <strong>ZIP package</strong>, you need to open the downloaded ZIP file, e.g. <code>LameXP.yyyy-mm-dd.Release-Static.Build-xxxx.zip</code>, in your favourite file archive software (we recommend using <a href="http://www.7-zip.org/">7-Zip</a> or <a href="http://www.rarlab.com/download.htm">WinRAR</a>).</p>
<p><img src="img/lamexp/setup_2a.png" alt="Figure" /></p>
<p> <br />This step may be slightly different, depending on what file archive software (e.g. 7-Zip or WinRAR) you are using. Select <strong>all</strong> files in the LameXP ZIP archive and <em>extract</em> them to a new/empty directory of your choice.</p>
<p><img src="img/lamexp/setup_2b.png" alt="Figure" /></p>
<p> <br />Congratulation, LameXP has been installed successfully on your computer! Now double-click on the <code>LameXP.exe</code> program file in order to launch the application!</p>
<p><img src="img/lamexp/setup_2c.png" alt="Figure" /></p>
-<h2 id="portable-mode"><span class="header-section-number">3.2</span> Portable Mode</h2>
+<h2 id="portable-mode"><span class="header-section-number">4.2</span> Portable Mode</h2>
<p>First of all, it is important to note that there is <strong>no</strong> such thing as a <em>separate</em> "portable version" or "portable edition" of the LameXP software. Instead, <strong>all</strong> versions of the LameXP software always <em>are</em> "portable" – in the sense that the LameXP software is <em>fully self-contained</em> and thus <strong>no</strong> additional dependencies (libraries, frameworks, codecs or whatsoever) need to be installed on the computer separately. Or, in other words, the LameXP software is designed to work "out of the box". And this applies regardless of whether you choose the setup program or the ZIP package!</p>
<p>Nonetheless, the LameXP software supports a so-called "portable mode", which can be enabled or disabled at any time. By default, i.e. when the "portable mode" is <strong>not</strong> enabled, LameXP will store all of its configuration files in the current user's <a href="http://en.wikipedia.org/wiki/Environment_variable#Windows"><code>%APPDATA%</code></a> directory. This is the correct way of storing <em>user-specific</em> configuration files on a modern multi-user operating system. Some users, however, may wish to use LameXP as a <em>portable application</em>. For example, they may wish to run the LameXP software directly off an USB flash drive – and do that on many <em>different</em> machines. In this particular situation, storing the configuration files in the <em>same</em> location where the LameXP program file resides (e.g. on the USB flash drive), instead of the local <code>%APPDATA%</code> directory, may come in handy! And that is exactly what LameXP does when the "portable mode" is <em>enabled</em>.</p>
-<h3 id="enable-the-portable-mode"><span class="header-section-number">3.2.1</span> Enable the Portable Mode</h3>
+<h3 id="enable-the-portable-mode"><span class="header-section-number">4.2.1</span> Enable the Portable Mode</h3>
<p>If you fully understand what the consequences of the "portable mode" are and still want to <em>enable</em> this mode, then simply <strong>rename</strong> the LameXP program file form <code>LameXP.exe</code> to <code>LameXP-Portable.exe</code>. You must exit LameXP, before you can rename the program file!</p>
<p><em>Note:</em> By default, the LameXP installation directory is either <code>C:\Program Files (x86)\MuldeR\LameXP</code> or <code>C:\Program Files\MuldeR\LameXP</code>. However, this can be changed by the user during the setup process.</p>
<p><img src="img/lamexp/setup_3a.png" alt="Figure" /></p>
-<h4 id="warning"><span class="header-section-number">3.2.1.1</span> Warning</h4>
+<h4 id="portable-mode-warning"><span class="header-section-number">4.2.1.1</span> Portable Mode Warning</h4>
<p>While the "portable mode" is in effect, it is the <em>user's</em> responsibility to ensure that LameXP will be provided with the proper access rights to save/load its configuration files to/from the LameXP program directory!</p>
-<p>Note that the directories <code>C:\Program Files (x86)</code> and <code>C:\Program Files</code> usually are "protected" by the operating system, so LameXP may <strong>not</strong> be able to write into these directories.</p>
-<h3 id="disable-the-portable-mode"><span class="header-section-number">3.2.2</span> Disable the Portable Mode</h3>
+<p><em>Note:</em> The directories <code>C:\Program Files (x86)</code> and <code>C:\Program Files</code> usually are "protected" by the operating system, so LameXP probably will <strong>not</strong> be able to write into these directories.</p>
+<h3 id="disable-the-portable-mode"><span class="header-section-number">4.2.2</span> Disable the Portable Mode</h3>
<p>If you wish to <em>disable</em> the "portable mode" again, then all you need to do is <strong>renaming</strong> the LameXP program file form <code>LameXP-Portable.exe</code> back to <code>LameXP.exe</code>. You must exit LameXP, before you can rename the program file!</p>
<p><em>Note:</em> After the "portable mode" has been <em>disabled</em>, any configurations files that may have been created in the LameXP installation directory will <strong>no</strong> longer be recognized. Therefore, you can delete these files safely…</p>
-<h2 id="install-the-aac-encoder"><span class="header-section-number">3.3</span> Install the AAC Encoder</h2>
+<h2 id="install-the-aac-encoder"><span class="header-section-number">4.3</span> Install the AAC Encoder</h2>
<p>For legal reasons, the AAC (Advanced Audio Coding) encoder can <strong>not</strong> be included in the official LameXP distribution packages. Therefore, you need to download and install the AAC encoder <em>manually</em>. Don't worry, it's easy!</p>
<p>LameXP can use the <strong>Nero Digital</strong> AAC encoder as well as the <strong>QAAC</strong> (Apple iTunes/QuickTime) encoder. This chapter describes how to set up one of these AAC encoders for use with the LameXP software.</p>
<p><em>Note:</em> If you are uncertain which AAC encoder to choose, please be aware that the QAAC encoder may produce slightly better sound quality, according to <a href="http://listening-tests.hydrogenaud.io/igorc/aac-96-a/results.html">listening tests</a>, while the Nero Digital encoder is less hassle to install.</p>
-<h3 id="nero-digital-aac-encoder"><span class="header-section-number">3.3.1</span> Nero Digital AAC Encoder</h3>
+<h3 id="nero-digital-aac-encoder"><span class="header-section-number">4.3.1</span> Nero Digital AAC Encoder</h3>
<p>First of all, you need to download the Nero AAC encoder from the official Nero Digital web-site. The download is free of charge:</p>
<ul>
<li><a href="http://www.nero.com/eng/company/about-nero/nero-aac-codec.php">http://www.nero.com/eng/company/about-nero/nero-aac-codec.php</a><br /></li>
<p><em>Note:</em> By default, the LameXP installation directory is either <code>C:\Program Files (x86)\MuldeR\LameXP</code> or <code>C:\Program Files\MuldeR\LameXP</code>. However, this can be changed by the user during the setup process.</p>
<p><img src="img/lamexp/setup_4c.png" alt="Figure" /></p>
<p> <br />Once the required Nero AAC files have been put into the proper place, simply <em>restart</em> LameXP in order to enable the AAC encoding support!</p>
-<h3 id="qaac-apple-aac-encoder"><span class="header-section-number">3.3.2</span> QAAC (Apple AAC) Encoder</h3>
+<h3 id="qaac-apple-aac-encoder"><span class="header-section-number">4.3.2</span> QAAC (Apple AAC) Encoder</h3>
<p>Getting the Apple/QuickTime AAC encoder ready involves <em>two</em> separate steps: In the first place we will install the QAAC encoder, and in the second place we will install the Apple AAC encoder libraries.</p>
-<h4 id="install-qaac-encoder"><span class="header-section-number">3.3.2.1</span> Install QAAC Encoder</h4>
+<h4 id="install-qaac-encoder"><span class="header-section-number">4.3.2.1</span> Install QAAC Encoder</h4>
<p>First of all, you need to download the <a href="https://github.com/nu774/qaac">QAAC</a> application, which provides a CLI font-end to the Apple/QuickTime AAC encoder. QAAC is provided as an <em>Add-in</em> for LameXP and is available from the following locations:</p>
<ul>
<li><a href="http://sourceforge.net/projects/lamexp/files/Miscellaneous/Add-ins/qaac/">http://sourceforge.net/projects/lamexp/files/Miscellaneous/Add-ins/qaac/</a><br /></li>
<p> <br />Now open the downloaded ZIP file, e.g. <code>LameXP.qaac-addin.yyyy-mm-dd.zip</code>, with your favourite file archive software (we recommend using <a href="http://www.7-zip.org/">7-Zip</a> or <a href="http://www.rarlab.com/download.htm">WinRAR</a>) to find the required QAAC program files.</p>
<p><em>Note:</em> The LameXP software generally expects the <strong>latest</strong> version of the QAAC add-in; and the QAAC add-in is designed to work with the <strong>latest</strong> version of the LameXP software. Make sure your files are up-to-date!</p>
<p><img src="img/lamexp/setup_5a.png" alt="Figure" /></p>
-<p> <br />Please <em>extract</em> all the three files, the program <code>qaac.exe</code> plus its DLLs <code>libsoxr.dll</code> and <code>libsoxconvolver.dll</code>, into the LameXP installation directory. That is the directory where your LameXP executable file, i.e. the <code>LameXP.exe</code>, is located.</p>
+<p> <br />Please <em>extract</em> all the three files, the program <code>qaac.exe</code> plus its companion DLLs <code>libsoxr.dll</code> and <code>libsoxconvolver.dll</code>, into the LameXP installation directory. That is the directory where your LameXP executable file, i.e. the <code>LameXP.exe</code>, is located.</p>
<p><em>Note:</em> By default, the LameXP installation directory is either <code>C:\Program Files (x86)\MuldeR\LameXP</code> or <code>C:\Program Files\MuldeR\LameXP</code>. However, this can be changed by the user during the setup process.</p>
<p><img src="img/lamexp/setup_5b.png" alt="Figure" /></p>
-<h4 id="install-apple-aac-encoder-libraries"><span class="header-section-number">3.3.2.2</span> Install Apple AAC Encoder Libraries</h4>
+<h4 id="install-apple-aac-encoder-libraries"><span class="header-section-number">4.3.2.2</span> Install Apple AAC Encoder Libraries</h4>
<p>Next, the actual Apple/QuickTime AAC encoder libraries, which are part of the so-called "Apple Application Support" package, need to be installed on your computer. QAAC can <em>not</em> work without these libraries!</p>
<p>The required "Apple Application Support" package is included, for example, in the official setup packages of <em>QuickTime</em> or <em>iTunes</em> for Windows, which can be obtained from the Apple web-site free of charge:</p>
<ul>
<p><img src="img/lamexp/setup_5d.png" alt="Figure" /></p>
<p> <br />Once the QAAC encoder as well as the Apple AAC encoder libraries ("Apple Application Support") have been installed properly, simply <em>restart</em> LameXP in order to enable the AAC encoding support!</p>
<p><em>Note:</em> You may run <code>qaac.exe --check</code> from the <a href="http://en.wikipedia.org/wiki/Cmd.exe">command prompt</a> to ensure that QAAC has been set up correctly. Expected output is <code>qaac 2.xx, CoreAudioToolbox x.x.x.x</code>.</p>
-<h1 id="tutorial-step-by-step-guide"><span class="header-section-number">4</span> Tutorial (Step-by-Step Guide)</h1>
+<h1 id="tutorial-step-by-step-guide"><span class="header-section-number">5</span> Tutorial (Step-by-Step Guide)</h1>
<p>This tutorial will teach you, step by step, how to convert your audio files using the LameXP software. The tutorial assumes that LameXP is already installed on your computer.</p>
-<h2 id="source-files"><span class="header-section-number">4.1</span> Source Files</h2>
+<h2 id="source-files"><span class="header-section-number">5.1</span> Source Files</h2>
<p>First of all, you need to add all <strong>source files</strong> that you want to convert. So switch to the "Source Files" tab, just in case that tab is not active already, and then click the "Add File(s)" button.</p>
<p><img src="img/lamexp/tutorial_1a.png" alt="Figure" /></p>
<p> <br />This will bring up a standard file selection dialogue. Now simply select the files that you want to add and click the "Open" button. You can repeat this step multiple times, e.g. to add files from different directories.</p>
<p> <br />All files you have added, so far, will show up in the list. You can click the "Remove" button to remove a single file from the list or "Clear" to remove them all. Click the "Show details" button to show details about a file.</p>
<p><img src="img/lamexp/tutorial_1c.png" alt="Figure" /></p>
<p> <br /><em>Did you know?</em> Files can also be added via <a href="http://en.wikipedia.org/wiki/Drag_and_drop">Drag & Drop</a>. Just grab the files that you want to add in your Explorer window and drop them onto the LameXP main window (or onto the LameXP "dropbox" widget).</p>
-<h2 id="output-directory"><span class="header-section-number">4.2</span> Output Directory</h2>
+<h2 id="output-directory"><span class="header-section-number">5.2</span> Output Directory</h2>
<p>Next, you need to choose the <strong>output directory</strong>, i.e. the directory where the converted files will be saved. Switch to the "Output Directory" tab and choose the desired output directory from the directory tree view.</p>
<p><em>Note:</em> There are several quick navigation buttons below, which will allow you to jump quickly to your personal "Home" folder, "Desktop" folder and "Music" folder, respectively.</p>
<p><img src="img/lamexp/tutorial_2a.png" alt="Figure" /></p>
<p> <br />The new folder is going to be created inside the current directory and will be selected automatically. You can repeat this step multiple times in order to created nested sub-folders.</p>
<p><img src="img/lamexp/tutorial_2c.png" alt="Figure" /></p>
<p> <br /><em>Did you know?</em> If you enable the "Save output files in the same directory where the input file is located" option, each output file will be saved to the same location where the corresponding source file resides.</p>
-<h2 id="compression-settings"><span class="header-section-number">4.3</span> Compression Settings</h2>
+<h2 id="compression-settings"><span class="header-section-number">5.3</span> Compression Settings</h2>
<p>Finally, you need to choose your <strong>compression settings</strong>. First, and most important, you must decide for an output <em>audio format (encoder)</em>. Depending on your needs and preferences, you can choose between <a href="http://en.wikipedia.org/wiki/MP3">MP3</a>, <a href="http://en.wikipedia.org/wiki/Vorbis">Ogg/Vorbis</a>, <a href="http://en.wikipedia.org/wiki/Opus_%28audio_format%29">Opus</a>, <a href="http://en.wikipedia.org/wiki/Advanced_Audio_Coding">AAC/MP4</a>, <a href="https://xiph.org/flac/">FLAC</a> and others.</p>
<p><em>Note:</em> If you are uncertain which audio format to choose, then <a href="http://lifehacker.com/5927052/whats-the-difference-between-all-these-audio-formats-and-which-one-should-i-use">this article</a> by Lifehacker is a good starting point. Also see the <a href="http://en.wikipedia.org/wiki/Comparison_of_audio_coding_formats">comparison of audio coding formats</a> on Wikipedia. If still uncertain, just go with good old MP3 😉</p>
<p><img src="img/lamexp/tutorial_3a.png" alt="Figure" /></p>
<p><em>Note:</em> If you are uncertain which bitrate or quality-level to choose, bare in mind that a higher bitrate (or a better quality level) results in better audio quality, but also produces larger files – and vice versa. "Level 2" or "192 kbps" is a typical choice for MP3.</p>
<p><img src="img/lamexp/tutorial_3c.png" alt="Figure" /></p>
<p> <br /><em>Did you know?</em> You can click on the "Reset" link at any time in order to reset all available settings for all available encoders to their factory defaults.</p>
-<h2 id="processing"><span class="header-section-number">4.4</span> Processing</h2>
+<h2 id="file-processing"><span class="header-section-number">5.4</span> File Processing</h2>
<p>When everything has been set up properly, the time has come to actually start the encoding process. So simply click the "Encode Now" button in order to get going!</p>
<p><img src="img/lamexp/tutorial_4a.png" alt="Figure" /></p>
<p> <br />This will bring up the "Processing" dialogue. LameXP will now convert all your audio files on the list. Depending on the number of audio files and depending on the performance of your system, this may take several minutes, so please be patient 😉</p>
<p> <br />The "Processing" dialogue is going to turn <em>green</em>, as soon as all encoding jobs have finished successfully. If anything went wrong, e.g. if one of the encoding jobs failed for some reason, it will turn <em>red</em> instead.</p>
<p><img src="img/lamexp/tutorial_4c.png" alt="Figure" /></p>
<p> <br /><em>Did you know?</em> You can double-click on a completed (or failed) job in the list, in order to bring up a dialogue with all details about the specific job. This is especially useful, if something went wrong.</p>
-<h1 id="help-support"><span class="header-section-number">5</span> Help & Support</h1>
+<h1 id="help-support"><span class="header-section-number">6</span> Help & Support</h1>
<p>Before you report any problems that you may have encountered with the LameXP software, please make sure that the problem can be <em>reproduced</em> with the <strong>latest</strong> release version of LameXP!</p>
-<h2 id="download-mirrors"><span class="header-section-number">5.1</span> Download Mirrors</h2>
+<h2 id="download-mirrors"><span class="header-section-number">6.1</span> Download Mirrors</h2>
<p>The latest <em>official</em> release of the LameXP software can be obtained from one of the following <em>official</em> download mirrors:</p>
<ul>
<li><a href="https://github.com/lordmulder/LameXP/releases/latest">https://github.com/lordmulder/LameXP/releases/latest</a><br /></li>
<li><a href="http://www.videohelp.com/tools/LameXP">http://www.videohelp.com/tools/LameXP</a></li>
</ul>
<p> <br />It is <em>highly recommended</em> to download LameXP <em>only</em> from one of the official mirrors listed above. We are <strong>not</strong> responsible for the integrity and trustworthiness of LameXP downloads you may have received from other locations!</p>
-<h2 id="diagnostic-output"><span class="header-section-number">5.2</span> Diagnostic Output</h2>
+<h2 id="diagnostic-output"><span class="header-section-number">6.2</span> Diagnostic Output</h2>
<p>If you want to report any problems that you have encountered with the LameXP software, please provide as much details as possible. <em>Diagnostic output</em> can be especially helpful here!</p>
<ul>
<li><p>If a certain encoding job has failed, you can double-click the failed job in the LameXP "Processing" dialogue, which will bring up a detailed <em>log</em> for that job. Use the "Copy to Clipboard" button to save that information.</p></li>
<li><p>The <a href="http://en.wikipedia.org/wiki/Environment_variable">environment variable</a> <code>MUTILS_LOGFILE</code> may be used to specify a <em>log file</em> that will be created by LameXP. The information that are saved to the log file are the same as those available from the debug console.</p></li>
</ul>
<p> <br /><em>Note:</em> We highly recommend using a web-service like <a href="https://gist.github.com/">Gist</a>, <a href="http://pastie.org/">Pastie</a> or <a href="http://pastebin.com/">Pastebin</a> in order to share your diagnostic information. Please avoid posting long log files directly on the forums!</p>
-<h2 id="bugtracker"><span class="header-section-number">5.3</span> Bugtracker</h2>
+<h2 id="bugtracker"><span class="header-section-number">6.3</span> Bugtracker</h2>
<p>The recommended way to submit <em>bug reports</em> or <em>feature requests</em> to the LameXP developers is using the <em>issue tracking system</em> at our GitHub project site:</p>
<ul>
<li><a href="https://github.com/lordmulder/LameXP/issues">https://github.com/lordmulder/LameXP/issues</a></li>
</ul>
<p> <br /><em>Note:</em> In order to use the issue tracking system, you need to log in with your GitHub account. Creating a GitHub account is easy and completely free of charge, simply click <a href="https://github.com/join">here</a>!</p>
-<h2 id="support-forum"><span class="header-section-number">5.4</span> Support Forum</h2>
+<h2 id="support-forum"><span class="header-section-number">6.4</span> Support Forum</h2>
<p>If you want to discuss the development of the LameXP software, help other users or receive help from other users, please use the LameXP thread at <em>Doom9's</em> Forum:</p>
<ul>
<li><a href="http://forum.doom9.org/showthread.php?t=157726">http://forum.doom9.org/showthread.php?t=157726</a> – English<br /></li>
<li><a href="http://forum.gleitz.info/showthread.php?t=37956">http://forum.gleitz.info/showthread.php?t=37956</a> – German</li>
</ul>
<p> <br /><em>Note:</em> Due to the massive amount of spam attacks, Doom9 has established strict anti-spam measures. Therefore, it takes a few days until your account will be approved.</p>
-<h1 id="developer-center"><span class="header-section-number">6</span> Developer Center</h1>
+<h1 id="developer-center"><span class="header-section-number">7</span> Developer Center</h1>
<p>While LameXP originally was written in Delphi/Pascal, the current version 4 series of the software has been re-written in the <a href="http://en.wikipedia.org/wiki/C%2B%2B"><strong>C++</strong></a> programming language. LameXP v4 uses the <a href="http://www.qt.io/"><em>Qt cross-platform application framework</em></a> and provides full <a href="http://en.wikipedia.org/wiki/Unicode"><em>Unicode</em></a> support. Furthermore, LameXP is tightly coupled with the <a href="https://github.com/lordmulder/MUtilities"><em>MUtilities</em></a> library, a vast collection of "utility" routines and classes to extend the Qt framework. Build files are currently provided for <em>Microsoft Visual Studio</em> only. Linux support is currently provided via <a href="https://www.winehq.org/"><em>Wine</em></a>; a native Linux port of LameXP is planned for a future version.</p>
-<h2 id="source-code-access"><span class="header-section-number">6.1</span> Source Code Access</h2>
+<h2 id="source-code-access"><span class="header-section-number">7.1</span> Source Code Access</h2>
<p>The source code of the <strong>LameXP</strong> software is managed using the <a href="http://git-scm.com/"><em>Git</em></a> version control system. The Git repository can be <em>cloned</em> from one of the official Git mirrors:</p>
<ul>
<li><p><code>git clone git://git.code.sf.net/p/lamexp/code LameXP</code> (<a href="http://sourceforge.net/p/lamexp/code/">Browse</a>)</p></li>
<li><p><code>git clone git://repo.or.cz/MUtilities.git MUtilities</code> (<a href="http://repo.or.cz/w/MUtilities.git">Browse</a>)</p></li>
</ul>
<p> <br /><em>Remarks:</em> In case you are new to Git or want to extend your knowledge, have a look at the <a href="http://git-scm.com/book/en/v2"><em>Pro Git</em></a> book by Scott Chacon! For Windows users, we highly recommend using <a href="http://msysgit.github.com/"><em>MSYS Git</em></a> in conjunction with the superb <a href="http://tortoisegit.googlecode.com/"><em>Tortoise Git</em></a> front-end.</p>
-<h2 id="build-prerequisites"><span class="header-section-number">6.2</span> Build Prerequisites</h2>
+<h2 id="build-prerequisites"><span class="header-section-number">7.2</span> Build Prerequisites</h2>
<p>LameXP is currently being developed and built using the following development tools and libraries:</p>
<ul>
<li><p><a href="http://www.visualstudio.com/en-us/downloads/download-visual-studio-vs.aspx">Visual Studio 2013 Update-4</a>, running on Windows 7 with Service Pack 1</p></li>
<li><p><a href="http://johnmacfarlane.net/pandoc/">Pandoc</a> – the Universal Document Converter</p></li>
<li><p><a href="ftp://ftp.gnupg.org/gcrypt/binary/">GnuPG</a> – the GNU Privacy Guard v1.4.x</p></li>
</ul>
-<h2 id="qt-as-static-libraries"><span class="header-section-number">6.3</span> Qt as Static Libraries</h2>
+<h2 id="qt-as-static-libraries"><span class="header-section-number">7.3</span> Qt as Static Libraries</h2>
<p>In order to create a "fully static" build of LameXP, i.e. a build that does <em>not</em> depend on any "external" DLL files (except for the obligatory operating system DLL's that you cannot get around), you'll need to compile Qt as "static" libraries. The official Qt web-site <em>does</em> provide pre-compiled Qt libraries. However, they only provide DLL versions, they do <em>not</em> provide "static" libraries. Consequently, you need to build the required "static" Qt libraries yourself. The following simple instructions should make it easy to build Qt from the sources and as "static" libraries:</p>
<ol>
<li><p>Make sure <em>Visual Studio 2013</em> with Update-4 (or later) is installed</p></li>
<li><p>Congratulations, you should now be prepared to build the <code>Release_Static</code> configuration of LameXP 😊</p></li>
</ol>
<p> <br /><em>Note:</em> Static libraries only work with the exactly same compiler (version) they were built with!</p>
-<h1 id="f.a.q.-frequently-asked-questions"><span class="header-section-number">7</span> F.A.Q. (Frequently Asked Questions)</h1>
+<h1 id="f.a.q.-frequently-asked-questions"><span class="header-section-number">8</span> F.A.Q. (Frequently Asked Questions)</h1>
<p><strong>TODO</strong></p>
<p> <br /> <br /><strong>EOF</strong></p>
</body>
OSDN Git Service
