From 0057a3d636621271313cdad2502cc5be98462e86 Mon Sep 17 00:00:00 2001
From: LoRd_MuldeR <mulder2@gmx.de>
Date: Mon, 11 Dec 2017 19:59:28 +0100
Subject: [PATCH] Updated changelog.

---
 doc/Changelog.html | 2 +-
 doc/Changelog.md   | 1 +
 doc/Manual.html    | 2 +-
 doc/Manual.md      | 2 +-
 4 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/Changelog.html b/doc/Changelog.html
index 0115d2d6..cc995d38 100644
--- a/doc/Changelog.html
+++ b/doc/Changelog.html
@@ -3,7 +3,7 @@
 h='&#x67;&#x6d;&#120;';a='&#64;';n='&#x6d;&#x75;&#108;&#100;&#x65;&#114;&#50;';e=n+a+h;
 document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'" clas'+'s="em' + 'ail">'+e+'<\/'+'a'+'>');
 // -->
-</script><noscript>&#x6d;&#x75;&#108;&#100;&#x65;&#114;&#50;&#32;&#x61;&#116;&#32;&#x67;&#x6d;&#120;</noscript>&gt; | <a href="http://muldersoft.com/" class="uri">http://muldersoft.com/</a></h2> </header> <nav id="TOC"> <ul> <li><a href="#lamexp-v4.xx-history"><span class="toc-section-number">1</span> LameXP v4.xx History</a><ul> <li><a href="#lamexp-v4.16-unreleased">LameXP v4.16 [UNRELEASED]</a></li> <li><a href="#lamexp-v4.15-2017-05-31">LameXP v4.15 [2017-05-31]</a></li> <li><a href="#lamexp-v4.14-2016-11-19">LameXP v4.14 [2016-11-19]</a></li> <li><a href="#lamexp-v4.13-2015-12-12">LameXP v4.13 [2015-12-12]</a></li> <li><a href="#lamexp-v4.12-2015-10-23">LameXP v4.12 [2015-10-23]</a></li> <li><a href="#lamexp-v4.11-2015-04-05">LameXP v4.11 [2015-04-05]</a></li> <li><a href="#lamexp-v4.10-2014-06-23">LameXP v4.10 [2014-06-23]</a></li> <li><a href="#lamexp-v4.09-2014-01-26">LameXP v4.09 [2014-01-26]</a></li> <li><a href="#lamexp-v4.08-2013-09-04">LameXP v4.08 [2013-09-04]</a></li> <li><a href="#lamexp-v4.07-2013-04-28">LameXP v4.07 [2013-04-28]</a></li> <li><a href="#lamexp-v4.06-2012-11-04">LameXP v4.06 [2012-11-04]</a></li> <li><a href="#lamexp-v4.05-2012-09-03">LameXP v4.05 [2012-09-03]</a></li> <li><a href="#lamexp-v4.04-2012-04-26">LameXP v4.04 [2012-04-26]</a></li> <li><a href="#lamexp-v4.03-2011-11-12">LameXP v4.03 [2011-11-12]</a></li> <li><a href="#lamexp-v4.02-2011-06-14">LameXP v4.02 [2011-06-14]</a></li> <li><a href="#lamexp-v4.01-2011-04-04">LameXP v4.01 [2011-04-04]</a></li> <li><a href="#lamexp-v4.00-2011-02-21">LameXP v4.00 [2011-02-21]</a></li> </ul></li> <li><a href="#lamexp-v3.xx-history"><span class="toc-section-number">2</span> LameXP v3.xx History</a><ul> <li><a href="#lamexp-v3.19-2010-07-12">LameXP v3.19 [2010-07-12]</a></li> <li><a href="#lamexp-v3.18-2010-05-08">LameXP v3.18 [2010-05-08]</a></li> <li><a href="#lamexp-v3.17-2010-02-21">LameXP v3.17 [2010-02-21]</a></li> <li><a href="#lamexp-v3.16-2010-01-26">LameXP v3.16 [2010-01-26]</a></li> <li><a href="#lamexp-v3.15-2009-12-24">LameXP v3.15 [2009-12-24]</a></li> <li><a href="#lamexp-v3.14-2009-12-01">LameXP v3.14 [2009-12-01]</a></li> <li><a href="#lamexp-v3.13-2009-10-21">LameXP v3.13 [2009-10-21]</a></li> <li><a href="#lamexp-v3.12-2009-09-19">LameXP v3.12 [2009-09-19]</a></li> <li><a href="#lamexp-v3.11-2009-06-22">LameXP v3.11 [2009-06-22]</a></li> <li><a href="#lamexp-v3.10-2009-06-11">LameXP v3.10 [2009-06-11]</a></li> <li><a href="#lamexp-v3.09-2009-06-01">LameXP v3.09 [2009-06-01]</a></li> <li><a href="#lamexp-v3.08-2009-03-05">LameXP v3.08 [2009-03-05]</a></li> <li><a href="#lamexp-v3.07-2008-12-24">LameXP v3.07 [2008-12-24]</a></li> <li><a href="#lamexp-v3.06-2008-10-26">LameXP v3.06 [2008-10-26]</a></li> <li><a href="#lamexp-v3.05-2008-10-11">LameXP v3.05 [2008-10-11]</a></li> <li><a href="#lamexp-v3.04-2008-09-26">LameXP v3.04 [2008-09-26]</a></li> <li><a href="#lamexp-v3.03-2008-08-12">LameXP v3.03 [2008-08-12]</a></li> <li><a href="#lamexp-v3.02-2008-08-06">LameXP v3.02 [2008-08-06]</a></li> <li><a href="#lamexp-v3.01-2008-08-01">LameXP v3.01 [2008-08-01]</a></li> <li><a href="#lamexp-v3.00-2008-07-04">LameXP v3.00 [2008-07-04]</a></li> </ul></li> <li><a href="#lamexp-v2.xx-history"><span class="toc-section-number">3</span> LameXP v2.xx History</a><ul> <li><a href="#lamexp-v2.03-2007-08-17">LameXP v2.03 [2007-08-17]</a></li> <li><a href="#lamexp-v2.00-2007-02-19">LameXP v2.00 [2007-02-19]</a></li> </ul></li> <li><a href="#lamexp-v1.xx-history"><span class="toc-section-number">4</span> LameXP v1.xx History</a><ul> <li><a href="#lamexp-v1.00-2004-12-10">LameXP v1.00 [2004-12-10]</a></li> </ul></li> </ul> </nav> <h1 id="lamexp-v4.xx-history"><span class="header-section-number">1</span> LameXP v4.xx History</h1> <h2 id="lamexp-v4.16-unreleased" class="unnumbered">LameXP v4.16 [UNRELEASED]</h2> <ul> <li>Upgraded build environment to Microsoft Visual Studio 2017 with Update-5</li> <li>Updated LAME encoder to v3.100 Final (2017-10-13), compiled with ICL 18.0 and MSVC 14.1</li> <li>Updated mpg123 decoder to v1.25.8 (2017-12-02), compiled with GCC 7.2.0</li> <li>Updated Opus encoder/decoder libraries to v1.2.1-35 (2017-11-16) and Opus-Tools to v0.1.10-9 (2017-05-25)</li> <li>Updated Monkey's Audio binary to v4.33 (2017-12-01), compiled with ICL 18.0 and MSVC 15.5</li> <li>Updated MediaInfo to v17.10 (2017-11-02), compiled with ICL 18.0 and MSVC 14.1</li> <li>Updated GnuPG to v1.4.22 (2017-07-19), compiled with GCC 7.2.0</li> <li>Complete re-write of MediaInfo parsing code, now using XML-based MediaInfo output</li> <li>Improved auto-detection of max. parallel instances on computers with &quot;fast&quot; (i.e. SSD or similar) drive</li> <li>Some improvements to output file name generation code</li> </ul> <h2 id="lamexp-v4.15-2017-05-31" class="unnumbered">LameXP v4.15 [2017-05-31]</h2> <ul> <li>Fixed a bug in auto-rename feature, that caused problems when a meta-tag contained path separators</li> <li>Fixed included MediaInfo binary not working on processor <em>without</em> SSE2 support</li> <li>Improved file name generation from meta-tags containing characters that are forbidden in file names</li> <li>Some improvements for &quot;high DPI&quot; screens: Adjust initial window size according to DPI setting</li> <li>Updated Opus encoder/decoder libraries to v1.2-beta (2017-05-26) and Opus-Tools to v0.1.10 (2017-05-25)</li> <li>Updated MediaInfo to v0.7.95 (2017-05-04), compiled with ICL 17.0 and MSVC 12.0</li> <li>Updated SoX to v14.4.2 (2015-02-22) with Dynamic Audio Normalizer v2.10 (2017-04-14) effect included</li> <li>Updated mpg123 decoder to v1.24.0 (2017-03-02), compiled with GCC 6.3.0</li> <li>Updated FAAD decoder to v2.7 from CVS in order to include latest libFAAD fixes (2016-11-11)</li> <li>Updated Monkey's Audio binary to v4.25 (2017-03-12), compiled with ICL 17.0 and MSVC 14.0</li> <li>Some tweaks to the auto-update function in order to speed-up the update check in most situations</li> </ul> <h2 id="lamexp-v4.14-2016-11-19" class="unnumbered">LameXP v4.14 [2016-11-19]</h2> <ul> <li>Upgraded build environment to Microsoft Visual Studio 2015 with Update-3</li> <li>Fixed the location of temporary intermediate files for SoX-based audio effects</li> <li>Fixed embedding of meta tags with OggEnc2 when reading directly from OGG/FLAC input file</li> <li>Fixed encoding of <em>non</em>-Stereo sources with NeroAAC, when &quot;HE-AAC <em>v2</em> (SBR+PS)&quot; is selected</li> <li>Fixed a bug that would cause the encoding job to fail, when an audio filter is <em>skipped</em></li> <li>Enabled the &quot;built-in&quot; resampler for QAAC encoder</li> <li>The &quot;Algorithm Quality&quot; slider now also affects the QAAC encoder</li> <li>Added &quot;AVX&quot; (Advanced Vector Extensions) to CPU feature detection code</li> <li>Updated Opus encoder/decoder libraries to v1.2-alpha and Opus-Tools to v0.1.9 (2016-11-04)</li> <li>Updated LAME encoder to v3.100 Alpha-2 (2016-01-29), compiled with ICL 15.0 and MSVC 12.0</li> <li>Updated FLAC encoder/decoder to v1.3.1 (2016-10-04), compiled with ICL 17.0 and MSVC 12.0</li> <li>Updated MediaInfo to v0.7.90 (2016-10-31), compiled with ICL 17.0 and MSVC 12.0</li> <li>Updated mpg123 decoder to v1.23.8 (2016-09-27), compiled with GCC 6.2.0</li> <li>Updated ALAC decoder to refalac v1.61 (2016-10-02)</li> <li>Updated WavPack decoder to v4.80.0 (2016-03-28), compiled with ICL 15.0 and MSVC 12.0</li> <li>Updated GnuPG to v1.4.21 (2016-08-17), compiled with GCC 6.1.0</li> <li>Updated QAAC add-in to the to QAAC v2.61 (2016-10-02)</li> <li>Updated FhgAacEnc add-in to &quot;Case&quot; edition (2015-10-24)</li> <li>Improved auto-update function (faster Internet connectivity check)</li> <li>Updated language files (big thank-you to all contributors !!!)</li> </ul> <h2 id="lamexp-v4.13-2015-12-12" class="unnumbered">LameXP v4.13 [2015-12-12]</h2> <ul> <li>Upgraded build environment to Microsoft Visual Studio 2015 with Update-1</li> <li>Apply the original file's &quot;creation&quot; and &quot;last modified&quot; date/time to the output file (optional)</li> <li>Updated Vorbis encoder to OggEnc v2.88 (2015-09-10), using libvorbis v1.3.5 and aoTuV b6.03_2015</li> <li>Updated MediaInfo to v0.7.78 (2015-10-02), compiled with ICL 15.0 and MSVC 12.0</li> <li>Fixed resampling bug with Vorbis encoder, regression in OggEnc v2.87</li> <li>Fixed creation of Monkey's Audio (APE) files, when <strong>no</strong> meta data is being embedded</li> <li>Updated language files (big thank-you to all contributors !!!)</li> </ul> <h2 id="lamexp-v4.12-2015-10-23" class="unnumbered">LameXP v4.12 [2015-10-23]</h2> <ul> <li>Upgraded build environment to Microsoft Visual Studio 2013 with Update-5</li> <li>Updated Qt runtime libraries to v4.8.7 Final (2015-05-25), compiled with MSVC 12.0</li> <li>Added support for building LameXP and MUtilities with Visual Studio 2015</li> <li>Added Hungarian translation, contributed by Zityi's Translator Team &lt;<script type="text/javascript">
+</script><noscript>&#x6d;&#x75;&#108;&#100;&#x65;&#114;&#50;&#32;&#x61;&#116;&#32;&#x67;&#x6d;&#120;</noscript>&gt; | <a href="http://muldersoft.com/" class="uri">http://muldersoft.com/</a></h2> </header> <nav id="TOC"> <ul> <li><a href="#lamexp-v4.xx-history"><span class="toc-section-number">1</span> LameXP v4.xx History</a><ul> <li><a href="#lamexp-v4.16-unreleased">LameXP v4.16 [UNRELEASED]</a></li> <li><a href="#lamexp-v4.15-2017-05-31">LameXP v4.15 [2017-05-31]</a></li> <li><a href="#lamexp-v4.14-2016-11-19">LameXP v4.14 [2016-11-19]</a></li> <li><a href="#lamexp-v4.13-2015-12-12">LameXP v4.13 [2015-12-12]</a></li> <li><a href="#lamexp-v4.12-2015-10-23">LameXP v4.12 [2015-10-23]</a></li> <li><a href="#lamexp-v4.11-2015-04-05">LameXP v4.11 [2015-04-05]</a></li> <li><a href="#lamexp-v4.10-2014-06-23">LameXP v4.10 [2014-06-23]</a></li> <li><a href="#lamexp-v4.09-2014-01-26">LameXP v4.09 [2014-01-26]</a></li> <li><a href="#lamexp-v4.08-2013-09-04">LameXP v4.08 [2013-09-04]</a></li> <li><a href="#lamexp-v4.07-2013-04-28">LameXP v4.07 [2013-04-28]</a></li> <li><a href="#lamexp-v4.06-2012-11-04">LameXP v4.06 [2012-11-04]</a></li> <li><a href="#lamexp-v4.05-2012-09-03">LameXP v4.05 [2012-09-03]</a></li> <li><a href="#lamexp-v4.04-2012-04-26">LameXP v4.04 [2012-04-26]</a></li> <li><a href="#lamexp-v4.03-2011-11-12">LameXP v4.03 [2011-11-12]</a></li> <li><a href="#lamexp-v4.02-2011-06-14">LameXP v4.02 [2011-06-14]</a></li> <li><a href="#lamexp-v4.01-2011-04-04">LameXP v4.01 [2011-04-04]</a></li> <li><a href="#lamexp-v4.00-2011-02-21">LameXP v4.00 [2011-02-21]</a></li> </ul></li> <li><a href="#lamexp-v3.xx-history"><span class="toc-section-number">2</span> LameXP v3.xx History</a><ul> <li><a href="#lamexp-v3.19-2010-07-12">LameXP v3.19 [2010-07-12]</a></li> <li><a href="#lamexp-v3.18-2010-05-08">LameXP v3.18 [2010-05-08]</a></li> <li><a href="#lamexp-v3.17-2010-02-21">LameXP v3.17 [2010-02-21]</a></li> <li><a href="#lamexp-v3.16-2010-01-26">LameXP v3.16 [2010-01-26]</a></li> <li><a href="#lamexp-v3.15-2009-12-24">LameXP v3.15 [2009-12-24]</a></li> <li><a href="#lamexp-v3.14-2009-12-01">LameXP v3.14 [2009-12-01]</a></li> <li><a href="#lamexp-v3.13-2009-10-21">LameXP v3.13 [2009-10-21]</a></li> <li><a href="#lamexp-v3.12-2009-09-19">LameXP v3.12 [2009-09-19]</a></li> <li><a href="#lamexp-v3.11-2009-06-22">LameXP v3.11 [2009-06-22]</a></li> <li><a href="#lamexp-v3.10-2009-06-11">LameXP v3.10 [2009-06-11]</a></li> <li><a href="#lamexp-v3.09-2009-06-01">LameXP v3.09 [2009-06-01]</a></li> <li><a href="#lamexp-v3.08-2009-03-05">LameXP v3.08 [2009-03-05]</a></li> <li><a href="#lamexp-v3.07-2008-12-24">LameXP v3.07 [2008-12-24]</a></li> <li><a href="#lamexp-v3.06-2008-10-26">LameXP v3.06 [2008-10-26]</a></li> <li><a href="#lamexp-v3.05-2008-10-11">LameXP v3.05 [2008-10-11]</a></li> <li><a href="#lamexp-v3.04-2008-09-26">LameXP v3.04 [2008-09-26]</a></li> <li><a href="#lamexp-v3.03-2008-08-12">LameXP v3.03 [2008-08-12]</a></li> <li><a href="#lamexp-v3.02-2008-08-06">LameXP v3.02 [2008-08-06]</a></li> <li><a href="#lamexp-v3.01-2008-08-01">LameXP v3.01 [2008-08-01]</a></li> <li><a href="#lamexp-v3.00-2008-07-04">LameXP v3.00 [2008-07-04]</a></li> </ul></li> <li><a href="#lamexp-v2.xx-history"><span class="toc-section-number">3</span> LameXP v2.xx History</a><ul> <li><a href="#lamexp-v2.03-2007-08-17">LameXP v2.03 [2007-08-17]</a></li> <li><a href="#lamexp-v2.00-2007-02-19">LameXP v2.00 [2007-02-19]</a></li> </ul></li> <li><a href="#lamexp-v1.xx-history"><span class="toc-section-number">4</span> LameXP v1.xx History</a><ul> <li><a href="#lamexp-v1.00-2004-12-10">LameXP v1.00 [2004-12-10]</a></li> </ul></li> </ul> </nav> <h1 id="lamexp-v4.xx-history"><span class="header-section-number">1</span> LameXP v4.xx History</h1> <h2 id="lamexp-v4.16-unreleased" class="unnumbered">LameXP v4.16 [UNRELEASED]</h2> <ul> <li>Upgraded build environment to Microsoft Visual Studio 2017 with Update-5</li> <li>Updated LAME encoder to v3.100 Final (2017-10-13), compiled with ICL 18.0 and MSVC 14.1</li> <li>Updated mpg123 decoder to v1.25.8 (2017-12-02), compiled with GCC 7.2.0</li> <li>Updated Opus encoder/decoder libraries to v1.2.1-35 (2017-11-16) and Opus-Tools to v0.1.10-9 (2017-05-25)</li> <li>Updated Monkey's Audio binary to v4.33 (2017-12-01), compiled with ICL 18.0 and MSVC 15.5</li> <li>Updated WavPack decoder to v5.1.0 (2017-01-20), compiled with ICL 18.0 and MSVC 15.5</li> <li>Updated MediaInfo to v17.10 (2017-11-02), compiled with ICL 18.0 and MSVC 14.1</li> <li>Updated GnuPG to v1.4.22 (2017-07-19), compiled with GCC 7.2.0</li> <li>Complete re-write of MediaInfo parsing code, now using XML-based MediaInfo output</li> <li>Improved auto-detection of max. parallel instances on computers with &quot;fast&quot; (i.e. SSD or similar) drive</li> <li>Some improvements to output file name generation code</li> </ul> <h2 id="lamexp-v4.15-2017-05-31" class="unnumbered">LameXP v4.15 [2017-05-31]</h2> <ul> <li>Fixed a bug in auto-rename feature, that caused problems when a meta-tag contained path separators</li> <li>Fixed included MediaInfo binary not working on processor <em>without</em> SSE2 support</li> <li>Improved file name generation from meta-tags containing characters that are forbidden in file names</li> <li>Some improvements for &quot;high DPI&quot; screens: Adjust initial window size according to DPI setting</li> <li>Updated Opus encoder/decoder libraries to v1.2-beta (2017-05-26) and Opus-Tools to v0.1.10 (2017-05-25)</li> <li>Updated MediaInfo to v0.7.95 (2017-05-04), compiled with ICL 17.0 and MSVC 12.0</li> <li>Updated SoX to v14.4.2 (2015-02-22) with Dynamic Audio Normalizer v2.10 (2017-04-14) effect included</li> <li>Updated mpg123 decoder to v1.24.0 (2017-03-02), compiled with GCC 6.3.0</li> <li>Updated FAAD decoder to v2.7 from CVS in order to include latest libFAAD fixes (2016-11-11)</li> <li>Updated Monkey's Audio binary to v4.25 (2017-03-12), compiled with ICL 17.0 and MSVC 14.0</li> <li>Some tweaks to the auto-update function in order to speed-up the update check in most situations</li> </ul> <h2 id="lamexp-v4.14-2016-11-19" class="unnumbered">LameXP v4.14 [2016-11-19]</h2> <ul> <li>Upgraded build environment to Microsoft Visual Studio 2015 with Update-3</li> <li>Fixed the location of temporary intermediate files for SoX-based audio effects</li> <li>Fixed embedding of meta tags with OggEnc2 when reading directly from OGG/FLAC input file</li> <li>Fixed encoding of <em>non</em>-Stereo sources with NeroAAC, when &quot;HE-AAC <em>v2</em> (SBR+PS)&quot; is selected</li> <li>Fixed a bug that would cause the encoding job to fail, when an audio filter is <em>skipped</em></li> <li>Enabled the &quot;built-in&quot; resampler for QAAC encoder</li> <li>The &quot;Algorithm Quality&quot; slider now also affects the QAAC encoder</li> <li>Added &quot;AVX&quot; (Advanced Vector Extensions) to CPU feature detection code</li> <li>Updated Opus encoder/decoder libraries to v1.2-alpha and Opus-Tools to v0.1.9 (2016-11-04)</li> <li>Updated LAME encoder to v3.100 Alpha-2 (2016-01-29), compiled with ICL 15.0 and MSVC 12.0</li> <li>Updated FLAC encoder/decoder to v1.3.1 (2016-10-04), compiled with ICL 17.0 and MSVC 12.0</li> <li>Updated MediaInfo to v0.7.90 (2016-10-31), compiled with ICL 17.0 and MSVC 12.0</li> <li>Updated mpg123 decoder to v1.23.8 (2016-09-27), compiled with GCC 6.2.0</li> <li>Updated ALAC decoder to refalac v1.61 (2016-10-02)</li> <li>Updated WavPack decoder to v4.80.0 (2016-03-28), compiled with ICL 15.0 and MSVC 12.0</li> <li>Updated GnuPG to v1.4.21 (2016-08-17), compiled with GCC 6.1.0</li> <li>Updated QAAC add-in to the to QAAC v2.61 (2016-10-02)</li> <li>Updated FhgAacEnc add-in to &quot;Case&quot; edition (2015-10-24)</li> <li>Improved auto-update function (faster Internet connectivity check)</li> <li>Updated language files (big thank-you to all contributors !!!)</li> </ul> <h2 id="lamexp-v4.13-2015-12-12" class="unnumbered">LameXP v4.13 [2015-12-12]</h2> <ul> <li>Upgraded build environment to Microsoft Visual Studio 2015 with Update-1</li> <li>Apply the original file's &quot;creation&quot; and &quot;last modified&quot; date/time to the output file (optional)</li> <li>Updated Vorbis encoder to OggEnc v2.88 (2015-09-10), using libvorbis v1.3.5 and aoTuV b6.03_2015</li> <li>Updated MediaInfo to v0.7.78 (2015-10-02), compiled with ICL 15.0 and MSVC 12.0</li> <li>Fixed resampling bug with Vorbis encoder, regression in OggEnc v2.87</li> <li>Fixed creation of Monkey's Audio (APE) files, when <strong>no</strong> meta data is being embedded</li> <li>Updated language files (big thank-you to all contributors !!!)</li> </ul> <h2 id="lamexp-v4.12-2015-10-23" class="unnumbered">LameXP v4.12 [2015-10-23]</h2> <ul> <li>Upgraded build environment to Microsoft Visual Studio 2013 with Update-5</li> <li>Updated Qt runtime libraries to v4.8.7 Final (2015-05-25), compiled with MSVC 12.0</li> <li>Added support for building LameXP and MUtilities with Visual Studio 2015</li> <li>Added Hungarian translation, contributed by Zityi's Translator Team &lt;<script type="text/javascript">
 <!--
 h='&#x67;&#x6d;&#x61;&#x69;&#108;&#46;&#x63;&#x6f;&#x6d;';a='&#64;';n='&#122;&#x69;&#116;&#x79;&#x69;&#x73;&#x6f;&#102;&#116;';e=n+a+h;
 document.write('<a h'+'ref'+'="ma'+'ilto'+':'+e+'" clas'+'s="em' + 'ail">'+e+'<\/'+'a'+'>');
