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: Lame header? (Read 3752 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Lame header?

I know that Lame by default writes its header with Lame version/vbr info/lowpass/psymodel etc. When the "-t" switch is used, it should disable Lame header. But it seems to do not disable it completely - when the mp3 file is analyzed in Encspot, it still knows which Lame version was used even when the file was encoded with the "-t" switch. So where does Lame squeeze its version info???

Thx, J.M.

Lame header?

Reply #1 –
Enscpot does not determine what Lame verion is used (or even that the codec used was Lame) from the Lame header.

Lame and its version can be found at the end of the file.

Lame header?

Reply #2 –
Quote from: greynol on
Enscpot does not determine what Lame verion is used (or even that the codec used was Lame) from the Lame header.

Lame and its version can be found at the end of the file.

So this means that the Lame version will ALWAYS be stored at the end of the file no matter what switches I use?

Lame header?

Reply #4 –
Quote from: greynol on
I'd say this is a safe assumption to make.  Do you mind if I ask why you don't want a Lame header?  True gapless playback will be impossible without one.

I was just wondering how Encspot was getting the version without the Lame header 

J.M.

Lame header?

Reply #5 –
AFAIK LAME includes its own version string into the bitreservoir to fill space that's wasted anyways. Something along those lines. (Usually at the start/end when there's silence).

Lame header?

Reply #6 –
...nevermind...
--alt-presets are there for a reason! These other switches DO NOT work better than it, trust me on this.
LAME + Joint Stereo doesn't destroy 'Stereo'
 

Lame header?

Reply #7 –
Quote from: jmartis on
So this means that the Lame version will ALWAYS be stored at the end of the file no matter what switches I use?
Whenever LAME needs to insert non-audio data to pad a frame it includes its own version string. The contents of this padding data are completely irrelevant to the mp3 decoder, btw. Zero bytes or random data or secret messages could be included, too.

Most (but not all) files encoded by LAME contain padding data and thus the encoder version string. Also, a tool like mp3packer can be used to strip padding data from mp3 files without changing the audio data.

So, the answer to your question is: no, not always.