MediaMonkey forum

Owyn wrote:Hmmm.
Codecs.com does not show a reference to that release.

I don't have "rarewares.org" on my trusted list, so, skipping this update (for now).

You can trust rarewares.org, they only did a compiled version of the tar.gz present on http://sourceforge.net/projects/lame/

Owyn, I have used the rarewares site for many years.

Ahh. Thanks. I see the file release (1 day ago) on lame.

I put this on my 30 day followups. Not critical to have latest, and, I like to give any new bugs time to surface. It also gives it time to migrate to my known good providers.

Thanks again.

MusicBringer wrote:Owyn, I have used the rarewares site for many years.

Sue me, I'm paranoid about software downloaded from the Internet. But, you are not really paranoid if they are really out to get you.

Owyn wrote:

MusicBringer wrote:Owyn, I have used the rarewares site for many years.

Sue me, I'm paranoid about software downloaded from the Internet. But, you are not really paranoid if they are really out to get you.

Yeah, I think I might understand.

By the way. You know it always rains after a drought.

And just to let dBpoweramp users know. They have updated to LAME 3.98.3 with R13.4.

No problem. I use and test a lot of software. 3.98.3 is probably great,and I will be using it, but, my update policies require:

- Notification by a trusted source (which in some cases is the developer)
- No obvious conflicts with my current configuration (e.g. I am still on FF3.5.8 due to FF3.6 conflicts with two required add-ons)
- After a waiting period to let any problems surface. Lame falls into the class of critical applications that I can not easily test myself.

Consequence of new problems is potentially bad rips or transcodes until problem corrected.
Consequence of delayed install. Possibly slower or suboptimal encodes to MP3. Need to read the full release notes to know.

Just in case anyone missed it, LAME 3.98.4 was released on March 22nd

gpzbc wrote:Just in case anyone missed it, LAME 3.98.4 was released on March 22nd

Yeah, I did miss it actually.

Here is a direct download link.

Me Too. Thanks gpzbc

Hi Guys. Help please.

If I put the v3.98.4 lame_enc.dll file into my MM programs folder (usually C:\program files\mediamonkey) then all new rips and transcodes to mp3 will use this new encoder?

What can I do to ensure that MM uses the v3.98.4 lame.exe decoder to play all my existing mp3's?

you will need to find the name of the encoder used by monkey. change that name by adding a number to it.
by adding the number to it you make the file unseen by monkey so you then just
rename the lame encoder the name that monkey had his encoder called just don't add the number to it.

@rovingcowboy Thanks for the quick reply. I seem to have the Lame encoder issue. I am now concerned about the "playback" of my MP3s.

I want to be sure that MM uses the latest lame to playback my mp3s. How do I do that?

technofool wrote:@rovingcowboy Thanks for the quick reply. I seem to have the Lame encoder issue. I am now concerned about the "playback" of my MP3s.

I want to be sure that MM uses the latest lame to playback my mp3s. How do I do that?

Lame is an encoder, not a decoder. Therefor, it's used to create MP3s (such as when you rip a CD or convert another file into MP3) but it's not used to play back the file. Unless I'm mistaken?

Mizery_Made wrote:

technofool wrote:@rovingcowboy Thanks for the quick reply. I seem to have the Lame encoder issue. I am now concerned about the "playback" of my MP3s.

I want to be sure that MM uses the latest lame to playback my mp3s. How do I do that?

Lame is an encoder, not a decoder. Therefor, it's used to create MP3s (such as when you rip a CD or convert another file into MP3) but it's not used to play back the file. Unless I'm mistaken?

That's the way I understand it to be. But I'm no professional.