diff --git a/doc/Changelog.md b/doc/Changelog.md
index 325f43a7..df7530d3 100644
--- a/doc/Changelog.md
+++ b/doc/Changelog.md
@@ -11,6 +11,7 @@ LameXP Audio-Encoder Front-End &ndash; Changelog
 * Updated mpg123 decoder to v1.25.8 (2017-12-02), compiled with GCC 7.2.0
 * Updated Opus encoder/decoder libraries to v1.2.1-35 (2017-11-16) and Opus-Tools to v0.1.10-9 (2017-05-25)
 * Updated Monkey's Audio binary to v4.33 (2017-12-01), compiled with ICL 18.0 and MSVC 15.5
+* Updated WavPack decoder to v5.1.0 (2017-01-20), compiled with ICL 18.0 and MSVC 15.5
 * Updated MediaInfo to v17.10 (2017-11-02), compiled with ICL 18.0 and MSVC 14.1
 * Updated GnuPG to v1.4.22 (2017-07-19), compiled with GCC 7.2.0
 * Complete re-write of MediaInfo parsing code, now using XML-based MediaInfo output
diff --git a/doc/Manual.html b/doc/Manual.html
index 7d96f5a6..81a33eea 100644
--- a/doc/Manual.html
+++ b/doc/Manual.html
@@ -23,7 +23,7 @@ GNU General Public License for more details.
 
 You should have received a copy of the GNU General Public License
 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><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="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 &quot;suspicious&quot;, &quot;generic&quot; or &quot;packed&quot;. Those results are <strong>not</strong> 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> &quot;packed&quot; executables of being malware. Nonetheless, using so-called &quot;executable packers&quot;, 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 &quot;packed&quot; 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>, which means that the <em>source codes</em> of LameXP are freely available. Everybody can easily see that there is <strong><em>no</em></strong> malware of any kind included in the LameXP source code! If you do <em>not</em> trust the provided <em>binaries</em> of LameXP, you may build your own binary directly from the LameXP source codes…</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 &quot;behind the scenes&quot; 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 <em>paying customer</em>, you can demand that <em>false positives</em> are fixed promptly. Otherwise, get your money back!</p> <h2 id="performance-issues"><span class="header-section-number">3.2</span> Performance Issues</h2> <p>During the <em>startup procedure</em>, the LameXP software has to perform a number of <em>file-system</em> operations. This can take a few moments. However, the startup procedure should <strong>never</strong> take longer than <em>approximately</em> 5 seconds. Even on our test system – Windows 7 running on an <em>ancient</em> Intel Core2 processor with 4 GB of RAM – the startup procedure takes only about 1.5 seconds. And that is with the &quot;real-time protection&quot; of Microsoft Security Essentials (MSE) enabled! If we disable the MSE &quot;real-time protection&quot; feature, the startup procedure takes less than 0.5 seconds. <em>Unfortunately</em>, it has been brought to our attention, that some other anti-virus products may <em>slow down</em> the startup procedure significantly! Startup delays of up to 20 seconds have been reported by users, which corresponds to a slow down factor of <strong>40×</strong> – caused by the anti-virus software!</p> <p>Consequently, if you think that LameXP is starting up &quot;slow&quot; on your machine, we recommend to <strong>temporarily</strong> <em>disable</em> or <em>uninstall</em> your current anti-virus software. If your anti-virus software has a so-called &quot;real-time protection&quot; or &quot;guard&quot; feature, please be sure to <em>deactivate</em> that feature too! As soon as the anti-virus software has been <em>neutralized</em> and <strong>no</strong> longer affects legitimate applications, please try launching the LameXP software again. If it turns out that the startup procedure of LameXP has become significantly <em>faster</em> when the anti-virus software is <strong>not</strong> interfering, then you know one thing for sure: It is the <em>anti-virus software</em> that was causing the slow down! Please recognize that <em>we</em> can <strong>not</strong> fix this kind of problems. Instead, since the problem is actually a <em>defect</em> of the anti-virus software, please report the problem to the developer of the <em>anti-virus software</em>!</p> <p>Another way of detecting performance issues that are caused by sloppy anti-virus software is monitoring the CPU usage in Task Manager (or <a href="https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx"><em>Process Explorer</em></a>) while LameXP is starting up. Please make sure that you are <strong>not</strong> looking at the &quot;overall&quot; CPU usage, but at the CPU usage caused by the <em>individual</em> processes, and that &quot;show processes from all users&quot; is <em>enabled</em>. Then you will probably notice that <code>LameXP.exe</code> is sitting &quot;idle&quot;, more or less, while some <em>service process</em> belonging to the anti-virus software is &quot;hogging&quot; the CPU. The anti-virus software is hindering LameXP startup! A typical example looks like this:</p> <figure> <img src="img/lamexp/av_gone_mad.png"/> </figure> <p>Please report <em>performance issues</em> to the anti-virus software's developer. Also, when reporting <em>performance issues</em>, please be self-confident! As a <em>paying customer</em>, you can demand that such <em>bugs</em> are fixed promptly. Otherwise, get your money back!</p> <h2 id="anti-virus-conclusions"><span class="header-section-number">3.3</span> Anti-Virus Conclusions</h2> <p>The <strong>code of conduct</strong> regarding problems and annoyances related to so-called &quot;anti-virus&quot; software:</p> <ul> <li><p>If your anti-virus software raises an &quot;alarm&quot; or &quot;warning&quot; while trying to launch the LameXP software or the LameXP setup program, please do <strong>not</strong> panic! In most cases, it is just the anti-virus software that went insane.</p></li> <li><p>Unless the alleged &quot;malware infection&quot; has been confirmed by <strong>multiple</strong> <a href="http://www.virustotal.com/"><em>different</em></a> anti-virus engines, this (almost) certainly is a <a href="http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives"><strong>false positive</strong></a>, i.e. <strong>not</strong> an &quot;infection&quot; at all. Therefore, it can be ignored safely 😊</p></li> <li><p>In the extremely unlikely case that you actually have a <em>confirmed</em> malware infection, please try re-downloading the LameXP software from one of the <strong>official</strong> mirrors first, <em>before</em> you send us any &quot;malware&quot; reports!</p></li> <li><p>If you encounter any <a href="http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives"><strong>false positives</strong></a>, please report these problems to the developer of the <em>defective</em> anti-virus software. <em>We</em> are <strong>not</strong> responsible for this problem (it is a bug in the anti-virus software) and thus <em>we</em> can <strong>not</strong> fix it!</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">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">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>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 &quot;Yes&quot;, if you wish to continue the installation process.</p> <p><em>Note:</em> If you wonder why Windows suggests that the LameXP setup program originates from an &quot;unknown publisher&quot;, despite the fact that it was downloaded from the official web-site, then please the explanation <a href="http://lamexp.sourceforge.net/doc/Manual.html#q-why-are-the-lamexp-binaries-not-digitally-signed">here</a>!</p> <figure> <img src="img/lamexp/setup_1a.png"/> </figure> <p>Now simply follow the instructions of the setup wizard, which will guide you through the installation process…</p> <p><em>Note:</em> Please do <strong>not</strong> change the &quot;Destionation Folder&quot;, unless you know exactly what you are doing. The &quot;Destionation Folder&quot; cannot be changed, when <em>upgrading</em> an existing LameXP installation.</p> <figure> <img src="img/lamexp/setup_1b.png"/> </figure> <p>Congratulation, LameXP has been installed successfully on your computer!</p> <p><em>Note:</em> If you keep the &quot;Run LameXP …&quot; option enabled and click on the &quot;Finish&quot; button, the LameXP software will be launched immediately.</p> <figure> <img src="img/lamexp/setup_1c.png"/> </figure> <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> <figure> <img src="img/lamexp/setup_2a.png"/> </figure> <p>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><em>Note:</em> It is very important that you have write-access to the chosen destination directory. So make sure that you choose a directory where the required access rights are granted!</p> <figure> <img src="img/lamexp/setup_2b.png"/> </figure> <p>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> <figure> <img src="img/lamexp/setup_2c.png"/> </figure> <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> &quot;portable version&quot; or &quot;portable edition&quot; of the LameXP software. Instead, <strong>all</strong> versions of the LameXP software always <em>are</em> &quot;portable&quot; – 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 &quot;out of the box&quot;. 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 &quot;portable mode&quot;, which can be enabled or disabled at any time. By default, i.e. when the &quot;portable mode&quot; 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 &quot;portable mode&quot; is <em>enabled</em>.</p> <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 &quot;portable mode&quot; 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> <figure> <img src="img/lamexp/setup_3a.png"/> </figure> <h4 id="portable-mode-warning" class="unnumbered">Portable Mode Warning</h4> <p>While the &quot;portable mode&quot; 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><em>Note:</em> The directories <code>C:\Program Files (x86)</code> and <code>C:\Program Files</code> usually are &quot;protected&quot; 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 &quot;portable mode&quot; 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 &quot;portable mode&quot; 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">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">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 or one of the mirrors:</p> <ul> <li><a href="http://www.videohelp.com/software/Nero-AAC-Codec" class="uri">http://www.videohelp.com/software/Nero-AAC-Codec</a></li> <li><a href="http://www.free-codecs.com/download/Nero_AAC_Codec.htm" class="uri">http://www.free-codecs.com/download/Nero_AAC_Codec.htm</a></li> <li><a href="http://www.majorgeeks.com/files/details/nero_aac_codec_(formerly_nero_digital_audio).html" class="uri">http://www.majorgeeks.com/files/details/nero_aac_codec_(formerly_nero_digital_audio).html</a></li> <li><a href="http://ftp6.nero.com/tools/NeroAACCodec-1.5.1.zip" class="uri">http://ftp6.nero.com/tools/NeroAACCodec-1.5.1.zip</a></li> </ul> <p><em>Note:</em> Although the ZIP file is sometimes called <code>NeroAACCodec-1.5.1.zip</code>, it may actually contains version <strong>1.5.4.0</strong> of the Nero AAC encoder software. Check the included <code>changelog.txt</code> to verify this!</p> <figure> <img src="img/lamexp/setup_4a.png"/> </figure> <p>Now open the downloaded ZIP file 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>) and navigate to the &quot;win32&quot; sub-directory.</p> <figure> <img src="img/lamexp/setup_4b.png"/> </figure> <p>Finally, <em>extract</em> all the three files <code>neroAacDec.exe</code>, <code>neroAacEnc.exe</code> and <code>neroAacTag.exe</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> <figure> <img src="img/lamexp/setup_4c.png"/> </figure> <p>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">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" class="unnumbered">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/" class="uri">http://sourceforge.net/projects/lamexp/files/Miscellaneous/Add-ins/qaac/</a></li> <li><a href="http://muldersoft.com/misc/lamexp/add-ins/qaac/" class="uri">http://muldersoft.com/misc/lamexp/add-ins/qaac/</a></li> </ul> <p>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> <figure> <img src="img/lamexp/setup_5a.png"/> </figure> <p>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> <figure> <img src="img/lamexp/setup_5b.png"/> </figure> <h4 id="install-apple-aac-encoder-libraries" class="unnumbered">Install Apple AAC Encoder Libraries</h4> <p>Next, the actual Apple/QuickTime AAC encoder libraries, which are part of the so-called &quot;Apple Application Support&quot; package, need to be installed on your computer. QAAC can <em>not</em> work without these libraries!</p> <p>The required &quot;Apple Application Support&quot; 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> <li><a href="https://www.apple.com/quicktime/download/" class="uri">https://www.apple.com/quicktime/download/</a></li> <li><a href="https://www.apple.com/itunes/download/" class="uri">https://www.apple.com/itunes/download/</a></li> </ul> <p>Since you usually do <strong>not</strong> want to <em>install</em> the complete QuickTime (or iTunes) software on your computer, please only <em>download</em> the QuickTime (or iTunes) setup package, but do <strong>not</strong> actually <em>run</em> the installer!</p> <p>Instead, open the QuickTimer setup program, i.e. <code>QuickTimeInstaller.exe</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>) and <em>extract</em> the required <code>AppleApplicationSupport.msi</code> package.</p> <figure> <img src="img/lamexp/setup_5c.png"/> </figure> <p>After the &quot;Apple Application Support&quot; setup package has been extracted, you can launch it by double-clicking on the <code>AppleApplicationSupport.msi</code> file. Then simply follow the installer's instructions!</p> <p><em>Note:</em> If you do <strong>not</strong> want to install the &quot;Apple Application Support&quot; software at all, there is an <em>alternative</em> method, that will extract only the required DLL files from the MSI package. See <a href="https://forum.doom9.org/showpost.php?p=1718529&amp;postcount=1221"><em>here</em></a> for details…</p> <figure> <img src="img/lamexp/setup_5d.png"/> </figure> <p>Once the QAAC encoder as well as the Apple AAC encoder libraries (&quot;Apple Application Support&quot;) 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">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">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 &quot;Source Files&quot; tab, just in case that tab is not active already, and then click the &quot;Add File(s)&quot; button.</p> <figure> <img src="img/lamexp/tutorial_1a.png"/> </figure> <p>This will bring up a standard file selection dialogue. Now simply select the files that you want to add and click the &quot;Open&quot; button. You can repeat this step multiple times, e.g. to add files from different directories.</p> <figure> <img src="img/lamexp/tutorial_1b.png"/> </figure> <p>All files you have added, so far, will show up in the list. You can click the &quot;Remove&quot; button to remove a single file from the list or &quot;Clear&quot; to remove them all. You can also click the &quot;Show details&quot; button to show details about the selected file.</p> <figure> <img src="img/lamexp/tutorial_1c.png"/> </figure> <p>If you want to add an <em>entire</em> directory, you can select &quot;Open Folder&quot; from the &quot;File&quot; menu, which will bring up a directory selection dialogue. &quot;Open Folder Recursively&quot; works in a similar way, but also includes <em>all</em> sub-directories.</p> <figure> <img src="img/lamexp/tutorial_1d.png"/> </figure> <p><em>Did you know?</em> Files can also be added via <a href="http://en.wikipedia.org/wiki/Drag_and_drop">Drag &amp; 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 &quot;dropbox&quot; widget).</p> <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 &quot;Output Directory&quot; 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 &quot;Home&quot; folder, &quot;Desktop&quot; folder and &quot;Music&quot; folder, respectively.</p> <figure> <img src="img/lamexp/tutorial_2a.png"/> </figure> <p>Sometimes you may wish to store the converted files in a <em>new</em> (sub-)folder. In this case, simply click the &quot;Make New Folder&quot; button, enter the desired folder name and hit the &quot;OK&quot; button.</p> <figure> <img src="img/lamexp/tutorial_2b.png"/> </figure> <p>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> <figure> <img src="img/lamexp/tutorial_2c.png"/> </figure> <p><em>Did you know?</em> If you enable the &quot;Save output files in the same directory where the input file is located&quot; 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">5.3</span> Compression Settings</h2> <p>Finally, you need to choose your <strong>compression settings</strong>. Most important, you must decide for an output <em>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> <figure> <img src="img/lamexp/tutorial_3a.png"/> </figure> <p>Once you have decided for an audio format, you need to choose a <em>rate-control</em> mode next. This controls how the bits are allocated for the compressed audio files. The available rate-control modes are <em>CBR</em>, <em>VBR</em> and <em>ABR</em>:</p> <ul> <li><p>CBR (constant bitrate) uses a <em>fixed</em> bitrate, i.e. each segment of the file receives the exactly same amount of bits, regardless of its contents. This comes at the advantage that the resulting file size is perfectly predictable. However, because the bitrate can <em>not</em> be adapted to the contents of the file at all, this generally is the <em>least</em> favorable mode!</p></li> <li><p>VBR (quality-base variable bitrate) mode adapts the bitrate to the contents of the file. Each segment of the file receives as many bits as are required to hit the target quality level. This means that &quot;complex&quot; segments of the file will end up with a higher bitrate than more &quot;simple&quot; segments. The bits will be used where they are actually needed. However, because the bitrate varies strongly depending on the contents of the file, the resulting file size is completely unpredictable!</p></li> <li><p>ABR (average bitrate) mode can be understood as a &quot;middle course&quot; between VBR and CBR mode. Similar to VBR mode, ABR mode adapts the bitrate to the contents of the file. But, at the same time, similar to CBR mode, ABR mode limits the bitrate variation in order to hit the specified target <em>average</em> bitrate, i.e. the resulting file size <em>is</em> predictable.</p></li> </ul> <p><em>Note:</em> If you are uncertain which rate-control mode to chose, the rule of thumb is that VBR mode should be preferred over ABR mode when possible. And CBR mode should be avoided. See also Wikipedia's article on <a href="http://en.wikipedia.org/wiki/Variable_bitrate">variable bitrate</a> encoding.</p> <figure> <img src="img/lamexp/tutorial_3b.png"/> </figure> <p>Last but not least, you need to choose the desired target <em>bitrate</em> (kbps) or the desired <em>quality-level</em>. Put simply, this controls the &quot;quality vs. file size&quot; trade-off. You choose a target quality-level in case of VBR mode. And you choose a target (average) bitrate in case of ABR or CBR mode. A <em>higher</em> target bitrate or a <em>higher</em> target quality level results in improved audio quality, but also comes at the cost of larger files. Conversely, a <em>lower</em> target bitrate or a <em>lower</em> target quality level results in smaller files, but also comes at the cost of reduced audio quality. The &quot;optimal&quot; setting highly depends on your personal preferences.</p> <p><em>Note:</em> If you are uncertain which bitrate or quality-level to choose, &quot;Level 2&quot; (VBR) or &quot;192 kbps&quot; (ABR) is a common choice for MP3. If the size of the resulting file is <em>not</em> a primary concern, you can go with &quot;Level 0&quot; (VBR) or &quot;320 kbps&quot; (ABR) right away.</p> <figure> <img src="img/lamexp/tutorial_3c.png"/> </figure> <p><em>Did you know?</em> You can click the &quot;Reset&quot; link in order to reset <em>all</em> compression settings for <em>all</em> encoders to their factory defaults.</p> <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 &quot;Encode Now&quot; button in order to get going!</p> <figure> <img src="img/lamexp/tutorial_4a.png"/> </figure> <p>This will bring up the &quot;Processing&quot; 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><em>Note:</em> In order to leverage the power &quot;multi-core&quot; processors and thus massively speed-up the encoding process, LameXP will run multiple encoding jobs in parallel – provided that your system has multiple processor cores and that there are enough encoding jobs left in the queue.</p> <figure> <img src="img/lamexp/tutorial_4b.png"/> </figure> <p>The &quot;Processing&quot; 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> <figure> <img src="img/lamexp/tutorial_4c.png"/> </figure> <p><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="command-line-usage"><span class="header-section-number">6</span> Command-line Usage</h1> <p>Additional <strong><a href="http://en.wikipedia.org/wiki/Command-line_interface">command-line</a> options</strong> may be passed to LameXP when launching the application. You may do so, for example, by typing the complete command-line into the <a href="http://en.wikipedia.org/wiki/Cmd.exe"><em>command prompt</em></a> or by creating a <a href="http://en.wikipedia.org/wiki/File_shortcut"><em>shortcut</em></a> with the desired command-line options. The basic command-line syntax of LameXP is as follows: Each command-line option has to start with a <code>--</code> prefix. So if you intend to pass the option called &quot;foo&quot;, then you actually need to type <code>--foo</code>. Furthermore, while some command-line options are just <em>flags</em>, i.e. they can either be present or not (but that's it!), there also are command-line options that take an <em>argument</em>. The argument is <em>appended</em> directly to the option name to which it belongs to, but a <code>=</code> sign <strong>must</strong> to be inserted as a separator. If, for example, you wish to set the command-line option &quot;foo&quot; to an argument value of &quot;bar&quot;, then the proper syntax is <code>--foo=bar</code>. Sometimes your argument value may contain <em>whitespaces</em> though, in which case the <em>whole</em> command-line option (name + argument) <strong>must</strong> be enclosed with double quotes. For example, in order to set the option &quot;foo&quot; to a value of &quot;C:\Some File.bar&quot; (note the space character between &quot;Some&quot; and &quot;File&quot;), the proper syntax is <code>&quot;--foo=C:\Some File.bar&quot;</code>. Last but not least, please note that the <em>same</em> command-line option may appear <em>multiple</em> times on the command-line – whether that actually makes any sense depends on the individual option though.</p> <h2 id="add-files-andor-folders"><span class="header-section-number">6.1</span> Add Files and/or Folders</h2> <p>Command-line options for adding files and/or folders:</p> <ul> <li><p><code>--add=filename</code><br/> Adds the file specified by <em>filename</em> to the source files list. The <em>filename</em> should be a <a href="http://en.wikipedia.org/wiki/Fully_qualified_name#Filenames_and_paths">fully-qualified</a> path. If you wish to add multiple files at once, you can simply include this option multiple times.</p></li> <li><p><code>--add-folder=directory</code><br/> Adds <em>all</em> supported files from the directory specified by <em>directory</em> to the source files list. The <em>directory</em> should be a <a href="http://en.wikipedia.org/wiki/Fully_qualified_name#Filenames_and_paths">fully-qualified</a> path. Sub-directories are <strong>not</strong> considered.</p></li> <li><p><code>--add-recursiver=directory</code><br/> This option works just like the &quot;add-folder&quot; option, except that it works recursively, i.e. it <em>does</em> take into account sub-directories. Use this option with care, since a whole lot of files may be added.</p></li> </ul> <h3 id="examples"><span class="header-section-number">6.1.1</span> Examples</h3> <p>Here are some <em>examples</em> on how to use the above command-line options correctly:</p> <ul> <li><p>Add one file:<br/> <code>LameXP.exe &quot;--add=C:\Some Folder\Some File.mp3&quot;</code></p></li> <li><p>Add multiple files at once:<br/> <code>LameXP.exe &quot;--add=C:\Some Folder\File #1.mp3&quot; &quot;--add=C:\Some Folder\File #2.mp3&quot; &quot;--add=C:\Some Folder\File #3.mp3&quot;</code></p></li> <li><p>Add a whole directory:<br/> <code>LameXP.exe &quot;--add-folder=C:\Some Folder&quot;</code></p></li> </ul> <h2 id="gui-adjustment-options"><span class="header-section-number">6.2</span> GUI Adjustment Options</h2> <p>Command-line options for adjusting the graphical user-interface:</p> <ul> <li><p><code>--huge-font</code><br/> Set the font scaling factor to 150%. Use this if you want <em>much</em> larger fonts.</p></li> <li><p><code>--big-font</code><br/> Set the font scaling factor to 125%. Use this if you want <em>somewhat</em> larger fonts.</p></li> <li><p><code>--small-font</code><br/> Set the font scaling factor to 87.5%. Use this if you want <em>somewhat</em> smaller fonts.</p></li> <li><p><code>--tiny-font</code><br/> Set the font scaling factor to 75%. Use this if you want <em>much</em> smaller fonts.</p></li> </ul> <h2 id="options-for-debugging"><span class="header-section-number">6.3</span> Options for Debugging</h2> <p>Command-line options that are intended for testing and debugging:</p> <ul> <li><p><code>--console</code><br/> Enable the LameXP debug console. Use this option with &quot;release&quot; builds of LameXP, where the console is hidden by default.</p></li> <li><p><code>--no-console</code><br/> The opposite of the &quot;console&quot; option: Disable the LameXP debug console. Use this option with &quot;pre-release&quot; (beta) builds of LameXP, where the console is visible by default.</p></li> <li><p><code>--force-cpu-no-64bit</code><br/> Treat the CPU as if it did <strong>not</strong> support <a href="http://en.wikipedia.org/wiki/X86-64">64-Bit (x64)</a> applications, even when it actually does so.</p></li> <li><p><code>--force-cpu-no-sse</code><br/> Treat the CPU as if it did <strong>not</strong> support any <a href="http://en.wikipedia.org/wiki/Streaming_SIMD_Extensions">SSE</a> extensions (SSE, SSE2, SSE3, SSSE3, SSSE4, etc), even when it actually does so.</p></li> <li><p><code>--force-cpu-no-intel</code><br/> Treat the CPU as if it was a <em>non</em>-Intel processor, even when the vendor tag indicates an Intel processor.</p></li> <li><p><code>--ignore-compat-mode</code><br/> Do <strong>not</strong> check whether the application is running with &quot;compatibility mode&quot; enabled. It's still <em>not</em> recommended to run with compatibility mode enabled!</p></li> </ul> <h2 id="miscellaneous-options"><span class="header-section-number">6.4</span> Miscellaneous Options</h2> <p>Miscellaneous command-line options that may come in handy in certain situations:</p> <ul> <li><p><code>--kill</code><br/> Exit all running instances of LameXP.</p></li> <li><p><code>--force-kill</code><br/> Exit all running instances of LameXP as quickly as possible, even if that incurs data loss. Use with extreme care!</p></li> </ul> <h1 id="help-support"><span class="header-section-number">7</span> Help &amp; 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">7.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" class="uri">https://github.com/lordmulder/LameXP/releases/latest</a></li> <li><a href="http://sourceforge.net/projects/lamexp/files/" class="uri">http://sourceforge.net/projects/lamexp/files/</a></li> <li><a href="https://lamexp.codeplex.com/releases/" class="uri">https://lamexp.codeplex.com/releases/</a></li> <li><a href="https://bitbucket.org/muldersoft/lamexp/downloads" class="uri">https://bitbucket.org/muldersoft/lamexp/downloads</a></li> <li><a href="https://www.assembla.com/spaces/lamexp/documents" class="uri">https://www.assembla.com/spaces/lamexp/documents</a></li> <li><a href="http://www.free-codecs.com/lamexp_download.htm" class="uri">http://www.free-codecs.com/lamexp_download.htm</a></li> <li><a href="http://www.videohelp.com/tools/LameXP" class="uri">http://www.videohelp.com/tools/LameXP</a></li> </ul> <p>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">7.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 &quot;Processing&quot; dialogue, which will bring up a detailed <em>log</em> for that job. Use the &quot;Copy to Clipboard&quot; button to save that information.</p></li> <li><p>You can launch the LameXP application with the additional <a href="http://en.wikipedia.org/wiki/Command-line_interface">command-line</a> parameter <code>--console</code> in order to enable the LameXP <em>debug console</em>, which provides many information on what is going on &quot;behind the scenes&quot;.</p></li> <li><p>If the debug console is <strong>not</strong> enabled, you may still use the <a href="http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx"><em>DebugView</em></a> utility, by Mark Russinovich, in order to show and/or capture LameXP's diagnostic output.</p></li> <li><p>In any case, 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 saved to the log file are the same as those available from the debug console.</p></li> </ul> <p><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">7.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" class="uri">https://github.com/lordmulder/LameXP/issues</a></li> </ul> <p><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">7.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" class="uri">http://forum.doom9.org/showthread.php?t=157726</a> – English</li> <li><a href="http://forum.gleitz.info/showthread.php?t=37956" class="uri">http://forum.gleitz.info/showthread.php?t=37956</a> – German</li> </ul> <p><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">8</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 &quot;utility&quot; 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">8.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 https://github.com/lordmulder/LameXP.git LameXP</code> (<a href="https://github.com/lordmulder/LameXP">Browse</a>)</p></li> <li><p><code>git clone https://git01.codeplex.com/lamexp LameXP</code> (<a href="https://lamexp.codeplex.com/SourceControl/latest">Browse</a>)</p></li> <li><p><code>git clone https://bitbucket.org/muldersoft/lamexp.git LameXP</code> (<a href="https://bitbucket.org/muldersoft/lamexp/src">Browse</a>)</p></li> <li><p><code>git clone git://git.assembla.com/lamexp.git LameXP</code> (<a href="https://www.assembla.com/code/lamexp/git/nodes">Browse</a>)</p></li> <li><p><code>git clone https://gitlab.com/lamexp/lamexp.git LameXP</code> (<a href="https://gitlab.com/lamexp/lamexp/tree/master">Browse</a>)</p></li> <li><p><code>git clone git://repo.or.cz/LameXP.git LameXP</code> (<a href="http://repo.or.cz/w/LameXP.git">Browse</a>)</p></li> </ul> <p>The source code of the <strong>MUtilities</strong> library 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/mutilities/code MUtilities</code> (<a href="http://sourceforge.net/p/mutilities/code/">Browse</a>)</p></li> <li><p><code>git clone https://github.com/lordmulder/MUtilities.git MUtilities</code> (<a href="https://github.com/lordmulder/MUtilities">Browse</a>)</p></li> <li><p><code>git clone https://git01.codeplex.com/mutilities MUtilities</code> (<a href="https://mutilities.codeplex.com/SourceControl/latest">Browse</a>)</p></li> <li><p><code>git clone https://bitbucket.org/muldersoft/mutilities.git MUtilities</code> (<a href="https://bitbucket.org/muldersoft/mutilities/src">Browse</a>)</p></li> <li><p><code>git clone git://git.assembla.com/mutilities.git MUtilities</code> (<a href="https://www.assembla.com/code/mutilities/git/nodes">Browse</a>)</p></li> <li><p><code>git clone https://gitlab.com/mutilities/mutilities.git MUtilities</code> (<a href="https://gitlab.com/mutilities/mutilities/tree/master">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><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">8.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="https://www.visualstudio.com/">Visual Studio 2015 Update-1</a>, running on Windows 10 x64 (v1511)</p></li> <li><p><a href="http://download.qt.io/archive/qt/4.8/">Qt libraries 4.8.7</a> for Windows (our <em>pre-compiled</em> Qt libraries for Visual Studio 2015 can be found <a href="http://sourceforge.net/projects/lamexp/files/Miscellaneous/Qt%20Libraries/"><strong>here</strong></a>)</p></li> <li><p><a href="https://vld.codeplex.com/">Visual Leak Detector</a>, open-source memory leak detection system for Visual C++</p></li> <li><p>Windows Platform SDK v7.1A, included with Visual Studio 2015 or Visual Studio 2013</p></li> <li><p>The minimum supported <em>build</em> platform is Windows 7 (x86 and x64)</p></li> </ul> <p>In order to create LameXP release packages, using the included deployment scripts, you need the following additional tools:</p> <ul> <li><p><a href="http://www.7-zip.org/">7-Zip</a> – file archiver with a high compression ratio</p></li> <li><a href="http://nsis.sourceforge.net/">NSIS</a> – Nullsoft Scriptable Install System (<a href="https://github.com/jimpark/unsis/releases"><em>Unicode version</em></a> recommended!) <ul> <li><a href="http://nsis.sourceforge.net/StdUtils_plug-in">StdUtils</a> plug-in</li> <li><a href="http://nsis.sourceforge.net/LockedList_plug-in">LockedList</a> plug-in</li> <li><a href="http://nsis.sourceforge.net/Inetc_plug-in">Inetc</a> plug-in</li> <li><a href="http://forums.winamp.com/showthread.php?t=329990">Aero</a> plug-in</li> <li><a href="http://nsis.sourceforge.net/SelfDel_plug-in">SelfDel</a> plug-in</li> </ul></li> <li><p><a href="http://upx.sourceforge.net/">UPX</a> – the Ultimate Packer for eXecutables</p></li> <li><p><a href="http://johnmacfarlane.net/pandoc/">Pandoc</a> – the Universal Document Converter</p></li> <li><p><a href="https://www.gpg4win.de/">GnuPG</a> – the GNU Privacy Guard (Gpg4win)</p></li> </ul> <h2 id="directory-layout"><span class="header-section-number">8.3</span> Directory Layout</h2> <p>In order to build LameXP using the provided project/solution files or the provided deployment script, please make sure you have the following directory layout, where <code>&lt;sources_root&gt;</code> is a new/empty directory:</p> <ul> <li><code>&lt;sources_root&gt;\LameXP_Qt</code> – the <em>LameXP</em> &quot;main&quot; project</li> <li><code>&lt;sources_root&gt;\Prerequisites</code> – prerequisites to build LameXP</li> <li><code>&lt;sources_root&gt;\MUtilities</code> – the <em>MUtilities</em> library</li> </ul> <p>The <em>Qt</em> libraries need to be located at the following location, where the <code>&lt;toolset_version&gt;</code> identifies your compiler version (e.g. <code>v140_xp</code> for VS2015) and the <code>&lt;build_type&gt;</code> identifies the build configuration (<code>Shared</code>, <code>Static</code> or <code>Debug</code>):</p> <ul> <li><code>&lt;sources_root&gt;\Prerequisites\Qt4\&lt;toolset_version&gt;\&lt;build_type&gt;</code></li> </ul> <h2 id="environment-variables"><span class="header-section-number">8.4</span> Environment variables</h2> <p>In order to build LameXP using the provided project/solution files or the provided deployment script, make sure the following environment variables are configured on your system:</p> <ul> <li><code>QTDIR</code> – points to your Qt installation directory, such that <code>%QTDIR%\bin\moc.exe</code> and friends exist</li> </ul> <h2 id="using-the-deployment-script"><span class="header-section-number">8.5</span> Using the deployment script</h2> <p>In order to create LameXP release packages, using the included deployment scripts, <strong>copy</strong> the <em>configuration</em> template file <code>buildenv.template.txt</code>, located at <code>&lt;sources_root&gt;\LameXP_Qt\etc\Deployment</code>, to the file <code>buildenv.txt</code> in the <em>same</em> directory. Now edit <em>your</em> <code>buildenv.txt</code> and adjust all the path variables as needed. All paths must be set up correctly, otherwise the build process is going to fail! Once everything has been set up, you can run <code>release.bat</code> or <code>release_static.bat</code> in order to create a new release package.</p> <h2 id="qt-as-static-libraries"><span class="header-section-number">8.6</span> Qt as Static Libraries</h2> <p>In order to create a &quot;fully static&quot; build of LameXP, i.e. a build that does <em>not</em> depend on any &quot;external&quot; DLL files (except for the obligatory operating system DLL's that you cannot get around), you'll need to compile Qt as &quot;static&quot; 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 &quot;static&quot; libraries. Consequently, you need to build the required &quot;static&quot; Qt libraries yourself. The following simple instructions should make it easy to build Qt from the sources and as &quot;static&quot; libraries:</p> <ol> <li><p>Make sure <em>Visual Studio 2015</em> with Update-1 (or later) is installed</p></li> <li><p>Make sure <em>Strawberry Perl </em>for Windows and <em>Python 2.7</em> are installed</p></li> <li><p>Download and extract the <em>Qt 4.8.x</em> source code package (e.g. to <code>C:\QtSources\4.8.x</code>)</p></li> <li><p>Edit the <em>qmake</em> configuration file (e.g. <code>mkspecs\win32-msvc2015\qmake.conf</code>) from your Qt Sources directory as follows:</p> <ul> <li>Edit #1: <ul> <li>⇐ <code>QMAKE_CFLAGS_RELEASE = -O2 -MD</code></li> <li>⇒ <code>QMAKE_CFLAGS_RELEASE = -O2 -MT &lt;more optimization flags here&gt;</code></li> </ul></li> <li>Edit #2: <ul> <li>⇐ <code>QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -O2 -MD -Zi</code></li> <li>⇒ <code>QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -O2 -MT -Zi &lt;more optimization flags here&gt;</code></li> </ul></li> </ul></li> <li><p>Open a new command window (<code>cmd.exe</code>) – use this very same console for all upcoming steps!</p></li> <li><p>Add <em>Strawberry Perl</em> to your PATH (e.g. <code>set PATH=C:\strawberry\perl\bin;%PATH%</code>)</p></li> <li><p>Add <em>Python 2.7</em> to your PATH (e.g. <code>set PATH=C:\python27;%PATH%</code>)</p></li> <li><p>Run <code>vcvarsall.bat x86</code> form your Visual C++ install directory - within the same console!</p></li> <li><p>Change the current directory to the <em>Qt Sources</em> path (e.g. <code>C:\QtSources\4.8.x</code>)</p></li> <li><p>Run <code>configure.exe -release -static -ltcg -qt-zlib -qt-libpng -qt-libjpeg -qt-libtiff -qt-libmng</code></p></li> <li><p>Now the makefiles should have been generated, so simply enter <code>nmake /B</code> and be patient - voilà!</p></li> <li><p>The build process is going to take good amount of time. Once it is done, make sure you got all needed libs:</p> <ul> <li><code>lib\qtmain.lib</code></li> <li><code>lib\QtCore.lib</code></li> <li><code>lib\QtGui.lib</code></li> <li><code>lib\QtSvg.lib</code></li> <li><code>lib\QtXml.lib</code></li> <li><code>plugins\imageformats\qico.lib</code></li> <li><code>plugins\imageformats\qsvg.lib</code></li> <li><code>plugins\imageformats\qtga.lib</code></li> </ul></li> <li><p>Put all the static *.lib files into the <code>&lt;sources_root&gt;\Prerequisites\Qt4\&lt;toolset_version&gt;\Static\lib</code> directory</p></li> <li><p>ImageFormat plugins go to <code>&lt;sources_root&gt;\Prerequisites\Qt4\&lt;toolset_version&gt;\plugins\imageformats</code></p></li> <li><p>Congratulations, you should now be prepared to build the <code>Release_Static</code> configuration of LameXP 😊</p></li> </ol> <p><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">9</span> F.A.Q. (Frequently Asked Questions)</h1> <p>This section tries to answer some of the most frequently asked questions. So if you have a question, please carefully read this section, before you send the question to us via email or before you open a new support ticket 😉</p> <h2 id="q-do-i-have-to-pay-for-using-or-obtaining-lamexp"><span class="header-section-number">9.1</span> Q: Do I have to pay for using or obtaining LameXP?</h2> <p><strong>A:</strong> Nope. LameXP is <a href="http://en.wikipedia.org/wiki/Free_software">free software</a>. You may use it <strong><em>free of charge</em></strong> and for any purpose, including commercial purposes, according to the terms of the <a href="GNU%20General%20Public%20License"><em>GNU General Public License</em></a>. The developers of LameXP will <strong>never</strong> ask you to pay for using the LameXP software. Also, several <strong><em>free</em></strong> download mirrors are provided. However, it was brought to our attention, that there are some <em>third-party</em> web-sites which offer <em>payed</em> downloads of LameXP, or provide LameXP downloads that have been infected with Adware – we do <strong>not</strong> cooperate with any of these web-sites! Therefore, please do <strong>not</strong> pay money for using or obtaining the LameXP software; the developers of LameXP will <strong>not</strong> benefit from this money at all. If anybody tries to make you pay money for using and/or for obtaining the LameXP software, you should <strong>not</strong> respond to this dubious offer!</p> <h2 id="q-can-i-redistribute-the-lamexp-software"><span class="header-section-number">9.2</span> Q: Can I redistribute the LameXP software?</h2> <p><strong>A:</strong> Yes. LameXP is <a href="http://en.wikipedia.org/wiki/Free_software">free software</a>. You may modify and/or redistribute it freely, according to the terms of the <a href="GNU%20General%20Public%20License"><em>GNU General Public License</em></a>. However, be aware that it is <em>strictly forbidden</em> to bundle the LameXP program files and/or the LameXP installation program with any kind of Adware, Spyware or PUP (potentially unwanted program). Usually, <strong>no</strong> additional permission is needed to redistribute LameXP. If, however, you wish to redistribute the LameXP software in a way that does <strong>not</strong> <em>comply</em> with the license terms, <em>then</em> a written permission from the author (copyright holder) is absolutely necessary!</p> <h2 id="q-how-can-i-donate-to-the-authors-of-lamexp"><span class="header-section-number">9.3</span> Q: How can I donate to the authors of LameXP?</h2> <p><strong>A:</strong> LameXP is a <em>non-profit</em> project. The authors of the LameXP software currently do <strong>not</strong> accept any donations, in terms of money. If you wish to support the LameXP project, then you may do so by contributing translations, by improving the LameXP program code or by providing web-servers. Please feel free to contact us at any time, if you want to help!</p> <h2 id="q-why-is-this-software-called-lamexp"><span class="header-section-number">9.4</span> Q: Why is this software called <em>LameXP</em>?</h2> <p><strong>A:</strong> Originally, the LameXP software was created as a very simple <a href="http://en.wikipedia.org/wiki/Graphical_user_interface">GUI front-end</a> to the <a href="http://lame.sourceforge.net/"><em>LAME</em></a> MP3 command-line encoder. The original version of this software, released some time in 2004, did <strong>not</strong> support any encoders except for LAME, it did <strong>not</strong> support any input formats except for Wave Audio, it did <strong>not</strong> support any audio filters, it did <strong>not</strong> support multi-threading, it did <strong>not</strong> support Unicode file names and it did <strong>not</strong> handle meta information. Because the software was a front-end to LAME, and because, back at that time, <em>Windows XP</em> was the most popular Windows version (by far), we decided to call the software &quot;LAME front-end for Windows XP&quot; – or, in short, <em>LameXP</em>. Anyway, more and more features have been added to the LameXP software over the years. Also, the software has been re-written from the scratch two times. Nonetheless, the original name of the software has remained. Now, a whole lot of people know the software by <em>this</em> name, so it is unlikely to ever change.</p> <h2 id="q-why-are-the-lamexp-binaries-not-digitally-signed"><span class="header-section-number">9.5</span> Q: Why are the LameXP binaries <em>not</em> digitally signed?</h2> <p><strong>A:</strong> They <em>are</em> signed! The official LameXP binaries are digitally signed by <a href="http://de.wikipedia.org/wiki/Pretty_Good_Privacy"><em>PGP</em></a> signatures, created using the <a href="http://de.wikipedia.org/wiki/GNU_Privacy_Guard">GnuPG</a> software. However, the LameXP binaries are <em>not</em> signed in a way that the Microsoft Windows operating system recognizes. Please note that Microsoft Windows does <strong>not</strong> currently recognize PGP (GnuPG) signatures. For this reason, Microsoft Windows may show a warning message when trying to launch or install the LameXP software. Microsoft Windows will also complain that the LameXP program files originate from an &quot;unknown publisher&quot;, as it can't understand the PGP signature.</p> <p>So why are the LameXP binaries not signed in the way Microsoft Windows recognizes? This is because Microsoft Windows uses a <em>hierarchical</em> trust model: Windows trusts into a number of <em>Certificate Authorities</em> (CA), which are built into the operating system. These CA's can issue signing certificates, e.g., to software companies. The software company can then use its signing certificate to sign their binaries. Finally, Windows will verify the signature by using the corresponding signing certificate. And the signing certificate is verified using the <em>built-in</em> CA certificate. However, there are problems: First of all, CA's do <em>not</em> issue software signing certificates for free. Also these certificates are only valid for a limited period of time. LameXP is a <em>non-profit</em> project and therefore we can <em>not</em> afford buying new certificates in regular intervals! Secondly, and even more important, the whole system depends on the <em>trustworthiness</em> of a few root CA's. But, as we all (should) know by now, the CA's <em>can</em> be forced to create &quot;bogus&quot; certificates, e.g. on the request of intelligence services or other governmental organizations.</p> <p>PGP, on the other hand, is based on the &quot;web of trust&quot; concept. This means that all participants sign each others' keys – after the keys have been verified. There are <strong>no</strong> &quot;almighty&quot; authorities! If you want to verify the LameXP signatures yourself, then you may do so by using the <a href="http://www.gpg4win.de/">Gpg4win</a> software package, an easy-to-use distribution of the <em>GnuPG</em> software for Microsoft Windows. Of course you will also require the <em>public</em> key of the LameXP developers! The <em>finperprint</em> of our PGP signing key is <strong><code>DFAD4340D83D4020435D78BB2B5913365F57E03F</code></strong> and the corresponding public key block is provided in the following. If you are <em>not</em> familiar with the GnuPG software yet, please have a look at the <a href="http://www.gpg4win.de/documentation.html">Gpg4win compendium</a> or the <a href="https://www.gnupg.org/documentation/manuals.html">GnuPG manual</a>.</p> <p><strong>MuldeR's signature key:</strong></p> <pre><code>pub   rsa4096 2015-08-23 [expires: 2025-08-20]
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.</code></pre> <p><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="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 &quot;suspicious&quot;, &quot;generic&quot; or &quot;packed&quot;. Those results are <strong>not</strong> 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> &quot;packed&quot; executables of being malware. Nonetheless, using so-called &quot;executable packers&quot;, 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 &quot;packed&quot; 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>, which means that the <em>source codes</em> of LameXP are freely available. Everybody can easily see that there is <strong><em>no</em></strong> malware of any kind included in the LameXP source code! If you do <em>not</em> trust the provided <em>binaries</em> of LameXP, you may build your own binary directly from the LameXP source codes…</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 &quot;behind the scenes&quot; 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 <em>paying customer</em>, you can demand that <em>false positives</em> are fixed promptly. Otherwise, get your money back!</p> <h2 id="performance-issues"><span class="header-section-number">3.2</span> Performance Issues</h2> <p>During the <em>startup procedure</em>, the LameXP software has to perform a number of <em>file-system</em> operations. This can take a few moments. However, the startup procedure should <strong>never</strong> take longer than <em>approximately</em> 5 seconds. Even on our test system – Windows 7 running on an <em>ancient</em> Intel Core2 processor with 4 GB of RAM – the startup procedure takes only about 1.5 seconds. And that is with the &quot;real-time protection&quot; of Microsoft Security Essentials (MSE) enabled! If we disable the MSE &quot;real-time protection&quot; feature, the startup procedure takes less than 0.5 seconds. <em>Unfortunately</em>, it has been brought to our attention, that some other anti-virus products may <em>slow down</em> the startup procedure significantly! Startup delays of up to 20 seconds have been reported by users, which corresponds to a slow down factor of <strong>40×</strong> – caused by the anti-virus software!</p> <p>Consequently, if you think that LameXP is starting up &quot;slow&quot; on your machine, we recommend to <strong>temporarily</strong> <em>disable</em> or <em>uninstall</em> your current anti-virus software. If your anti-virus software has a so-called &quot;real-time protection&quot; or &quot;guard&quot; feature, please be sure to <em>deactivate</em> that feature too! As soon as the anti-virus software has been <em>neutralized</em> and <strong>no</strong> longer affects legitimate applications, please try launching the LameXP software again. If it turns out that the startup procedure of LameXP has become significantly <em>faster</em> when the anti-virus software is <strong>not</strong> interfering, then you know one thing for sure: It is the <em>anti-virus software</em> that was causing the slow down! Please recognize that <em>we</em> can <strong>not</strong> fix this kind of problems. Instead, since the problem is actually a <em>defect</em> of the anti-virus software, please report the problem to the developer of the <em>anti-virus software</em>!</p> <p>Another way of detecting performance issues that are caused by sloppy anti-virus software is monitoring the CPU usage in Task Manager (or <a href="https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx"><em>Process Explorer</em></a>) while LameXP is starting up. Please make sure that you are <strong>not</strong> looking at the &quot;overall&quot; CPU usage, but at the CPU usage caused by the <em>individual</em> processes, and that &quot;show processes from all users&quot; is <em>enabled</em>. Then you will probably notice that <code>LameXP.exe</code> is sitting &quot;idle&quot;, more or less, while some <em>service process</em> belonging to the anti-virus software is &quot;hogging&quot; the CPU. The anti-virus software is hindering LameXP startup! A typical example looks like this:</p> <figure> <img src="img/lamexp/av_gone_mad.png"/> </figure> <p>Please report <em>performance issues</em> to the anti-virus software's developer. Also, when reporting <em>performance issues</em>, please be self-confident! As a <em>paying customer</em>, you can demand that such <em>bugs</em> are fixed promptly. Otherwise, get your money back!</p> <h2 id="anti-virus-conclusions"><span class="header-section-number">3.3</span> Anti-Virus Conclusions</h2> <p>The <strong>code of conduct</strong> regarding problems and annoyances related to so-called &quot;anti-virus&quot; software:</p> <ul> <li><p>If your anti-virus software raises an &quot;alarm&quot; or &quot;warning&quot; while trying to launch the LameXP software or the LameXP setup program, please do <strong>not</strong> panic! In most cases, it is just the anti-virus software that went insane.</p></li> <li><p>Unless the alleged &quot;malware infection&quot; has been confirmed by <strong>multiple</strong> <a href="http://www.virustotal.com/"><em>different</em></a> anti-virus engines, this (almost) certainly is a <a href="http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives"><strong>false positive</strong></a>, i.e. <strong>not</strong> an &quot;infection&quot; at all. Therefore, it can be ignored safely 😊</p></li> <li><p>In the extremely unlikely case that you actually have a <em>confirmed</em> malware infection, please try re-downloading the LameXP software from one of the <strong>official</strong> mirrors first, <em>before</em> you send us any &quot;malware&quot; reports!</p></li> <li><p>If you encounter any <a href="http://en.wikipedia.org/wiki/Antivirus_software#Problems_caused_by_false_positives"><strong>false positives</strong></a>, please report these problems to the developer of the <em>defective</em> anti-virus software. <em>We</em> are <strong>not</strong> responsible for this problem (it is a bug in the anti-virus software) and thus <em>we</em> can <strong>not</strong> fix it!</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">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">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>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 &quot;Yes&quot;, if you wish to continue the installation process.</p> <p><em>Note:</em> If you wonder why Windows suggests that the LameXP setup program originates from an &quot;unknown publisher&quot;, despite the fact that it was downloaded from the official web-site, then please the explanation <a href="http://lamexp.sourceforge.net/doc/Manual.html#q-why-are-the-lamexp-binaries-not-digitally-signed">here</a>!</p> <figure> <img src="img/lamexp/setup_1a.png"/> </figure> <p>Now simply follow the instructions of the setup wizard, which will guide you through the installation process…</p> <p><em>Note:</em> Please do <strong>not</strong> change the &quot;Destionation Folder&quot;, unless you know exactly what you are doing. The &quot;Destionation Folder&quot; cannot be changed, when <em>upgrading</em> an existing LameXP installation.</p> <figure> <img src="img/lamexp/setup_1b.png"/> </figure> <p>Congratulation, LameXP has been installed successfully on your computer!</p> <p><em>Note:</em> If you keep the &quot;Run LameXP …&quot; option enabled and click on the &quot;Finish&quot; button, the LameXP software will be launched immediately.</p> <figure> <img src="img/lamexp/setup_1c.png"/> </figure> <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> <figure> <img src="img/lamexp/setup_2a.png"/> </figure> <p>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><em>Note:</em> It is very important that you have write-access to the chosen destination directory. So make sure that you choose a directory where the required access rights are granted!</p> <figure> <img src="img/lamexp/setup_2b.png"/> </figure> <p>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> <figure> <img src="img/lamexp/setup_2c.png"/> </figure> <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> &quot;portable version&quot; or &quot;portable edition&quot; of the LameXP software. Instead, <strong>all</strong> versions of the LameXP software always <em>are</em> &quot;portable&quot; – 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 &quot;out of the box&quot;. 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 &quot;portable mode&quot;, which can be enabled or disabled at any time. By default, i.e. when the &quot;portable mode&quot; 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 &quot;portable mode&quot; is <em>enabled</em>.</p> <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 &quot;portable mode&quot; 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> <figure> <img src="img/lamexp/setup_3a.png"/> </figure> <h4 id="portable-mode-warning" class="unnumbered">Portable Mode Warning</h4> <p>While the &quot;portable mode&quot; 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><em>Note:</em> The directories <code>C:\Program Files (x86)</code> and <code>C:\Program Files</code> usually are &quot;protected&quot; 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 &quot;portable mode&quot; 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 &quot;portable mode&quot; 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">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">4.3.1</span> Nero Digital AAC Encoder</h3> <p>First of all, you need to download the <a href="https://web.archive.org/web/20160310025758/http://www.nero.com:80/enu/company/about-nero/nero-aac-codec.php"><b>Nero AAC encoder</b></a> from one of the following mirror sites:</p> <ul> <li><a href="http://www.videohelp.com/software/Nero-AAC-Codec" class="uri">http://www.videohelp.com/software/Nero-AAC-Codec</a></li> <li><a href="http://www.free-codecs.com/download/Nero_AAC_Codec.htm" class="uri">http://www.free-codecs.com/download/Nero_AAC_Codec.htm</a></li> <li><a href="http://www.majorgeeks.com/files/details/nero_aac_codec_(formerly_nero_digital_audio).html" class="uri">http://www.majorgeeks.com/files/details/nero_aac_codec_(formerly_nero_digital_audio).html</a></li> <li><a href="http://ftp6.nero.com/tools/NeroAACCodec-1.5.1.zip" class="uri">http://ftp6.nero.com/tools/NeroAACCodec-1.5.1.zip</a></li> </ul> <p><em>Note:</em> Although the ZIP file is sometimes called <code>NeroAACCodec-1.5.1.zip</code>, it may actually contains version <strong>1.5.4.0</strong> of the Nero AAC encoder software. Check the included <code>changelog.txt</code> to verify this!</p> <figure> <img src="img/lamexp/setup_4a.png"/> </figure> <p>Now open the downloaded ZIP file 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>) and navigate to the &quot;win32&quot; sub-directory.</p> <figure> <img src="img/lamexp/setup_4b.png"/> </figure> <p>Finally, <em>extract</em> all the three files <code>neroAacDec.exe</code>, <code>neroAacEnc.exe</code> and <code>neroAacTag.exe</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> <figure> <img src="img/lamexp/setup_4c.png"/> </figure> <p>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">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" class="unnumbered">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/" class="uri">http://sourceforge.net/projects/lamexp/files/Miscellaneous/Add-ins/qaac/</a></li> <li><a href="http://muldersoft.com/misc/lamexp/add-ins/qaac/" class="uri">http://muldersoft.com/misc/lamexp/add-ins/qaac/</a></li> </ul> <p>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> <figure> <img src="img/lamexp/setup_5a.png"/> </figure> <p>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> <figure> <img src="img/lamexp/setup_5b.png"/> </figure> <h4 id="install-apple-aac-encoder-libraries" class="unnumbered">Install Apple AAC Encoder Libraries</h4> <p>Next, the actual Apple/QuickTime AAC encoder libraries, which are part of the so-called &quot;Apple Application Support&quot; package, need to be installed on your computer. QAAC can <em>not</em> work without these libraries!</p> <p>The required &quot;Apple Application Support&quot; 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> <li><a href="https://www.apple.com/quicktime/download/" class="uri">https://www.apple.com/quicktime/download/</a></li> <li><a href="https://www.apple.com/itunes/download/" class="uri">https://www.apple.com/itunes/download/</a></li> </ul> <p>Since you usually do <strong>not</strong> want to <em>install</em> the complete QuickTime (or iTunes) software on your computer, please only <em>download</em> the QuickTime (or iTunes) setup package, but do <strong>not</strong> actually <em>run</em> the installer!</p> <p>Instead, open the QuickTimer setup program, i.e. <code>QuickTimeInstaller.exe</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>) and <em>extract</em> the required <code>AppleApplicationSupport.msi</code> package.</p> <figure> <img src="img/lamexp/setup_5c.png"/> </figure> <p>After the &quot;Apple Application Support&quot; setup package has been extracted, you can launch it by double-clicking on the <code>AppleApplicationSupport.msi</code> file. Then simply follow the installer's instructions!</p> <p><em>Note:</em> If you do <strong>not</strong> want to install the &quot;Apple Application Support&quot; software at all, there is an <em>alternative</em> method, that will extract only the required DLL files from the MSI package. See <a href="https://forum.doom9.org/showpost.php?p=1718529&amp;postcount=1221"><em>here</em></a> for details…</p> <figure> <img src="img/lamexp/setup_5d.png"/> </figure> <p>Once the QAAC encoder as well as the Apple AAC encoder libraries (&quot;Apple Application Support&quot;) 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">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">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 &quot;Source Files&quot; tab, just in case that tab is not active already, and then click the &quot;Add File(s)&quot; button.</p> <figure> <img src="img/lamexp/tutorial_1a.png"/> </figure> <p>This will bring up a standard file selection dialogue. Now simply select the files that you want to add and click the &quot;Open&quot; button. You can repeat this step multiple times, e.g. to add files from different directories.</p> <figure> <img src="img/lamexp/tutorial_1b.png"/> </figure> <p>All files you have added, so far, will show up in the list. You can click the &quot;Remove&quot; button to remove a single file from the list or &quot;Clear&quot; to remove them all. You can also click the &quot;Show details&quot; button to show details about the selected file.</p> <figure> <img src="img/lamexp/tutorial_1c.png"/> </figure> <p>If you want to add an <em>entire</em> directory, you can select &quot;Open Folder&quot; from the &quot;File&quot; menu, which will bring up a directory selection dialogue. &quot;Open Folder Recursively&quot; works in a similar way, but also includes <em>all</em> sub-directories.</p> <figure> <img src="img/lamexp/tutorial_1d.png"/> </figure> <p><em>Did you know?</em> Files can also be added via <a href="http://en.wikipedia.org/wiki/Drag_and_drop">Drag &amp; 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 &quot;dropbox&quot; widget).</p> <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 &quot;Output Directory&quot; 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 &quot;Home&quot; folder, &quot;Desktop&quot; folder and &quot;Music&quot; folder, respectively.</p> <figure> <img src="img/lamexp/tutorial_2a.png"/> </figure> <p>Sometimes you may wish to store the converted files in a <em>new</em> (sub-)folder. In this case, simply click the &quot;Make New Folder&quot; button, enter the desired folder name and hit the &quot;OK&quot; button.</p> <figure> <img src="img/lamexp/tutorial_2b.png"/> </figure> <p>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> <figure> <img src="img/lamexp/tutorial_2c.png"/> </figure> <p><em>Did you know?</em> If you enable the &quot;Save output files in the same directory where the input file is located&quot; 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">5.3</span> Compression Settings</h2> <p>Finally, you need to choose your <strong>compression settings</strong>. Most important, you must decide for an output <em>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> <figure> <img src="img/lamexp/tutorial_3a.png"/> </figure> <p>Once you have decided for an audio format, you need to choose a <em>rate-control</em> mode next. This controls how the bits are allocated for the compressed audio files. The available rate-control modes are <em>CBR</em>, <em>VBR</em> and <em>ABR</em>:</p> <ul> <li><p>CBR (constant bitrate) uses a <em>fixed</em> bitrate, i.e. each segment of the file receives the exactly same amount of bits, regardless of its contents. This comes at the advantage that the resulting file size is perfectly predictable. However, because the bitrate can <em>not</em> be adapted to the contents of the file at all, this generally is the <em>least</em> favorable mode!</p></li> <li><p>VBR (quality-base variable bitrate) mode adapts the bitrate to the contents of the file. Each segment of the file receives as many bits as are required to hit the target quality level. This means that &quot;complex&quot; segments of the file will end up with a higher bitrate than more &quot;simple&quot; segments. The bits will be used where they are actually needed. However, because the bitrate varies strongly depending on the contents of the file, the resulting file size is completely unpredictable!</p></li> <li><p>ABR (average bitrate) mode can be understood as a &quot;middle course&quot; between VBR and CBR mode. Similar to VBR mode, ABR mode adapts the bitrate to the contents of the file. But, at the same time, similar to CBR mode, ABR mode limits the bitrate variation in order to hit the specified target <em>average</em> bitrate, i.e. the resulting file size <em>is</em> predictable.</p></li> </ul> <p><em>Note:</em> If you are uncertain which rate-control mode to chose, the rule of thumb is that VBR mode should be preferred over ABR mode when possible. And CBR mode should be avoided. See also Wikipedia's article on <a href="http://en.wikipedia.org/wiki/Variable_bitrate">variable bitrate</a> encoding.</p> <figure> <img src="img/lamexp/tutorial_3b.png"/> </figure> <p>Last but not least, you need to choose the desired target <em>bitrate</em> (kbps) or the desired <em>quality-level</em>. Put simply, this controls the &quot;quality vs. file size&quot; trade-off. You choose a target quality-level in case of VBR mode. And you choose a target (average) bitrate in case of ABR or CBR mode. A <em>higher</em> target bitrate or a <em>higher</em> target quality level results in improved audio quality, but also comes at the cost of larger files. Conversely, a <em>lower</em> target bitrate or a <em>lower</em> target quality level results in smaller files, but also comes at the cost of reduced audio quality. The &quot;optimal&quot; setting highly depends on your personal preferences.</p> <p><em>Note:</em> If you are uncertain which bitrate or quality-level to choose, &quot;Level 2&quot; (VBR) or &quot;192 kbps&quot; (ABR) is a common choice for MP3. If the size of the resulting file is <em>not</em> a primary concern, you can go with &quot;Level 0&quot; (VBR) or &quot;320 kbps&quot; (ABR) right away.</p> <figure> <img src="img/lamexp/tutorial_3c.png"/> </figure> <p><em>Did you know?</em> You can click the &quot;Reset&quot; link in order to reset <em>all</em> compression settings for <em>all</em> encoders to their factory defaults.</p> <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 &quot;Encode Now&quot; button in order to get going!</p> <figure> <img src="img/lamexp/tutorial_4a.png"/> </figure> <p>This will bring up the &quot;Processing&quot; 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><em>Note:</em> In order to leverage the power &quot;multi-core&quot; processors and thus massively speed-up the encoding process, LameXP will run multiple encoding jobs in parallel – provided that your system has multiple processor cores and that there are enough encoding jobs left in the queue.</p> <figure> <img src="img/lamexp/tutorial_4b.png"/> </figure> <p>The &quot;Processing&quot; 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> <figure> <img src="img/lamexp/tutorial_4c.png"/> </figure> <p><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="command-line-usage"><span class="header-section-number">6</span> Command-line Usage</h1> <p>Additional <strong><a href="http://en.wikipedia.org/wiki/Command-line_interface">command-line</a> options</strong> may be passed to LameXP when launching the application. You may do so, for example, by typing the complete command-line into the <a href="http://en.wikipedia.org/wiki/Cmd.exe"><em>command prompt</em></a> or by creating a <a href="http://en.wikipedia.org/wiki/File_shortcut"><em>shortcut</em></a> with the desired command-line options. The basic command-line syntax of LameXP is as follows: Each command-line option has to start with a <code>--</code> prefix. So if you intend to pass the option called &quot;foo&quot;, then you actually need to type <code>--foo</code>. Furthermore, while some command-line options are just <em>flags</em>, i.e. they can either be present or not (but that's it!), there also are command-line options that take an <em>argument</em>. The argument is <em>appended</em> directly to the option name to which it belongs to, but a <code>=</code> sign <strong>must</strong> to be inserted as a separator. If, for example, you wish to set the command-line option &quot;foo&quot; to an argument value of &quot;bar&quot;, then the proper syntax is <code>--foo=bar</code>. Sometimes your argument value may contain <em>whitespaces</em> though, in which case the <em>whole</em> command-line option (name + argument) <strong>must</strong> be enclosed with double quotes. For example, in order to set the option &quot;foo&quot; to a value of &quot;C:\Some File.bar&quot; (note the space character between &quot;Some&quot; and &quot;File&quot;), the proper syntax is <code>&quot;--foo=C:\Some File.bar&quot;</code>. Last but not least, please note that the <em>same</em> command-line option may appear <em>multiple</em> times on the command-line – whether that actually makes any sense depends on the individual option though.</p> <h2 id="add-files-andor-folders"><span class="header-section-number">6.1</span> Add Files and/or Folders</h2> <p>Command-line options for adding files and/or folders:</p> <ul> <li><p><code>--add=filename</code><br/> Adds the file specified by <em>filename</em> to the source files list. The <em>filename</em> should be a <a href="http://en.wikipedia.org/wiki/Fully_qualified_name#Filenames_and_paths">fully-qualified</a> path. If you wish to add multiple files at once, you can simply include this option multiple times.</p></li> <li><p><code>--add-folder=directory</code><br/> Adds <em>all</em> supported files from the directory specified by <em>directory</em> to the source files list. The <em>directory</em> should be a <a href="http://en.wikipedia.org/wiki/Fully_qualified_name#Filenames_and_paths">fully-qualified</a> path. Sub-directories are <strong>not</strong> considered.</p></li> <li><p><code>--add-recursiver=directory</code><br/> This option works just like the &quot;add-folder&quot; option, except that it works recursively, i.e. it <em>does</em> take into account sub-directories. Use this option with care, since a whole lot of files may be added.</p></li> </ul> <h3 id="examples"><span class="header-section-number">6.1.1</span> Examples</h3> <p>Here are some <em>examples</em> on how to use the above command-line options correctly:</p> <ul> <li><p>Add one file:<br/> <code>LameXP.exe &quot;--add=C:\Some Folder\Some File.mp3&quot;</code></p></li> <li><p>Add multiple files at once:<br/> <code>LameXP.exe &quot;--add=C:\Some Folder\File #1.mp3&quot; &quot;--add=C:\Some Folder\File #2.mp3&quot; &quot;--add=C:\Some Folder\File #3.mp3&quot;</code></p></li> <li><p>Add a whole directory:<br/> <code>LameXP.exe &quot;--add-folder=C:\Some Folder&quot;</code></p></li> </ul> <h2 id="gui-adjustment-options"><span class="header-section-number">6.2</span> GUI Adjustment Options</h2> <p>Command-line options for adjusting the graphical user-interface:</p> <ul> <li><p><code>--huge-font</code><br/> Set the font scaling factor to 150%. Use this if you want <em>much</em> larger fonts.</p></li> <li><p><code>--big-font</code><br/> Set the font scaling factor to 125%. Use this if you want <em>somewhat</em> larger fonts.</p></li> <li><p><code>--small-font</code><br/> Set the font scaling factor to 87.5%. Use this if you want <em>somewhat</em> smaller fonts.</p></li> <li><p><code>--tiny-font</code><br/> Set the font scaling factor to 75%. Use this if you want <em>much</em> smaller fonts.</p></li> </ul> <h2 id="options-for-debugging"><span class="header-section-number">6.3</span> Options for Debugging</h2> <p>Command-line options that are intended for testing and debugging:</p> <ul> <li><p><code>--console</code><br/> Enable the LameXP debug console. Use this option with &quot;release&quot; builds of LameXP, where the console is hidden by default.</p></li> <li><p><code>--no-console</code><br/> The opposite of the &quot;console&quot; option: Disable the LameXP debug console. Use this option with &quot;pre-release&quot; (beta) builds of LameXP, where the console is visible by default.</p></li> <li><p><code>--force-cpu-no-64bit</code><br/> Treat the CPU as if it did <strong>not</strong> support <a href="http://en.wikipedia.org/wiki/X86-64">64-Bit (x64)</a> applications, even when it actually does so.</p></li> <li><p><code>--force-cpu-no-sse</code><br/> Treat the CPU as if it did <strong>not</strong> support any <a href="http://en.wikipedia.org/wiki/Streaming_SIMD_Extensions">SSE</a> extensions (SSE, SSE2, SSE3, SSSE3, SSSE4, etc), even when it actually does so.</p></li> <li><p><code>--force-cpu-no-intel</code><br/> Treat the CPU as if it was a <em>non</em>-Intel processor, even when the vendor tag indicates an Intel processor.</p></li> <li><p><code>--ignore-compat-mode</code><br/> Do <strong>not</strong> check whether the application is running with &quot;compatibility mode&quot; enabled. It's still <em>not</em> recommended to run with compatibility mode enabled!</p></li> </ul> <h2 id="miscellaneous-options"><span class="header-section-number">6.4</span> Miscellaneous Options</h2> <p>Miscellaneous command-line options that may come in handy in certain situations:</p> <ul> <li><p><code>--kill</code><br/> Exit all running instances of LameXP.</p></li> <li><p><code>--force-kill</code><br/> Exit all running instances of LameXP as quickly as possible, even if that incurs data loss. Use with extreme care!</p></li> </ul> <h1 id="help-support"><span class="header-section-number">7</span> Help &amp; 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">7.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" class="uri">https://github.com/lordmulder/LameXP/releases/latest</a></li> <li><a href="http://sourceforge.net/projects/lamexp/files/" class="uri">http://sourceforge.net/projects/lamexp/files/</a></li> <li><a href="https://lamexp.codeplex.com/releases/" class="uri">https://lamexp.codeplex.com/releases/</a></li> <li><a href="https://bitbucket.org/muldersoft/lamexp/downloads" class="uri">https://bitbucket.org/muldersoft/lamexp/downloads</a></li> <li><a href="https://www.assembla.com/spaces/lamexp/documents" class="uri">https://www.assembla.com/spaces/lamexp/documents</a></li> <li><a href="http://www.free-codecs.com/lamexp_download.htm" class="uri">http://www.free-codecs.com/lamexp_download.htm</a></li> <li><a href="http://www.videohelp.com/tools/LameXP" class="uri">http://www.videohelp.com/tools/LameXP</a></li> </ul> <p>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">7.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 &quot;Processing&quot; dialogue, which will bring up a detailed <em>log</em> for that job. Use the &quot;Copy to Clipboard&quot; button to save that information.</p></li> <li><p>You can launch the LameXP application with the additional <a href="http://en.wikipedia.org/wiki/Command-line_interface">command-line</a> parameter <code>--console</code> in order to enable the LameXP <em>debug console</em>, which provides many information on what is going on &quot;behind the scenes&quot;.</p></li> <li><p>If the debug console is <strong>not</strong> enabled, you may still use the <a href="http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx"><em>DebugView</em></a> utility, by Mark Russinovich, in order to show and/or capture LameXP's diagnostic output.</p></li> <li><p>In any case, 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 saved to the log file are the same as those available from the debug console.</p></li> </ul> <p><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">7.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" class="uri">https://github.com/lordmulder/LameXP/issues</a></li> </ul> <p><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">7.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" class="uri">http://forum.doom9.org/showthread.php?t=157726</a> – English</li> <li><a href="http://forum.gleitz.info/showthread.php?t=37956" class="uri">http://forum.gleitz.info/showthread.php?t=37956</a> – German</li> </ul> <p><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">8</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 &quot;utility&quot; 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">8.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 https://github.com/lordmulder/LameXP.git LameXP</code> (<a href="https://github.com/lordmulder/LameXP">Browse</a>)</p></li> <li><p><code>git clone https://git01.codeplex.com/lamexp LameXP</code> (<a href="https://lamexp.codeplex.com/SourceControl/latest">Browse</a>)</p></li> <li><p><code>git clone https://bitbucket.org/muldersoft/lamexp.git LameXP</code> (<a href="https://bitbucket.org/muldersoft/lamexp/src">Browse</a>)</p></li> <li><p><code>git clone git://git.assembla.com/lamexp.git LameXP</code> (<a href="https://www.assembla.com/code/lamexp/git/nodes">Browse</a>)</p></li> <li><p><code>git clone https://gitlab.com/lamexp/lamexp.git LameXP</code> (<a href="https://gitlab.com/lamexp/lamexp/tree/master">Browse</a>)</p></li> <li><p><code>git clone git://repo.or.cz/LameXP.git LameXP</code> (<a href="http://repo.or.cz/w/LameXP.git">Browse</a>)</p></li> </ul> <p>The source code of the <strong>MUtilities</strong> library 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/mutilities/code MUtilities</code> (<a href="http://sourceforge.net/p/mutilities/code/">Browse</a>)</p></li> <li><p><code>git clone https://github.com/lordmulder/MUtilities.git MUtilities</code> (<a href="https://github.com/lordmulder/MUtilities">Browse</a>)</p></li> <li><p><code>git clone https://git01.codeplex.com/mutilities MUtilities</code> (<a href="https://mutilities.codeplex.com/SourceControl/latest">Browse</a>)</p></li> <li><p><code>git clone https://bitbucket.org/muldersoft/mutilities.git MUtilities</code> (<a href="https://bitbucket.org/muldersoft/mutilities/src">Browse</a>)</p></li> <li><p><code>git clone git://git.assembla.com/mutilities.git MUtilities</code> (<a href="https://www.assembla.com/code/mutilities/git/nodes">Browse</a>)</p></li> <li><p><code>git clone https://gitlab.com/mutilities/mutilities.git MUtilities</code> (<a href="https://gitlab.com/mutilities/mutilities/tree/master">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><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">8.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="https://www.visualstudio.com/">Visual Studio 2015 Update-1</a>, running on Windows 10 x64 (v1511)</p></li> <li><p><a href="http://download.qt.io/archive/qt/4.8/">Qt libraries 4.8.7</a> for Windows (our <em>pre-compiled</em> Qt libraries for Visual Studio 2015 can be found <a href="http://sourceforge.net/projects/lamexp/files/Miscellaneous/Qt%20Libraries/"><strong>here</strong></a>)</p></li> <li><p><a href="https://vld.codeplex.com/">Visual Leak Detector</a>, open-source memory leak detection system for Visual C++</p></li> <li><p>Windows Platform SDK v7.1A, included with Visual Studio 2015 or Visual Studio 2013</p></li> <li><p>The minimum supported <em>build</em> platform is Windows 7 (x86 and x64)</p></li> </ul> <p>In order to create LameXP release packages, using the included deployment scripts, you need the following additional tools:</p> <ul> <li><p><a href="http://www.7-zip.org/">7-Zip</a> – file archiver with a high compression ratio</p></li> <li><a href="http://nsis.sourceforge.net/">NSIS</a> – Nullsoft Scriptable Install System (<a href="https://github.com/jimpark/unsis/releases"><em>Unicode version</em></a> recommended!) <ul> <li><a href="http://nsis.sourceforge.net/StdUtils_plug-in">StdUtils</a> plug-in</li> <li><a href="http://nsis.sourceforge.net/LockedList_plug-in">LockedList</a> plug-in</li> <li><a href="http://nsis.sourceforge.net/Inetc_plug-in">Inetc</a> plug-in</li> <li><a href="http://forums.winamp.com/showthread.php?t=329990">Aero</a> plug-in</li> <li><a href="http://nsis.sourceforge.net/SelfDel_plug-in">SelfDel</a> plug-in</li> </ul></li> <li><p><a href="http://upx.sourceforge.net/">UPX</a> – the Ultimate Packer for eXecutables</p></li> <li><p><a href="http://johnmacfarlane.net/pandoc/">Pandoc</a> – the Universal Document Converter</p></li> <li><p><a href="https://www.gpg4win.de/">GnuPG</a> – the GNU Privacy Guard (Gpg4win)</p></li> </ul> <h2 id="directory-layout"><span class="header-section-number">8.3</span> Directory Layout</h2> <p>In order to build LameXP using the provided project/solution files or the provided deployment script, please make sure you have the following directory layout, where <code>&lt;sources_root&gt;</code> is a new/empty directory:</p> <ul> <li><code>&lt;sources_root&gt;\LameXP_Qt</code> – the <em>LameXP</em> &quot;main&quot; project</li> <li><code>&lt;sources_root&gt;\Prerequisites</code> – prerequisites to build LameXP</li> <li><code>&lt;sources_root&gt;\MUtilities</code> – the <em>MUtilities</em> library</li> </ul> <p>The <em>Qt</em> libraries need to be located at the following location, where the <code>&lt;toolset_version&gt;</code> identifies your compiler version (e.g. <code>v140_xp</code> for VS2015) and the <code>&lt;build_type&gt;</code> identifies the build configuration (<code>Shared</code>, <code>Static</code> or <code>Debug</code>):</p> <ul> <li><code>&lt;sources_root&gt;\Prerequisites\Qt4\&lt;toolset_version&gt;\&lt;build_type&gt;</code></li> </ul> <h2 id="environment-variables"><span class="header-section-number">8.4</span> Environment variables</h2> <p>In order to build LameXP using the provided project/solution files or the provided deployment script, make sure the following environment variables are configured on your system:</p> <ul> <li><code>QTDIR</code> – points to your Qt installation directory, such that <code>%QTDIR%\bin\moc.exe</code> and friends exist</li> </ul> <h2 id="using-the-deployment-script"><span class="header-section-number">8.5</span> Using the deployment script</h2> <p>In order to create LameXP release packages, using the included deployment scripts, <strong>copy</strong> the <em>configuration</em> template file <code>buildenv.template.txt</code>, located at <code>&lt;sources_root&gt;\LameXP_Qt\etc\Deployment</code>, to the file <code>buildenv.txt</code> in the <em>same</em> directory. Now edit <em>your</em> <code>buildenv.txt</code> and adjust all the path variables as needed. All paths must be set up correctly, otherwise the build process is going to fail! Once everything has been set up, you can run <code>release.bat</code> or <code>release_static.bat</code> in order to create a new release package.</p> <h2 id="qt-as-static-libraries"><span class="header-section-number">8.6</span> Qt as Static Libraries</h2> <p>In order to create a &quot;fully static&quot; build of LameXP, i.e. a build that does <em>not</em> depend on any &quot;external&quot; DLL files (except for the obligatory operating system DLL's that you cannot get around), you'll need to compile Qt as &quot;static&quot; 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 &quot;static&quot; libraries. Consequently, you need to build the required &quot;static&quot; Qt libraries yourself. The following simple instructions should make it easy to build Qt from the sources and as &quot;static&quot; libraries:</p> <ol> <li><p>Make sure <em>Visual Studio 2015</em> with Update-1 (or later) is installed</p></li> <li><p>Make sure <em>Strawberry Perl </em>for Windows and <em>Python 2.7</em> are installed</p></li> <li><p>Download and extract the <em>Qt 4.8.x</em> source code package (e.g. to <code>C:\QtSources\4.8.x</code>)</p></li> <li><p>Edit the <em>qmake</em> configuration file (e.g. <code>mkspecs\win32-msvc2015\qmake.conf</code>) from your Qt Sources directory as follows:</p> <ul> <li>Edit #1: <ul> <li>⇐ <code>QMAKE_CFLAGS_RELEASE = -O2 -MD</code></li> <li>⇒ <code>QMAKE_CFLAGS_RELEASE = -O2 -MT &lt;more optimization flags here&gt;</code></li> </ul></li> <li>Edit #2: <ul> <li>⇐ <code>QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -O2 -MD -Zi</code></li> <li>⇒ <code>QMAKE_CFLAGS_RELEASE_WITH_DEBUGINFO += -O2 -MT -Zi &lt;more optimization flags here&gt;</code></li> </ul></li> </ul></li> <li><p>Open a new command window (<code>cmd.exe</code>) – use this very same console for all upcoming steps!</p></li> <li><p>Add <em>Strawberry Perl</em> to your PATH (e.g. <code>set PATH=C:\strawberry\perl\bin;%PATH%</code>)</p></li> <li><p>Add <em>Python 2.7</em> to your PATH (e.g. <code>set PATH=C:\python27;%PATH%</code>)</p></li> <li><p>Run <code>vcvarsall.bat x86</code> form your Visual C++ install directory - within the same console!</p></li> <li><p>Change the current directory to the <em>Qt Sources</em> path (e.g. <code>C:\QtSources\4.8.x</code>)</p></li> <li><p>Run <code>configure.exe -release -static -ltcg -qt-zlib -qt-libpng -qt-libjpeg -qt-libtiff -qt-libmng</code></p></li> <li><p>Now the makefiles should have been generated, so simply enter <code>nmake /B</code> and be patient - voilà!</p></li> <li><p>The build process is going to take good amount of time. Once it is done, make sure you got all needed libs:</p> <ul> <li><code>lib\qtmain.lib</code></li> <li><code>lib\QtCore.lib</code></li> <li><code>lib\QtGui.lib</code></li> <li><code>lib\QtSvg.lib</code></li> <li><code>lib\QtXml.lib</code></li> <li><code>plugins\imageformats\qico.lib</code></li> <li><code>plugins\imageformats\qsvg.lib</code></li> <li><code>plugins\imageformats\qtga.lib</code></li> </ul></li> <li><p>Put all the static *.lib files into the <code>&lt;sources_root&gt;\Prerequisites\Qt4\&lt;toolset_version&gt;\Static\lib</code> directory</p></li> <li><p>ImageFormat plugins go to <code>&lt;sources_root&gt;\Prerequisites\Qt4\&lt;toolset_version&gt;\plugins\imageformats</code></p></li> <li><p>Congratulations, you should now be prepared to build the <code>Release_Static</code> configuration of LameXP 😊</p></li> </ol> <p><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">9</span> F.A.Q. (Frequently Asked Questions)</h1> <p>This section tries to answer some of the most frequently asked questions. So if you have a question, please carefully read this section, before you send the question to us via email or before you open a new support ticket 😉</p> <h2 id="q-do-i-have-to-pay-for-using-or-obtaining-lamexp"><span class="header-section-number">9.1</span> Q: Do I have to pay for using or obtaining LameXP?</h2> <p><strong>A:</strong> Nope. LameXP is <a href="http://en.wikipedia.org/wiki/Free_software">free software</a>. You may use it <strong><em>free of charge</em></strong> and for any purpose, including commercial purposes, according to the terms of the <a href="GNU%20General%20Public%20License"><em>GNU General Public License</em></a>. The developers of LameXP will <strong>never</strong> ask you to pay for using the LameXP software. Also, several <strong><em>free</em></strong> download mirrors are provided. However, it was brought to our attention, that there are some <em>third-party</em> web-sites which offer <em>payed</em> downloads of LameXP, or provide LameXP downloads that have been infected with Adware – we do <strong>not</strong> cooperate with any of these web-sites! Therefore, please do <strong>not</strong> pay money for using or obtaining the LameXP software; the developers of LameXP will <strong>not</strong> benefit from this money at all. If anybody tries to make you pay money for using and/or for obtaining the LameXP software, you should <strong>not</strong> respond to this dubious offer!</p> <h2 id="q-can-i-redistribute-the-lamexp-software"><span class="header-section-number">9.2</span> Q: Can I redistribute the LameXP software?</h2> <p><strong>A:</strong> Yes. LameXP is <a href="http://en.wikipedia.org/wiki/Free_software">free software</a>. You may modify and/or redistribute it freely, according to the terms of the <a href="GNU%20General%20Public%20License"><em>GNU General Public License</em></a>. However, be aware that it is <em>strictly forbidden</em> to bundle the LameXP program files and/or the LameXP installation program with any kind of Adware, Spyware or PUP (potentially unwanted program). Usually, <strong>no</strong> additional permission is needed to redistribute LameXP. If, however, you wish to redistribute the LameXP software in a way that does <strong>not</strong> <em>comply</em> with the license terms, <em>then</em> a written permission from the author (copyright holder) is absolutely necessary!</p> <h2 id="q-how-can-i-donate-to-the-authors-of-lamexp"><span class="header-section-number">9.3</span> Q: How can I donate to the authors of LameXP?</h2> <p><strong>A:</strong> LameXP is a <em>non-profit</em> project. The authors of the LameXP software currently do <strong>not</strong> accept any donations, in terms of money. If you wish to support the LameXP project, then you may do so by contributing translations, by improving the LameXP program code or by providing web-servers. Please feel free to contact us at any time, if you want to help!</p> <h2 id="q-why-is-this-software-called-lamexp"><span class="header-section-number">9.4</span> Q: Why is this software called <em>LameXP</em>?</h2> <p><strong>A:</strong> Originally, the LameXP software was created as a very simple <a href="http://en.wikipedia.org/wiki/Graphical_user_interface">GUI front-end</a> to the <a href="http://lame.sourceforge.net/"><em>LAME</em></a> MP3 command-line encoder. The original version of this software, released some time in 2004, did <strong>not</strong> support any encoders except for LAME, it did <strong>not</strong> support any input formats except for Wave Audio, it did <strong>not</strong> support any audio filters, it did <strong>not</strong> support multi-threading, it did <strong>not</strong> support Unicode file names and it did <strong>not</strong> handle meta information. Because the software was a front-end to LAME, and because, back at that time, <em>Windows XP</em> was the most popular Windows version (by far), we decided to call the software &quot;LAME front-end for Windows XP&quot; – or, in short, <em>LameXP</em>. Anyway, more and more features have been added to the LameXP software over the years. Also, the software has been re-written from the scratch two times. Nonetheless, the original name of the software has remained. Now, a whole lot of people know the software by <em>this</em> name, so it is unlikely to ever change.</p> <h2 id="q-why-are-the-lamexp-binaries-not-digitally-signed"><span class="header-section-number">9.5</span> Q: Why are the LameXP binaries <em>not</em> digitally signed?</h2> <p><strong>A:</strong> They <em>are</em> signed! The official LameXP binaries are digitally signed by <a href="http://de.wikipedia.org/wiki/Pretty_Good_Privacy"><em>PGP</em></a> signatures, created using the <a href="http://de.wikipedia.org/wiki/GNU_Privacy_Guard">GnuPG</a> software. However, the LameXP binaries are <em>not</em> signed in a way that the Microsoft Windows operating system recognizes. Please note that Microsoft Windows does <strong>not</strong> currently recognize PGP (GnuPG) signatures. For this reason, Microsoft Windows may show a warning message when trying to launch or install the LameXP software. Microsoft Windows will also complain that the LameXP program files originate from an &quot;unknown publisher&quot;, as it can't understand the PGP signature.</p> <p>So why are the LameXP binaries not signed in the way Microsoft Windows recognizes? This is because Microsoft Windows uses a <em>hierarchical</em> trust model: Windows trusts into a number of <em>Certificate Authorities</em> (CA), which are built into the operating system. These CA's can issue signing certificates, e.g., to software companies. The software company can then use its signing certificate to sign their binaries. Finally, Windows will verify the signature by using the corresponding signing certificate. And the signing certificate is verified using the <em>built-in</em> CA certificate. However, there are problems: First of all, CA's do <em>not</em> issue software signing certificates for free. Also these certificates are only valid for a limited period of time. LameXP is a <em>non-profit</em> project and therefore we can <em>not</em> afford buying new certificates in regular intervals! Secondly, and even more important, the whole system depends on the <em>trustworthiness</em> of a few root CA's. But, as we all (should) know by now, the CA's <em>can</em> be forced to create &quot;bogus&quot; certificates, e.g. on the request of intelligence services or other governmental organizations.</p> <p>PGP, on the other hand, is based on the &quot;web of trust&quot; concept. This means that all participants sign each others' keys – after the keys have been verified. There are <strong>no</strong> &quot;almighty&quot; authorities! If you want to verify the LameXP signatures yourself, then you may do so by using the <a href="http://www.gpg4win.de/">Gpg4win</a> software package, an easy-to-use distribution of the <em>GnuPG</em> software for Microsoft Windows. Of course you will also require the <em>public</em> key of the LameXP developers! The <em>finperprint</em> of our PGP signing key is <strong><code>DFAD4340D83D4020435D78BB2B5913365F57E03F</code></strong> and the corresponding public key block is provided in the following. If you are <em>not</em> familiar with the GnuPG software yet, please have a look at the <a href="http://www.gpg4win.de/documentation.html">Gpg4win compendium</a> or the <a href="https://www.gnupg.org/documentation/manuals.html">GnuPG manual</a>.</p> <p><strong>MuldeR's signature key:</strong></p> <pre><code>pub   rsa4096 2015-08-23 [expires: 2025-08-20]
       DFAD 4340 D83D 4020 435D 78BB 2B59 1336 5F57 E03F
 uid   LoRd_MuldeR (muldersoft.com)</code></pre> <p><strong>PGP key block containing the required key:</strong></p> <pre><code>-----BEGIN PGP PUBLIC KEY BLOCK-----
 mQINBFXZtmgBEADZVW8CgoSjGvjwKVWWfZ+I/MsyD1y495hp7or+XW+OW/wWI7Qb
diff --git a/doc/Manual.md b/doc/Manual.md
index a20f4711..ed1731de 100644
--- a/doc/Manual.md
+++ b/doc/Manual.md
@@ -257,7 +257,7 @@ LameXP can use the **Nero Digital** AAC encoder as well as the **QAAC** (Apple i
 
 ### Nero Digital AAC Encoder ###
 
-First of all, you need to download the Nero AAC encoder from the official Nero Digital web-site or one of the mirrors:
+First of all, you need to download the <a href="https://web.archive.org/web/20160310025758/http://www.nero.com:80/enu/company/about-nero/nero-aac-codec.php"><b>Nero AAC encoder</b></a> from one of the following mirror sites:
 
 * <http://www.videohelp.com/software/Nero-AAC-Codec>
 * <http://www.free-codecs.com/download/Nero_AAC_Codec.htm>
-- 
2.11.4.GIT