LameXP v4.18 Final · Build #2240 (2019-12-18)

[LoRd_MuldeR]

LameXP v4.19 Beta-2
https://sourceforge.net/projects/lam...8.exe/download

Changes between v4.18 and v4.19 [unreleased]
* Updated Vorbis encoder to OggEnc v2.88 (2020-07-07), using libvorbis v1.3.7 with aoTuV beta-6.03
* Updated Monkey's Audio binary to v5.54 (2020-08-24), compiled with ICL 19.1 and MSVC 15.9
* Updated mpg123 decoder to v1.26.3 (2020-07-16), compiled with GCC 10.1.0
* Updated MediaInfo to v20.08 (2020-08-11), compiled with ICL 19.1 and MSVC 15.9
* Updated cURL to v7.72.0 (2020-08-19), with libcurl v7.72.0 and OpenSSL v1.1.1g
* Added command-line switch --no-splash, which can be used to hide the "splash" screen at startup

[tormento]

Originally Posted by LoRd_MuldeR

LameXP v4.19 Beta-2

Couple of days the service is unavailable on downloading.

Strange enough, only one mirror has the download file.

Can you please provide a mirror? Binary expired here

[manolito]

SourceForge downloading can be a bit unreliable...

What always works here is to click on "Problems Downloading?" and then choose the "Direct Link". Just checked for the latest Beta-2, no problems.

[LoRd_MuldeR]

Originally Posted by tormento

Couple of days the service is unavailable on downloading.

Strange enough, only one mirror has the download file.

Can you please provide a mirror? Binary expired here

Just checked, and all of the 16 update mirrors seem to be up and synchronized, so you should always be able to get the latest version via "auto-update" function:
https://pastebin.com/6vhtLuZi

As far as problems with SourceForge.net downloads are concerned, there is not much I can do about this, but I just downloaded the latest version from SourceForge.net without any problem.

[LoRd_MuldeR]

LameXP v4.19 Beta-3
https://sourceforge.net/projects/lam...0.exe/download

Changes between v4.18 and v4.19 [unreleased]
* Updated LAME encoder to v3.100.1-SVN (2020-08-25), compiled with ICL 19.1 and MSVC 15.9
* Updated Vorbis encoder to OggEnc v2.88 (2020-07-07), using libvorbis v1.3.7 with aoTuV beta-6.03
* Updated Monkey's Audio binary to v5.54 (2020-08-24), compiled with ICL 19.1 and MSVC 15.9
* Updated mpg123 decoder to v1.26.3 (2020-07-16), compiled with GCC 10.1.0
* Updated MediaInfo to v20.08 (2020-08-11), compiled with ICL 19.1 and MSVC 15.9
* Updated cURL to v7.72.0 (2020-08-19), with libcurl v7.72.0 and OpenSSL v1.1.1g
* Added command-line switch --no-splash, which can be used to hide the "splash" screen at startup

LAME v3.100.1 Release
This is a point release that includes NO changes to the encoding libraries.
This release replaces the previous mpglib decoding library with the libmpg123 decoding library.

[MrVideo]

I notice while starting the program on my XP-32 box, it warns that dwnapi.dll is missing. Doing a little bit of research, I find out that its use starts with Vista. OK, but the strange part is that versions for XP-32 can be found and downloaded.

Is dwmapi really needed and what is it used for with regards to LameXP? I'm guessing that it isn't really important, since the program runs just fine without it.

[LoRd_MuldeR]

Some Windows API functions are only available in newer Windows versions. If we linked these functions statically, then the executable would no longer be able to run on "old" Windows versions.

The workaround is to import these "optional" functions dynamically, at runtime, via LoadLibrary() and GetProcAddress(). This way, we can use the new API functions where available, but still continue without them otherwise.

Specifically, the DWM (Desktop Window Manager) is only available in Windows Vista an later. LameXP uses DwmEnableBlurBehindWindow() from Dwmapi.dll to enable fancy "Aero" effects on support OS versions.

[MrVideo]

Thanks for the update. Certainly doesn't bother me that blur effects are missing.

[MrVideo]

Slight problem... the beta has expired. I know, it keeps working. That is why it is slight.

Another slight problem... when trying to check for a new version, the beta says that my internet connection is broken. It isn't.

[LoRd_MuldeR]

Originally Posted by MrVideo

Another slight problem... when trying to check for a new version, the beta says that my internet connection is broken. It isn't.

Not quite sure. Nothing about the update check should have changed recently

Can you can press F11 in the update window to show the log?

[MrVideo]

Here is the result:

Checking your Internet connection...

Connecting to host: www.ebay.com

ERROR: Terminated with unknown code -1073741515

Connecting to host: www.gnu.org

ERROR: Terminated with unknown code -1073741515

Connecting to host: bandcamp.com

