LAME 3.99.5 - where to get?

[LoRd_MuldeR]

Does anybody know what the status of LAME v3.99.5 is?

According to the changelog, it was released this February:
http://lame.cvs.sourceforge.net/viewvc/lame/lame/doc/html/history.html

However there is no source code package in the file release system yet:
http://sourceforge.net/projects/lame/files/lame/3.99/

Also there is no tag for v3.99.5 in their CVS repository, as far as I can tell.

So do I have to build from CVS HEAD this time? :confused:

[burfadel]

I don't know who manages or uploads this, all I know of is it existence and that it has thus far been safe to use (been using them ever since http://lame.bakerweb.biz/ hadn't been updated (September 2010).
http://www.mediafire.com/lame

They're updated reasonably frequently (check the 'old' folder for example), and they do have the LAME 3.99.5 version, and also have been uploading of 3.100 alpha's. The alphas and betas are well worth checking out, even if just from an interest point of view. I haven't come across a bad one yet.

[LoRd_MuldeR]

I'm not looking for binaries. I want to make them myself :)

What I'm looking for is the "official" source code for LAME v3.99.5, which I can't seem to find anywhere yet (see above).

Sure, I could build straight from CVS HEAD, but that might already include soem post v3.99.5 changes.

Usually they make a Tag in their CVS repository for each release version. But apparently this has not happened this time.

Or it's still pending. I don't know...

[burfadel]

From what I could find looking up the LAME sourceforge pages, the official LAME page, and other sites quickly, the latest version is officially 3.99.4, making 3.99.5 a pre-release version. Thats why you can't find the sourcecode for it, since it was probably built straight from the CVS. I would say the released sourcecode for 3.99.5 won't be available until 3.99.5 is completely finalised.

[LoRd_MuldeR]

Seems like v3.99.5 indeed has not been released yet, although it's not marked as "not yet released":
http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=93308&view=findpost&p=786321

[smok3]

any special reason that you need uberlatest lame?

[burfadel]

Much better than running LAME 3.96 and even earlier like some people still do :) (not suggesting you do, just using that as an example)!

[LoRd_MuldeR]

any special reason that you need uberlatest lame?

I don't want to use an "uberlatest" LAME. I want to use the latest stable release ;)

Since v3.99 has been released quite some time ago, v3.99.x is the current stable series. Development is going on in the v3.100 branch.

So far, v3.99 has seen four maintenance/bugfix releases. If they now have another one, I certainly want to update to that one.


Especially the following fixes in v3.99.5 seems to be important:
Fix for a problem when LAME is compiled with fast floating point math. It could result in bitrate bloat with silent input data.
Bug fix for tracker item [ 3486753 ] Artifacts at the beginning of decoded file.

[hajj_3]

compiled versions of 3.99.4 are on http://free-codecs.com/Lame_Encoder_download.htm if that is any help.

[LoRd_MuldeR]

compiled versions of 3.99.4 are on http://free-codecs.com/Lame_Encoder_download.htm if that is any help.

Nope. If you read the topic, you will noticed that this was not about pre-compiled binaries...

[burfadel]

As you know I made that mistake too :) the first post didn't make it clear of that intention. That said, you did correct that assumption further down! :)

In terms of the sourcecode, its probably best that you use the CVS. Aren't the commits in the CVS actually kind of mini-releases in themselves, and that versioned releases are done only to make it definitive? such that the guideline of when they bump the revision is one based on the number of fixes or time lapsed since the last release, or a combination of the two, and not explicitly based on a set rule defining the version bumps?

[LoRd_MuldeR]

Binaries that have been built from CVS "HEAD" generally have to be handled with care, because they may contain new fixes/improvements, but they may also contain new regressions or experimental stuff that simply needs more testing. The developers know best when it's time to "freeze" the current state as a new release version. That's also the reason why you will find a Tag ("snapshot") for each release version in the CVS repository. The source code package that is offered for download (over the SourceForge.net file release system) matches exactly that CVS Tag. The only reason why there was some confusion recently is that v3.99.5 appeared on the "version history" as if it was already released. But in fact it was not. Consequently there was no Tag and no source code package for v3.99.5 yet. It's now clarified that v3.99.5 is a work in progress (http://www.hydrogenaudio.org/forums/index.php?showtopic=93308&st=50&p=786321&#entry786321) and I will wait until they are done...

[LoRd_MuldeR]

Binaries that have been built from CVS "HEAD" generally have to be handled with care, because they may contain new fixes/improvements, but they may also contain new regressions or experimental stuff that simply needs more testing. The developers know best when it's time to "freeze" the current state as a new release version. That's also the reason why you will find a Tag ("snapshot") for each release version in the CVS repository. The source code package that is offered for download (over the SourceForge.net file release system) matches exactly that CVS Tag. The only reason why there was some confusion recently is that v3.99.5 appeared on the "version history" as if it was already released. But in fact it was not. Consequently there was no Tag and no source code package for v3.99.5 yet. It's now clarified that v3.99.5 is a work in progress (http://www.hydrogenaudio.org/forums/index.php?showtopic=93308&st=50&p=786321&#entry786321) and I will wait until they are done...

It's out now :D

[Midzuki]

^ Thanks for the info, downloading from Rarewares :devil: right now, also pestering Baldrick@Videohelp again :D