Re: Testers needed for current SVN version of LAME

Michael Fink via Lame-dev <[email protected]> Fri, 21 Aug 2020 21:19:09 +0200
Newsgroups gmane.comp.audio.mp3.lame
Message-ID <[email protected]>
Hi Alexander, hi lame-dev list,

> We have now updated Windows project files. Can anyone please validate
> them (more or less to validate that I didn't destroy something)?

I've tested compiling LAME using the new project files, downloading the 
revision 6471. Compiling worked, and I could use the new libmp3lame.dll 
in winLAME without problems (I'm the maintainer of winLAME). Since the 
project files were created by me, I'm a bit biased :-) So for anyone who 
wants to compile LAME using the latest Visual Studio 2019 (I used 
16.7.1), here's the command line I used:

c:\temp\lame-svn-r6471-trunk\lame\vc_solution> msbuild 
vs2019_libmp3lame_dll.vcxproj /m /property:Configuration=Release 
/property:HaveMpg123=true

Before that I extracted the mpg123 binaries to the folder 
lame\vc_solution\mpg123. I used this Win32 binary package:
https://mpg123.de/download/win32/1.26.3/mpg123-1.26.3-x86.zip

The compiled libmp3lame.dll and the libmpg123-0.dll from the zip works 
well with winLAME.

I also compiled lame.exe with the mpg123 integration. I tested both 
transcoding an existing .mp3 file and decoding an .mp3 file to .wav 
(using the --decode switch). Both output files sound OK. Although the 
lame.exe outputs the message "Could not close audio input file" at the 
end of transcoding and decoding. This might be a Win32 issue, which I'll 
look into.

Note: Compiling without the /property:HaveMpg123=true switch currently 
doesn't work, since the project files are already made for when 
Alexander applies Step 2 (removing the old mpglib).

Cheers,
Michael