Lame 3.100 has been released

Topic: Lame 3.100 has been released (Read 57523 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

Re: Lame 3.100 has been released

Reply #100 – 2018-01-14 00:11:23

Quote from: Slivka on 2017-12-09 12:41:01

Looks like Rarewares build is fastest without patches. But the problem is 32bit & 64bit versions don't null and three pops appear in beggining of one of the files (when null compared). I have no idea why if they use same Intel Compiler.
Maybe it should be recompiled again?

What program do you use for this comparison? Those pops are not audible for you?

Quote from: john33 on 2017-12-12 22:05:50

I've re-compiled and uploaded the lame bundles. The 32 bit version appears unchanged, but there is a difference with the 64 bit version. Personally, I can't hear a difference, but maybe someone can do a more exhaustive check.

I have compared 4 files encoded with your 64-bit version compiled in October and in December. Binary comparator in foobar2000 says "no differences found".
BTW, I am converting using foobar2000 converter. Is it in any way important that I am inititating 64-bit LAME encoder from foobar2000 which is 32-bit program?

Re: Lame 3.100 has been released

Reply #101 – 2018-01-14 08:22:51

Quote from: inrobert on 2018-01-14 00:11:23

Quote from: john33 on 2017-12-12 22:05:50
I've re-compiled and uploaded the lame bundles. The 32 bit version appears unchanged, but there is a difference with the 64 bit version. Personally, I can't hear a difference, but maybe someone can do a more exhaustive check.
I have compared 4 files encoded with your 64-bit version compiled in October and in December. Binary comparator in foobar2000 says "no differences found".
BTW, I am converting using foobar2000 converter. Is it in any way important that I am inititating 64-bit LAME encoder from foobar2000 which is 32-bit program?

I didn't expect there to be any difference between the Oct and Dec compiles, I just re-checked the compile options just to be sure that I hadn't missed something the first time round.

I also usually convert using Foobar as you specify and, no, that isn't an issue.

Re: Lame 3.100 has been released

Reply #102 – 2018-01-14 13:37:42

Quote from: john33 on 2018-01-14 08:22:51

I didn't expect there to be any difference between the Oct and Dec compiles, I just re-checked the compile options just to be sure that I hadn't missed something the first time round.

"Slivka" was saying that your "32bit & 64bit versions don't null and three pops appear in beggining of one of the files (when null compared)" so I thought you are recompiling to check if this is eliminated

Are those "pops" even confirmed? As I understand 32-bit and 64-bit compiled versions can produce slightly different files in encoding, but I don't know what he meant by "three pops in the beginning". Three pops that can be heard or just three bits with different values?

Re: Lame 3.100 has been released

Reply #103 – 2018-11-22 04:00:55

tmkk patch + fastcrc patch + clang 8.0 snapshot (Full LTO) + msvc2010 lib

Re: Lame 3.100 has been released

Reply #104 – 2018-12-09 18:29:03

Quote from: izmo on 2017-11-14 05:52:41

I may be the sole user of lamedrop (xpd) . . .

Quote from: Brazil2 on 2017-11-28 10:14:15

+1
You are not alone

Me too. LameDropXPd has been my "go-to" Lame frontend for a long time.

Quote from: john33 on 2017-11-29 21:11:56

New LamedropXPd compiles uploaded with the narrative corrected.

Thanks John. And for all the work you do for making our music enjoyment better.

Artie

Re: Lame 3.100 has been released

Reply #105 – 2019-01-13 12:46:55

Why when compressing to V0 there's 20kHz lowpass on 3.100 when in LAME 3.99 that lowpass was removed? I know I should listen with my ears not eyes and I'm not saying 3.99 sounds better because of this, but I'm just curious why it was removed in 3.99 and then added again in 3.100. Thank you for help.

Re: Lame 3.100 has been released

Reply #106 – 2019-01-13 13:24:13

Code: [Select]

lame.exe -V0 test.wav

LAME 3.100 32bits (http://lame.sf.net)
CPU features: MMX (ASM used), SSE (ASM used), SSE2
polyphase lowpass filter disabled
Encoding test.wav to test.mp3
Encoding as 44.1 kHz j-stereo MPEG-1 Layer III VBR(q=0)

So no, there's no 20 kHz lowpass.

Re: Lame 3.100 has been released

Reply #107 – 2019-01-13 14:21:30

Maybe there's no lowpass filter, but comparing to 3.99r there's much less audio above 20kHz:
Spoiler (click to show/hide)

I'm using LAME 3.100 64bit build from RareWares if that matters.

Re: Lame 3.100 has been released

Reply #108 – 2019-01-13 15:02:11

Quote from: Kanapka on 2019-01-13 14:21:30

I'm using LAME 3.100 64bit build from RareWares if that matters.

Are you REALLY sure?

Re: Lame 3.100 has been released

Reply #109 – 2019-01-14 01:27:30

I just tested 3.100-2 (-2 being a distribution second edition, -1 would be the first release of that version).

Top is original, bottom is 3.100 -V0.

Re: Lame 3.100 has been released

Reply #110 – 2019-01-21 18:25:49

It seems that there is some bug in original build from tmkk. On some files when encoding with -S --noreplaygain -V 0 encoder crashes with error and resulting mp3 file is corrupted.

Code: [Select]

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
LAME 3.100 32bits (http://lame.sf.net)
CPU features: MMX (ASM used), SSE (ASM used), SSE2
polyphase lowpass filter disabled
Encoding D:\Music\I Love Disco Diamonds Collection\I Love Disco Diamonds Collection Vol. 14\02. Yeti.wav
      to D:\Music\I Love Disco Diamonds Collection\I Love Disco Diamonds Collection Vol. 14\02. Yeti.mp3
Encoding as 44.1 kHz j-stereo MPEG-1 Layer III VBR(q=0)
Assertion failed!

Program: D:\0__CODECS\Lossy\LAME\3.100\lame_tmkk.exe
File: ../../libmp3lame/vbrquantize.c, Line 948

Expression: vbrsf[sfb] >= vbrsfmin[sfb]

Windows 7 32 bit, core i3 3245
File is too long to share here, but if someone is interested, i can send link in PM. It is track #2 from CD #14 from compilation "I Love Disco Diamonds Collection"

Re: Lame 3.100 has been released

Reply #111 – 2019-01-22 14:03:57

tmkk already reported the bug and a fix is in SVN.

https://sourceforge.net/p/lame/bugs/496/

https://sourceforge.net/p/lame/svn/6438/tree//trunk/lame/libmp3lame/vector/xmm_quantize_sub.c?diff=59e1c885dab7b929b5817e2e:6437

Seems like you are running a debug version.

Re: Lame 3.100 has been released

Reply #112 – 2019-01-22 14:21:14

Quote from: robert on 2019-01-22 14:03:57

tmkk already reported the bug and a fix is in SVN.

https://sourceforge.net/p/lame/bugs/496/

https://sourceforge.net/p/lame/svn/6438/tree//trunk/lame/libmp3lame/vector/xmm_quantize_sub.c?diff=59e1c885dab7b929b5817e2e:6437

Seems like you are running a debug version.

Is compiled binary with fix available somewhere? I used binary from tmkk's site dated 2017.10.14

Re: Lame 3.100 has been released

Reply #113 – 2019-01-24 10:20:51

Binaries of LAME snapshot [r6438] https://sourceforge.net/p/lame/svn/HEAD/tree/trunk/lame/ with
https://tmkk.undo.jp/lame/lame-3.100-sse-20171014.diff and
https://freac.org/patches/lame-3.100-fastcrc.diff patch applied.

Re: Lame 3.100 has been released

Reply #114 – 2019-02-27 05:06:03

tmkk patch + fastcrc patch + clang-cl 9.0 snapshot (Full LTO, SSE2 (ASM used) forcing, AMD procie target) + msvc2013 lib (WinXP SP3)

btw unstable

Re: Lame 3.100 has been released

Reply #115 – 2019-05-21 04:50:36

Quote from: descrates on 2019-02-27 05:06:03

tmkk patch + fastcrc patch + clang-cl 9.0 snapshot (Full LTO, SSE2 (ASM used) forcing, AMD procie target) + msvc2013 lib (WinXP SP3)

btw unstable

Hello friend, can you tell me how to compile Lame encoder?I like this small and easy-to-use coding scheme very much, so I want to delve into it.
Can you tell me?I look forward to your reply, best wishes.

Re: Lame 3.100 has been released

Reply #116 – 2019-05-21 04:53:36

Perhaps,
You can also record a video the next time you make it.
English is not very good, I'm sorry

Re: Lame 3.100 has been released

Reply #117 – 2019-06-20 04:23:50

Quote from: HydrogenAudioFans on 2019-05-21 04:50:36

Quote from: descrates on 2019-02-27 05:06:03
tmkk patch + fastcrc patch + clang-cl 9.0 snapshot (Full LTO, SSE2 (ASM used) forcing, AMD procie target) + msvc2013 lib (WinXP SP3)

btw unstable

Hello friend, can you tell me how to compile Lame encoder?I like this small and easy-to-use coding scheme very much, so I want to delve into it.
Can you tell me?I look forward to your reply, best wishes.

compile lame via clang-cl?
in simplest (as example)
1st install msvc/visual studio 2017 x64
[or 2010/2013/2015 etc]

then...

1. download clang x64 snapshot or stable for windows
   open with 7zip (keep default msvc's config)
   (1) select file
1. clang-cl.exe
2. lld-link.exe
3. llvm-lib.exe
copy & paste into /bin/ in "VC folder" (/bin/HostX64/x64/)
[in visual studio folder]
rename llvm-lib.exe -> lib.exe
[1st backup msvc's lib.exe]
   (2) select all folder in /lib/
copy & paste into /lib/ in "VC folder" (/lib/x64)
[in visual studio folder]

2. download nasm for windows
   open with 7zip
   select file -> nasm.exe
   copy & paste into /bin/ in "VC folder"
   [in visual studio folder]
   rename nasm.exe -> nasmw.exe

3. edit makefile.msvc (in /lame-svn-?-trunk/lame/)
   [in msvc config section]
   replace string
   cl -> clang-cl [flags]
   link -> lld-link /force [flags]
   link -> lld-link /force /DLL [flags] to combating lame_enc.dll
   then save

4. select file -> lame.h "lame header file"
   (in /lame-svn-?-trunk/lame/include/)
   copy & paste into /include/ in "VC folder"
   [in visual studio folder]

5. open visual c++ command prompt
   cd /lame-svn-?-trunk/lame/
   nmake -f makefile.msvc lame_enc.dll
   cd output

6. if visual studio 2019 + clang-cl can create lame.exe
but "no speed" in Win10

   (1) grab lib
grab libmmt.lib & libirc.lib from intel compiler lib
grab libucrtbase.a from mingw-w64 runtime 6.0
rename libucrtbase.a -> libucrt.lib
copy & paste into /lib/ in "VC folder"
[in visual studio folder]
[1st backup msvc's libucrt.lib]
   (2) linking into libmmt.lib
edit /frontend/main.obj
replace string
libcmt.lib -> libmmt.lib
   (3) _strnlen missing in parse.obj
open msvc's libucrt.lib with 7zip
search strnlen.obj
copy & paste into /lib/ in "VC folder"
[in visual studio folder]
convert strnlen.obj -> custom.lib
edit /frontend/parse.obj
replace string
libcmt.lib -> custom.lib

Re: Lame 3.100 has been released

Reply #118 – 2019-09-16 05:08:17

tmkk patch + clang 9.0 snapshot (Full LTO, Intel procie target) + msvc2013 lib + icl17 lib

no fastcrc patch (contra with icl17 lib)

Re: Lame 3.100 has been released

Reply #119 – 2020-03-28 04:36:03

tmkk patch + clang 10.0 snapshot (Full LTO, psymodel w/ -fveclib=SVML (SVML exp2 forcing), Intel procie target) + msvc2010 lib + svml 15 lib

-V0 & -V1 "higher" bitrate testing