Skip to main content

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

0 Members and 2 Guests are viewing this topic.
  • Case
  • [*][*][*][*][*]
  • Developer (Donating)
Re: Lame 3.100 has been released
Reply #75
Your parameters are wrong. The right parameter for CBR is --cbr. The data gets treated as RAW PCM and it's assumed to be 16 bits.

  • knik
  • [*][*]
  • Developer
Re: Lame 3.100 has been released
Reply #76
I just did a little test with the most recent SVN code. It compiles smoothly and fast but the encoding speed is terribly low, about x7(default settings) vs x27 with lame 3.95.
Am I missing something?
  • Last Edit: 16 November, 2017, 04:59:56 AM by knik

  • knik
  • [*][*]
  • Developer
Re: Lame 3.100 has been released
Reply #77
Figured it out, gcc optimization flags are missing after recent compiler detection change. Latest lame cannot really be compiled with gcc.

Re: Lame 3.100 has been released
Reply #78
LAME development is culminated. Last quality changes were made 6 years ago.
In the other hand LAME developers have squeezed all out of what MP3 can do.

Thank You for release.

:) life continues ...


Couldn't have said it better...

Re: Lame 3.100 has been released
Reply #79
LAME development is culminated. Last quality changes were made 6 years ago.
In the other hand LAME developers have squeezed all out of what MP3 can do.

Thank You for release.

:) life continues ...

Couldn't have said it better...
Yeah, LAME has definitely reached its pinnacle ever since.

The finest MP3, as a format, will ever be.
  • Last Edit: 21 November, 2017, 04:16:29 PM by includemeout
Listen to the music, not the media.

Re: Lame 3.100 has been released
Reply #80
LAME development is culminated. Last quality changes were made 6 years ago.
In the other hand LAME developers have squeezed all out of what MP3 can do.

Thank You for release.

:) life continues ...

Couldn't have said it better...
Yeah, LAME has definitely reached its pinnacle ever since.

The finest MP3, as a format, will ever be.

Not according to some ABX. Also, it's extremely slow.

Re: Lame 3.100 has been released
Reply #81
I meant in terms of what LAME could milk, quality-wise, out of the MP3 format itself; as the problem samples detectable during ABX'ing seem to be inherent to that format.
Listen to the music, not the media.

  • tuxnowar
  • [*]
Re: Lame 3.100 has been released
Reply #82
hi everybody, anyone knows how can i pass the dB value computed with the --replaygain-accurate switch into the new --gain switch?

  • Brazil2
  • [*][*][*]
Re: Lame 3.100 has been released
Reply #83
i may be the sole user of lamedrop (xpd), but was wondering if you'd be able to update that too at some point?
+1
You are not alone :)

  • robert
  • [*][*][*][*][*]
  • Developer
Re: Lame 3.100 has been released
Reply #84
hi everybody, anyone knows how can i pass the dB value computed with the --replaygain-accurate switch into the new --gain switch?
As an example, the output was ReplayGain: -8.3dB then add --gain -8.3 to your command line.

  • tuxnowar
  • [*]
Re: Lame 3.100 has been released
Reply #85
hi everybody, anyone knows how can i pass the dB value computed with the --replaygain-accurate switch into the new --gain switch?
As an example, the output was ReplayGain: -8.3dB then add --gain -8.3 to your command line.
yes that is simple and even i managed to realize it. :)
but there is a way to do something like
lame -V 0 -S --gain $(--replaygain-accurate ) inputfile outputfile
just to encode with the right volume in one passage ?

  • robert
  • [*][*][*][*][*]
  • Developer
Re: Lame 3.100 has been released
Reply #86
Well, you could use wavgain to calculate replaygain, though it doesn't take mp3 specifics into account, it may be good enough.

To give you some example, take a look at the following bash script:
https://sourceforge.net/p/lame/svn/HEAD/tree/trunk/lame/misc/mk_mp3.sh

  • john33
  • [*][*][*][*][*]
  • Developer
Re: Lame 3.100 has been released
Reply #87
i may be the sole user of lamedrop (xpd), but was wondering if you'd be able to update that too at some point?
+1
You are not alone :)
LamedropXPd updated compiles are now on Rarewares. Sorry for the delay. ;)
John
----------------------------------------------------------------
My compiles and utilities are at http://www.rarewares.org/

  • Brazil2
  • [*][*][*]
Re: Lame 3.100 has been released
Reply #88
LamedropXPd updated compiles are now on Rarewares.
Thanks a lot! :)

A small glitch: even though the About window says "Using LAME 3.100.0" the Encoding Options window says "Using LAME 3.99.5 encoding engine".

  • john33
  • [*][*][*][*][*]
  • Developer
Re: Lame 3.100 has been released
Reply #89
Ooops!! That's only narrative, it was compiled using 3.100, but I'll make the change and upload again. Thanks for the 'heads up'. ;)
John
----------------------------------------------------------------
My compiles and utilities are at http://www.rarewares.org/

  • john33
  • [*][*][*][*][*]
  • Developer
Re: Lame 3.100 has been released
Reply #90
New LamedropXPd compiles uploaded with the narrative corrected. :)
John
----------------------------------------------------------------
My compiles and utilities are at http://www.rarewares.org/

  • izmo
  • [*]
Re: Lame 3.100 has been released
Reply #91
New LamedropXPd compiles uploaded with the narrative corrected. :)

thanks!

  • Slivka
  • [*]
Re: Lame 3.100 has been released
Reply #92
Here my tests:
Chocobo1 (msvc2017, nasm 2.13.01)
32bit - 68x
64bit - 58x
Files produced: same

--
Descrates (all are 32bits)
tmkk patch + clang 5.0 + icl 15 + msvc2010 lib + icl 15 lib - 76x
clang 5.0 with msvc2010 lib - 65x
msvc2005 - 47x

Files produced: same for clang versions, msvc2005 different than clang

--
Tmkk (gcc-5.4/MinGW)
32bit - 79x
64bit - 79x

Files produced: same

--
Rarewares (Intel Compiler)
32bit - 60x
64bit - 75x

Files produced: different, comparing says one of them produces 3 clicks at the beggining. Otherwise they null.


--
Foobar2000 (no compiler info)
32bit - 64x

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?
  • Last Edit: 09 December, 2017, 07:43:10 AM by Slivka

  • saratoga
  • [*][*][*][*][*]
Re: Lame 3.100 has been released
Reply #93
If there is any assembly in a program, and you aren't disabling assembly, then the 32 and 64 bit versions won't be running the same code paths. For this reason you shouldn't expect the results to be identical.

  • NetRanger
  • [*][*][*]
Re: Lame 3.100 has been released
Reply #94
L.A.M.E. v3.100
Built on December 12, 2017, GCC 7.2.0
http://lame.sourceforge.net

  • john33
  • [*][*][*][*][*]
  • Developer
Re: Lame 3.100 has been released
Reply #95
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. :)
John
----------------------------------------------------------------
My compiles and utilities are at http://www.rarewares.org/