ERROR: Terminated with unknown code -1073741515

Connecting to host: neocities.org

ERROR: Terminated with unknown code -1073741515

Connecting to host: www.avidemux.org

ERROR: Terminated with unknown code -1073741515
[...]
Connecting to host: support.proboards.com

ERROR: Terminated with unknown code -1073741515

Connecting to host: www.oxford.gov.uk

ERROR: Terminated with unknown code -1073741515

Connecting to host: www.jd.com

ERROR: Terminated with unknown code -1073741515

Connecting to host: marknelson.us

ERROR: Terminated with unknown code -1073741515

Connecting to host: www.libav.org

ERROR: Terminated with unknown code -1073741515


Connectivity test has failed: Internet connection appears to be broken!

Just a subset of the list. All sites exit with the some code. I have no clue has to how you are trying to connected to these locations. A simple ping of 8.8.8.8 would be a great test.

[nevcairiel]

-1073741515 is C0000135, which means "DLL not found". Some component involved in the connection process is not present.

[LoRd_MuldeR]

Originally Posted by MrVideo

Here is the result:

Checking your Internet connection...

Connecting to host: www.gnu.org

ERROR: Terminated with unknown code -1073741515

Originally Posted by nevcairiel

-1073741515 is C0000135, which means "DLL not found". Some component involved in the connection process is not present.

Well, it would indicate that cURL process failed to start, apprently because of a missing DLL.

If I remember correctly, you are one of those diehard Windows XP users. Not that we should care at this point, but for me the cURL binary that ships with LameXP works fine on my Windows XP (with SP-3) VM:



You could try opening the "lxp_curl.exe" form the LameXP "temp" directory with Dependency Walker and see if it reveals anything...

[danlock]

Something I've intended to mention for quite a while... (It seems to be cosmetic only (NOT? SEE EDIT!), but it is confusing nonetheless.)

When I transcode one or more files to (an) Opus file(s), regardless of the Quality / Bitrate setting on the Compression tab, if I set a different bitrate in the OpusEnc text entry box in the Custom Encoder Parameters portion of the Advanced Options tab), the resulting file's ENCODER_OPTIONS: tag contains an extra artifact from the Compression tab.

In this example, the Compression tab was set to ≈ 144 kbps and my custom parameter was --bitrate 150, which resulted in the following ENCODER_OPTIONS tag:

ENCODER_OPTIONS : --vbr --comp 10 --framesize 20 --bitrate 144 --bitrate 150

The resulting file is the same as if the setting from the Compression tab were not present; the file is identical to one encoded with --bitrate 150. Either the second --bitrate option supersedes the first one on the command line, the setting from the tab is being inserted into the tag prior to the custom setting, or both.

I guess it's NOT cosmetic only (Edit #2: my mistake... it is only cosmetic, as LoRd_MuldeR reminded me (below)):

I just re-encoded the same file with a higher bitrate on the Compression tab (≈160) and got a larger file (tag says ENCODER_OPTIONS : --vbr --comp 10 --framesize 20 --bitrate 160 --bitrate 150), which remained larger/160kbps when I changed to 12kbps and re-encoded (custom still set to 150, tag says ENCODER_OPTIONS : --vbr --comp 10 --framesize 20 --bitrate 12 --bitrate 150) , but removing the custom option completely gave me a tiny file with an overall (VBR/quality) bit rate of 12.5 kbps. The tag ends with --bitrate 12 as it should.

Over the years since the Compression tab's --bitrate=??? text has been visible in the ENCODER_OPTIONS tag prior to the custom value, I have noticed no other strange tagging issues when I've had settings on the "ordinary" tabs that differ from any custom options I have set. I haven't tested exhaustively.

I'm using the latest beta, but I've noticed the tagging issue for many, many months and versions.

-------------
I was in a hurry at the end when I posted this yesterday. I neglected to thank you for your help and response, LoRd_MuldeR. I'll insert it now (Sunday 06.December 2020) and in this message to avoid creating another message at the bottom of the thread. Thank you! ...and I was right the first time: it is only cosmetic. Thanks for pointing that out, too!

[LoRd_MuldeR]

Well, it is not under our control what exactly OpusEnc stores in the "ENCODER_OPTIONS" meta tag. That's an OpusEnc thing.

Anyways, it would appear that OpusEnc simply stores the "raw" (full) command-line, not just the effective encoder options. This explains why you will see "--bitrate" twice, iff you add "--bitrate" to the "Custom Encoder Parameters": LameXP already generates the "--bitrate" option for you, based on the selected bitrate, on the "Compression" tab. Consequently, if you add that option again, as a custom parameter, you'll end up with two times "--bitrate" in the command-line.

Furthermore, the general convention for conflicting command-line options is that the last one takes precedence. And that is exactly what OpusEnc seems to follow here