lame 3.98.4, 3.99 alpha, 32- and 64-bit builds Options

[lvqcl]

The difference between them was a small digital 1-bit noise.

Really? Usually differences are much bigger.

tsnr (bakerweb.biz)

tsnr is not bakerweb.biz.

This post has been edited by lvqcl: Jan 26 2011, 17:35

[alter4]

3.99a contains the new VBR mode which enables with --vbr-new key. In other modes the result will be the same as for lame 3.98.4

Ha! AFAIK --vbr-new, which enabled a superior VBR mode in LAME 3.97 and some previous versions, is no longer needed with LAME 3.98 as it is now the default VBR mode
see Lame Wiki

This post has been edited by alter4: Jan 31 2011, 21:51

[IgorC]

It's vbr new 2.0

This post has been edited by IgorC: Jan 31 2011, 21:56

[john33]

So, now I must ask: which is the best? Of course, in terms of quality

That question has been asked many times before and to the best of my knowledge no one has yet been able reliably to differentiate between the outputs from the encoders compiled with different compilers. So it's safe to say that you can use whichever takes your fancy.

I asked the same question about different bitstream of 320 CBR encoded with two compiles. The difference between them was a small digital 1-bit noise. These could be the results of some processing optimizations.
But here we have different bitrates, and I think this is very strange and must affect quality.

Again:

john33 build - 191 kbps
tsnr (bakerweb.biz) - 185 kbps
lvqcl - 185 kbps

Sorry, but again, you may be able to see a difference, but can you hear one? The difference is only of any consequence if you can discern it accurately and repeatedly via blind listening tests.

[Fishman0919]

Does anyone know why this is not working anymore?

http://lame.cvs.sourceforge.net/viewvc/lam...tar.gz?view=tar

It will download a file but it is 0 bytes in size.


EDIT: Seems it's not work for some other programs as well.

This post has been edited by Fishman0919: Feb 7 2011, 23:18

[lvqcl]

http://www.hydrogenaudio.org/forums/index....st&p=741978

[Fishman0919]

http://www.hydrogenaudio.org/forums/index....st&p=741978

Thank You

[obones]

Hello,

I have Vegas Pro in 64bit version installed under Windows 7 x64 and I would like to use the lame codec inside it. I believe this is what lame64.acm is for but I can't find a way to install it properly.
I believe there should be a .inf file with it that would tell windows how to install it but it's not there.
Can any of you give me instructions for installing the acm file under Windows 7 64 bits ?

I have had a look at the rarewares website, but it does not seem to offer any x64 ACM build. There are instructions as to how to install under Win7 x64, but it's to install the x86 version that would then not be accessible to x64 applications

Thank you for your help

[tsnr]

LAME 3.99 alpha 12 (13 Feb 2011) - cvs snapshot

download (mediafire)

Changelog:

- make vbr_mt the default vbr mode
- new mono encoding switches:
-ml encodes left channel only
-mr encodes right channel only
- small fixes for compiler warnings
(vbrquantize.c) bug fix, out of bounds memory write
- reintroduction of fast encoding mode (-q7 / -f) (vbr_mt / vbr_mtrh)
- minor fix for sfb21 encoding (vbr_mt / vbr_mrth)
- small tunings


-----------------------------------------------------------------------
Win32:
lame.exe - the command line encoder, used from the Windows command shell
lame_enc.dll - LAME encoding library, generally used with CD rippers, etc
lame.acm - windows acm codec
libmp3lame.dll

x64:
lame64.exe
lame_enc64.dll
lame64.acm
libmp3lame64.dll

Bundle compiled with Intel Compiler XE 12.0

LAME MP3 Encoders (download homepage)

[obones]

I tried the x64 ACM codec as it includes an INF file this time but it crashes Vegas Pro so it seems it is not working.
Does anyone have any idea?

[IgorC]

Interesting. Now last alpha preserves frequencies up to 22 Khz (V0).

[Enig123]

What is vbr_mt exactly? And why it was set as default instead of the former vbr_new?

[Larson]

What is vbr_mt exactly? And why it was set as default instead of the former vbr_new?

If I've understood well, until the previous alpha to access the new vbr mode (vbr new 2.0 some have called it) you had to make the command "-VX --vbr-new" otherwise it worked with the older and regular vbr. Now as far as I've seen it is enabled by default, tested with dbpoweramp.

