Skip to main content

Topic: why --vbr-new produce different file size ? (Read 7660 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • CharlyZ
  • [*]
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 ?

  • lvqcl
  • [*][*][*][*][*]
  • Developer
why --vbr-new produce different file size ?
Reply #1
"--vbr-new " is exactly 10 bytes long. So, check "COMMENT" tag in these mp3s.

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
why --vbr-new produce different file size ?
Reply #2
Ten bytes could simply be a difference in metadata (" --vbr-new" is ten characters long).  Did you compare the audio portion?
Is 24-bit/192kHz good enough for your lo-fi vinyl, or do you need 32/384?

  • CharlyZ
  • [*]
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 ?

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
why --vbr-new produce different file size ?
Reply #4
That's correct.  EAC adds a few extended tags: TENC (EncodedBy), TSSE (EncoderSettings) and TLEN (Length).
Is 24-bit/192kHz good enough for your lo-fi vinyl, or do you need 32/384?

  • CharlyZ
  • [*]
why --vbr-new produce different file size ?
Reply #5
How can i see those tag like TENC, TSSE ?

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
why --vbr-new produce different file size ?
Reply #6
mp3tag/foobar2000/hex editor
Is 24-bit/192kHz good enough for your lo-fi vinyl, or do you need 32/384?

  • CharlyZ
  • [*]
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
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.

  • greynol
  • [*][*][*][*][*]
  • Global Moderator
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.
  • Last Edit: 03 December, 2008, 02:14:51 AM by greynol
Is 24-bit/192kHz good enough for your lo-fi vinyl, or do you need 32/384?

why --vbr-new produce different file size ?
Reply #10
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.