</script><noscript><MuldeR2@GMX.de> (%3CMuldeR2 at GMX dot de%3E)</noscript>. Consequently, all copyrights on LameXP belong to LoRd_MuldeR. The right to use, modify and redistribute the LameXP software <em>according to the terms of the GPL (GNU General Public License)</em> is hereby granted to everybody. Please see below for license details! Be aware though that, if you want to use the LameXP software in a way that is <strong><em>not</em></strong> covered by the GPL, e.g. if you want to include the LameXP software (or parts of it) in a <em>proprietary</em> software, then an explicit written permission by LoRd_MuldeR is required!</p><p>More OpenSource projects by LoRd_MuldeR can be found at <ahref="http://muldersoft.com/"class="uri">http://muldersoft.com/</a> and <ahref="https://github.com/lordmulder"class="uri">https://github.com/lordmulder</a>. Please do <strong>not</strong> send us e-mail directly, if the problem or suggestion can be discussed on the support forums or on the issue tracker!</p><h2id="third-party-software"><spanclass="header-section-number">2.1</span> Third-party Software</h2><p>Note that LameXP uses a number of <em>third-party</em> applications and libraries. The copyright on these third-party tools belongs to the individual authors. <em>All</em> third-party tools that are included in the official distribution packages of LameXP are distributed in full accordance with the respective software license. For legal reasons, some of the third-party tools can <strong><em>not</em></strong> be redistributed along with LameXP and therefore need to be obtained separately. For more details on the third-party tools that are used by the LameXP software, please refer to the "Third-party software" tab in the "About" dialogue. Moreover, various people have contributed translations to the LameXP project. These translation are redistributed with permission of the respective contributor. For more information about our contributors, please refer to the "Contributors" tab in the "About" dialogue.</p><h2id="license-terms"><spanclass="header-section-number">2.2</span> License Terms</h2><p>LameXP is <ahref="http://en.wikipedia.org/wiki/Free_software_movement"><em>free software</em></a>, released under the terms of the <ahref="http://www.gnu.org/licenses/gpl-2.0.html"><em>GNU General Public License</em> (GPL), version 2</a>. The licenses for most software and other practical works are designed to take away your freedom to share and change those works. In contrast, the GPL is designed to <em>guarantee</em> your freedom to share and change all versions of the software. In other words, the GPL ensures that free software is going to remain free for all of its users until doomsday. LameXP adds some additional terms in order to keep your computer safe from unwanted software. See the <em>GNU General Public License</em> for more details!</p><pre><code>LameXP - Audio Encoder Front-End
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><h1id="anti-virus-notes"><spanclass="header-section-number">3</span> Anti-Virus Notes</h1><p>Occasionally, it may happen that your anti-virus software <em>mistakenly</em> detects <ahref="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 <ahref="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 <ahref="http://www.virustotal.com/">VirusTotal.com</a>, <ahref="http://www.virscan.org/">Virscan.org</a> or a similar web-service to check the file in question with <em>multiple</em> anti-virus engines. Unless the vast majority of the anti-virus engines detect malware, it can be assumed that the file is really harmless. However, please take care with <em>heuristic</em> scan results, such as "suspicious", "generic" or "packed". Those results are <strong>not</strong> 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 <ahref="http://nsis.sourceforge.net/">NSIS</a>– which includes the LameXP setup program. But, of course, installers created with NSIS are perfectly legitimate. Thus, if your anti-virus program complains about the LameXP setup program, please ignore the <em>nonsensical</em> warning! Furthermore, it seems that some anti-virus programs accuse <em>all</em>"packed" executables of being malware. Nonetheless, using so-called "executable packers", e.g. <ahref="http://upx.sourceforge.net/">UPX</a>, is perfectly legitimate. Executable packers are commonly used by legitimate software, including numerous OpenSource projects – and so does LameXP. Thus, if your anti-virus program complains about the LameXP program file, because it has been "packed" by UPX, please ignore the <em>nonsensical</em> warning!</p><p>Last but not least: Always keep in mind that LameXP is <em>free software</em>, 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><h2id="reporting-false-positives"><spanclass="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>misinte
-----END PGP PUBLIC KEY BLOCK-----</code></pre><h2id="q-why-does-lamexp-connect-to-random-web-servers"><spanclass="header-section-number">9.6</span> Q: Why does LameXP connect to (random) web-servers?</h2><p><strong>A:</strong> LameXP does <strong>not</strong> connect to any web-server, except for the "automatic updates" feature. Of course, in order to check for new updates, LameXP <em>unavoidably</em> has to communicate with our update servers. However, in <strong>no</strong> event LameXP will search for updates <em>without</em> your consent. Also, LameXP will <strong>not</strong> send any personal information to the update server. Instead of <em>uploading</em> your information, e.g. your current program version, to the web-server, LameXP will <em>download</em> the update information from the update server and compare it to your installed version locally. Furthermore, all information and program files downloaded from the update servers are protected by PGP (GnuPG) signatures, in order to assure the authenticity and integrity of these files. Files with missing/invalid signature are going to be <em>rejected</em>, so (spoofing) attacks are prevented.</p><p><em>Note:</em> Before LameXP actually tries to download information from our update servers, it will check your Internet connection. Only checking whether the update server itself is reachable does <strong>not</strong> suffice here. In case that the update server does <strong>not</strong> respond, this could mean that our servers are currently experiencing problems, but it could also mean that your Internet connection is failing. In order to distinguish these cases, LameXP will validate the Internet connection prior to connecting to the update server. For this purpose, LameXP contains a rather long list of "known" hosts, taken mostly from <ahref="http://www.alexa.com/topsites">Alexa's Top 500</a> list. In order to validate the Internet connection, LameXP will pick a <em>random</em> host from the list and check whether that host can be reached. This process will be repeated, until a certain minimum number of "known" hosts have been reached.</p><h2id="q-can-lamexp-convert-tracks-from-an-audio-cd"><spanclass="header-section-number">9.7</span> Q: Can LameXP convert tracks from an Audio CD?</h2><p>LameXP <em>can</em> be used to convert audio files that have been extracted from an Audio CD, but it currently can <strong>not</strong> extract ("rip") the audio tracks from the Audio CD directly. Consequently you will have to extract the audio tracks first, before you can convert them with LameXP. We recommend using the <ahref="http://www.exactaudiocopy.de/"><em>Exact Audio Copy</em></a> software for that purpose. When ripping tracks from an Audio CD, always save the tracks as <em>uncompressed</em> Wave files (or as lossless FLAC files) in order to avoid quality loss!</p><p><em>Warning:</em> The Windows Explorer will show CDA files (such as <code>Track01.cda</code>) on an Audio CD. These are just <em>dummy</em> files! Actually an Audio CD does <strong>not</strong> contain a file system. Thus there are <strong>no</strong> files either. There only are <em>audio tracks</em> on an Audio CD. These audio tracks <em>can</em> be extracted as files (e.g. Wave Audio files), by using a proper ripping software. Then the extracted files can be converted. At the same time, any attempt to convert the dummy <code>*.cda</code> files is <strong>not</strong> going to work!</p><h2id="q-is-there-a-way-to-use-custom-binaries-with-lamexp"><spanclass="header-section-number">9.8</span> Q: Is there a way to use <em>custom</em> binaries with LameXP?</h2><p>LameXP is a GUI front-end that uses a number third-party tools. All of these tools are already "built-in", with only a few exceptions. Therefore it is <strong>not</strong> normally required to provide separate binaries – LameXP uses the built-in binaries by default. If,however, you wish to use a <em>custom</em> (user-provided) binary, rather than the built-in binary, then this is still