[Fishman0919]

What is vbr_mt exactly? And why it was set as default instead of the former vbr_new?

What is vbr_mt exactly? = a vbr routine build into Lame

The old vbr new was "--vbr-mtrh" (I assume by Mark Taylor and Robert Hegemann) ... now the new vbr new is "--vbr-mt" (I'm assumming by Mark Taylor)... There's also a "--vbr-rh" (assumming by Robert Hegemann) which I beleave is the vbr-old routine

EDIT: So it's still "-Vx --vbr-new or just -Vx" in the comandline.... it just routes to the vbr mt routine in Lame instead of vbr mtrh

This post has been edited by Fishman0919: Feb 21 2011, 08:33

[Aleron Ives]

If I've understood well, until the previous alpha to access the new vbr mode (vbr new 2.0 some have called it) you had to make the command "-VX --vbr-new" otherwise it worked with the older and regular vbr.

I think that is correct, although the way you said it might still be confusing, since "the older and regular vbr" is not --vbr-old. To be clear, the "old" VBR mode that used to be default in LAME 3.97 and previous versions (vbr-rh) was deprecated for the "new" VBR mode in LAME 3.98. The "new" VBR mode is vbr-mtrh. Because the new VBR mode was made default in LAME 3.98, using the --vbr-new switch didn't actually do anything, since --vbr-new (vbr-mtrh) was the default VBR mode.

In LAME 3.99, the developers began to work on more VBR improvements, so they made the --vbr-new switch enable those improvements. As of the latest alpha, the --vbr-new switch is no longer needed, and running in VBR mode will use the new encoding method by default (vbr-mt). What I don't know is whether this vbr-mt mode is the same vbr-mt that was deprecated around 2002 in favour of vbr-mtrh, or if this vbr-mt is just vbr-mtrh + improvements.

If I've gotten everything completely muddled, feel free to just delete this post so as to not confuse people further, haha.

[robert]

@Fisman0919: your guess about people involved in developing different variations of LAME's vbr code is correct.

There is some internal API enumeration of different VBR modes: vbr_rh, vbr_mt, vbr_mtrh
The command line switches to select one of those are: --vbr-old (vbr_rh), --vbr-mtrh and --vbr-new (vbr_mt)

It's been a long time, since the original vbr_mt code was discarded in favour of vbr_mtrh. The recent discrimination of vbr_mt and vbr_mtrh was only there to make experimentation easier for me. Now both modes do exactly the same again.


With 3.99 alpha 13 I'm starting to re-use some of the latest VBR code tunings in CBR/ABR.

[alter4]

@Robert

Sorry for a little bit off-top, but When do you plan to come into 3.99beta stage?

[john33]

Alpha 13 bundles are at Rarewares.

[robert]

@Robert

Sorry for a little bit off-top, but When do you plan to come into 3.99beta stage?

Probably in March...

[Fishman0919]

I noticed that alpha 13 is not inserting the Lame Header??

[robert]

Just checked john33's compiled binary, the header is there.
Do you do anything special? How do you call LAME? How do you determine the existence of the header?

This post has been edited by robert: Feb 24 2011, 18:20

[Fishman0919]

Just checked john33's compiled binary, the header is there.
Do you do anything special? How do you call LAME? How do you determine the existence of the header?

Both with Foobar2000 "-S --noreplaygain -V 2 - %d" and command line "lame.exe --noreplaygain -V 2 test.wav test.mp3"

In Foobar2000, it's not showing the ver of Lame used to encoder and EncSpot is showing Gogo 3.0 as encoder with the Lame Header showing just Xing Tag

This post has been edited by Fishman0919: Feb 24 2011, 18:39

[robert]

It seems, Foobar2000 assumes the "Encoder short VersionString" has to start with LAME.

This post has been edited by robert: Feb 24 2011, 18:47

[alter4]

@Robert

Sorry for a little bit off-top, but When do you plan to come into 3.99beta stage?

Probably in March...

Thank you Robert.

[Fishman0919]

Lame 3.99a14 is up... LINK -"http://www.mediafire.com/?7iva5wwo7ld4wr6"

This post has been edited by Fishman0919: Feb 27 2011, 20:12