diff --git a/doc/Changelog.html b/doc/Changelog.html index 7acf80a6..42446259 100644 --- a/doc/Changelog.html +++ b/doc/Changelog.html @@ -20,7 +20,7 @@ a:visited { color: #0000EE; }
  • Upgraded build environment to Microsoft Visual Studio 2010
  • Dropping support for Windows 2000 and for Windows XP RTM/SP1, Windows XP needs SP2 or SP3 now!
  • Added a new translation: Korean -
  • Added a method to use custom tools instead of the "built-in" ones (see FAQ doc for details) +
  • Added a method to use custom tools instead of the "built-in" ones (see FAQ doc for details)
  • Updated LAME encoder to v3.99.1.0 (2011-04-15), compiled with ICL 12.0.3 and MSVC 10.0 (details)
  • Updated MediaInfo to v0.7.43 (2011-04-10), compiled with ICL 12.0.3 and MSVC 10.0
  • Updated language files (big thank-you to all contributors !!!) diff --git a/doc/FAQ.html b/doc/FAQ.html index 6f70426f..b790de54 100644 --- a/doc/FAQ.html +++ b/doc/FAQ.html @@ -32,6 +32,7 @@ a:visited { color: #0000EE; }
  • Is there a way to output ".m4a" or ".aac" files with LameXP?
  • How do I enable WMA input (decoding) in LameXP?
  • How can I use LameXP as a "portable" application? +
  • Is there a way to use custom tools (binaries) with LameXP instead of the "built-in" ones?
  • The LameXP startup (splash screen) takes very long on my system. What can I do?
  • Why does application 'xyz' not open the Wave files created by LameXP?
  • Why does LameXP run only 'n' parallel instances/threads on my computer? @@ -335,6 +336,27 @@ write-access is granted to the directory where the LameXP executable is located.

    +Is there a way to use custom tools (binaries) with LameXP instead of the "built-in" ones?
    +
    +LameXP uses a number third-party tools. All of these tools are already "built-in" (with a few exceptions) and
    +thus it is NOT required to provide separate binaries. Usually it will NOT be necessary to replace any of
    +the "built-in" tools with a custom (user-provided) binary. If, however, you need to replace/update/downgrade
    +one of the binaries for a good reason, the recommended method is re-building LameXP from the sources. If you
    +don't know how to build LameXP from the sources, then you probably shouldn't be trying to replace the binary.
    +
    +Having said that, there now is a more convenient method for using a custom tool version (binary) instead of
    +the "built-in" one. This method works WITHOUT re-building LameXP. However note that the following is intended
    +for testing and debugging purposes only! Also note that LameXP was specifically designed to work with the
    +"built-in" versions of the tools. It may not work properly or may not work at all with custom tool versions!
    +
    +In order to replace a "built-in" binary, simply put the user-provided binary to the following location: +
    <install_folder>\tools\<build_number>\<tool_name>.exe
    +If, for example, you want to replace 'lame.exe' in Build #666 of LameXP, you would put it to the this path: +
    C:\Path to your LameXP install folder\tools\666\lame.exe
    +(It is intended that the '<build_number>' part of the path has to be adjusted with every update of LameXP)

    + +

    + The LameXP startup (splash screen) takes very long on my system. What can I do?

    Starting up LameXP shouldn't take longer than approximately 10 seconds. However it was brought to our
    diff --git a/src/Config.h b/src/Config.h index 38ab8b32..089d7e7d 100644 --- a/src/Config.h +++ b/src/Config.h @@ -30,7 +30,7 @@ #define VER_LAMEXP_MINOR_LO 2 #define VER_LAMEXP_TYPE Alpha #define VER_LAMEXP_PATCH 4 -#define VER_LAMEXP_BUILD 448 +#define VER_LAMEXP_BUILD 449 /////////////////////////////////////////////////////////////////////////////// // Tools versions