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: why --vbr-new produce different file size ? (Read 10236 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

why --vbr-new produce different file size ?

Hello,
I've encoded the same song twice, one with the --vbr-new switch and the other without it.
The song was ripped with EAC and encoded with LAME 3.98.2

ie : one song with :
-V 2 %s %d

and the same song with :
-V 2 --vbr-new %s %d

Then i looked up the size :

Song with --vbr-new : 7 212 327 bytes

Song without --vbr-new : 7 212 317 bytes

The LAME wiki page says that the --vbr-new switch is the default VBR mode and is no longer needed so 'im wondering why the two files are not the same.

Does someone know ?

why --vbr-new produce different file size ?

Reply #1 –
"--vbr-new " is exactly 10 bytes long. So, check "COMMENT" tag in these mp3s.

why --vbr-new produce different file size ?

Reply #3 –
The comment field say "Track 5". I let EAC tag my mp3.
I use winamp 2.95 to check tag.

You are surely right about this. So somewhere in the metadata, EAC has written the command line used to encode ?

why --vbr-new produce different file size ?

Reply #5 –
How can i see those tag like TENC, TSSE ?

why --vbr-new produce different file size ?

Reply #7 –
Thank you, it's clear for me now

why --vbr-new produce different file size ?

Reply #8 –
Quote from: greynol on
That's correct.  EAC adds a few extended tags: TENC (EncodedBy), TSSE (EncoderSettings) and TLEN (Length).


Are you sure?  I've encoded several CDs in 3.98.2 recently, and only TLEN and TSSE are written.  TSSE is always written as "LAME 32bits version 3.98.2 (http://www.mp3dev.org/)" which seems more like what should be written as TENC.  I would like LAME to automatically write my input parameters in the ID3, but it doesn't seem to.

why --vbr-new produce different file size ?

Reply #9 –
Yes, I'm sure.  It seems like you missed the posts that show the OP is using EAC to tag the files instead of Lame.

This discussion has nothing to do with having Lame write tags.

why --vbr-new produce different file size ?

Reply #10 –
Quote from: greynol on
Yes, I'm sure.  It seems like you missed the posts that show the OP is using EAC to tag the files instead of Lame.

This discussion has nothing to do with having Lame write tags.


Doh!  Stupid me, you're right, I read EAC as LAME for some reason.