Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Encoded with Lame 3.98, 3.98.2 or 3.9.4? (Read 12503 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Hello everyone,

I just wanted to know if there is any way to tell if my MP3 have been encoded with Lame 3.98.2, 3.98.3 or with 3.98.4.
Foobar and encspot just spot Lame 3.98r and do not tell me more.

Thank you.


Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #1
Mr Questionman might be able to do this.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #2
Also foobar2000 can show it (in the properties)

edit: I'm sorry, the mentioned LAME versions show the version, so this doesn't help.
In theory, there is no difference between theory and practice. In practice there is.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #3
Thank you twostar, I'll try that.

Also foobar2000 can show it (in the properties)

Are you sure with that? Foobar shows me 3.98r! Could be an add-on I don't have?

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #4
Hello everyone,

I just wanted to know if there is any way to tell if my MP3 have been encoded with Lame 3.98.2, 3.98.3 or with 3.98.4.
Foobar and encspot just spot Lame 3.98r and do not tell me more.

Thank you.



1: LAME writes its version info into the ID3v2 tag, if you used LAME to tag your files
2: LAME writes its version info into the ancillary data of each mp3 frame, if there is unused space available.
Make a hexdump from the last few bytes, it's likely that you find some version info there in the last frame.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #5
Thank you.
1. I use EAC + Lame.exe (-V3 %1 %2 or something like this)
2. Using this? Is there any "mass hexdumper"?


Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #7
Open up the file in a text editor like notepad and then search among the gibberish for the word "lame" followed by the version number, for example LAME3.98.4

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #8
Open up the file in a text editor like notepad and then search among the gibberish for the word "lame" followed by the version number, for example LAME3.98.4

That's fun!
Thank you for the suggestion but I would like something easier to deal with.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #9
That's about as easy as it gets.  Open notepad or any other text edit. Hit Ctrl+O and locate the mp3 file and open it.  Hit Ctrl+F and type in lame.  Done...

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #10
That's about as easy as it gets.  Open notepad or any other text edit. Hit Ctrl+O and locate the mp3 file and open it.  Hit Ctrl+F and type in lame.  Done...

Ho, I know that but when you have 900 albums that's another story!

I'm looking for something like what you can get in foobar (for example) when you type $info(tool) but that would give 3.98.4 and not 3.98r.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #11
Thanks, but it's really strange way to determine the LAME version... And I wonder why someone like Peter Pavlovsky can not add displaying of full LAME version info in foobar2000 file properties...
🇺🇦 Glory to Ukraine!

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #12
Code: [Select]
> grep -a -o "LAME[0-9.]*" ../test-0606/*.mp3
../test-0606/yello-V8-A.mp3:LAME3.98
../test-0606/yello-V8-A.mp3:LAME3.9
../test-0606/yello-V8-B.mp3:LAME3.99
../test-0606/yello-V8-B.mp3:LAME3.99
../test-0606/yello-V8-R.mp3:LAME3.97
../test-0606/yello-V8-R.mp3:LAME
../test-0606/yello-V9-A.mp3:LAME3.98
../test-0606/yello-V9-A.mp3:LAME3.98.2
../test-0606/yello-V9-B.mp3:LAME3.99
../test-0606/yello-V9-B.mp3:LAME
../test-0606/yello-V9-R.mp3:LAME3.97
../test-0606/yello-V9-R.mp3:LAME3.97

> grep "LAME3.98.2" ../test-0606/*.mp3
Übereinstimmungen in Binärdatei ../test-0606/yello-V0-A.mp3.
Übereinstimmungen in Binärdatei ../test-0606/yello-V1-A.mp3.
Übereinstimmungen in Binärdatei ../test-0606/yello-V2-A.mp3.
Übereinstimmungen in Binärdatei ../test-0606/yello-V3-A.mp3.
Übereinstimmungen in Binärdatei ../test-0606/yello-V4-A.mp3.
Übereinstimmungen in Binärdatei ../test-0606/yello-V5-A.mp3.
Übereinstimmungen in Binärdatei ../test-0606/yello-V6-A.mp3.
Übereinstimmungen in Binärdatei ../test-0606/yello-V7-A.mp3.
Übereinstimmungen in Binärdatei ../test-0606/yello-V9-A.mp3.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #13
I'm curious as to why LAME doesn't write the full version number in its tag in the first place... was there a specific reason for this?

@ robert

Seeing as he wants a foobar2000-esque plugin, it seems unlikely he has access to *nix tools like grep, haha.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #14
I'm curious as to why LAME doesn't write the full version number in its tag in the first place... was there a specific reason for this?

Because back in those days, the LAME tag was specified to contain 9 characters version info in textual form:
http://gabriel.mp3-tech.org/mp3infotag.html

Quote
@ robert

Seeing as he wants a foobar2000-esque plugin, it seems unlikely he has access to *nix tools like grep, haha.

http://unxutils.sourceforge.net/

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #15
Nice, I only have native tar and gzip.  Thanks.

You could use "LAME3984" if worse comes to worse, I suppose... It's too bad that limitation is in place.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #16
In Windows, you could just....

1.) Start -> Search -> Files and Folders

2.) In the "Search for files and folders named" field put "*.mp3"

3.) In the "Containing text" field put one of the following

LAME3.98.2

LAME3.98.3

LAME3.98.4


4.) In the "Look in:" field put the parent folder/directory you want to search.  If all your MP3 files are in a folder called D:\MP3 (with all the various subdirectories underneath) then put "D:\MP3" in this field.


Then click 'Search Now' to begin.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #17
In Windows, you could just....

1.) Start -> Search -> Files and Folders

2.) In the "Search for files and folders named" field put "*.mp3"

3.) In the "Containing text" field put one of the following

LAME3.98.2

LAME3.98.3

LAME3.98.4


4.) In the "Look in:" field put the parent folder/directory you want to search.  If all your MP3 files are in a folder called D:\MP3 (with all the various subdirectories underneath) then put "D:\MP3" in this field.


Then click 'Search Now' to begin.

Thanks but I can't find that on Windows 7!

Robert, how did you get that?



Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #20
a month or two ago, when Lame 3.98.3 first debuted, I raised the indeterminacy issue on Lame 3.98r.
http://www.hydrogenaudio.org/forums/index....showtopic=79059

Lame 3.98 (initial release) showed up in foobar2000, encspot, Mr Question Man, Audio Identifier, etc., as Lame 3.98
Lame 3.98.2 showed up as Lame 3.98r

However, Lame 3.98.3 and Lame 3.98.4 also show up as Lame 3.98r

When I encode using Lame 3.98.4 I add metadata to specify.
However, it would be nice to have this info accessible (e.g., showing up as the encoder in foobar2000) without having to tag.

I made the suggestion that a different letter could be added to replace the "r" in Lame 3.98r
Either "count" up from r, s, t, etc.
or just go Lame 3.98u (for "updated")

This could still be adopted if there is a Lame 3.98.5
God kills a kitten every time you encode with CBR 320

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #21
I don't see why "LAME3.984" can't be used. At least until LAME 3.100 (what would constitute v4, I wonder?), then we can drop the dot to buy more time.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #22
Quote
However, it would be nice to have this info accessible (e.g., showing up as the encoder in foobar2000) without having to tag.

Download any hex editor (XVI32 comes to mind).
Open Lame.exe in it. Find "LAME3.98r" string and replace "r" by "u" or "4".
???
Profit!

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #23
Going from the previous post I did a literal single character mod in LAME so it will read LAME3.984 instead of LAME3.98r and it works.

Since the forum doesn't allow MediaFire links I won't be able to post it on here, however the mod is stupidly easy to do in a hex editor - I did it on my first try and didn't blow up anything.

Encoded with Lame 3.98, 3.98.2 or 3.9.4?

Reply #24
I don't see why "LAME3.984" can't be used. At least until LAME 3.100 (what would constitute v4, I wonder?)

They had better figure out something to constitute version 4 soon, as they're almost out of version 3 sub-numbers.

I'd say starting development of a faster CBR/ABR routine on-par with VBR-new would constitute a significant enough jump to warrant version 4, but I can dream.