I'm been encoding some wavs off of CDs using the builds on 
dkutsanov's website.  I found an odd change in lame encoding when 
going from lame383a1_f to lame383a1_f. (day before yesterday to 
yesterday).

I am encoding my files with -m j -h -v -V 2 -b 96

On all previous builds of lame, in VBR encoding I have never gotten 
frames requiring bitrates greater than 256.  As of yesterday evening, 
just after the announcement of the 383 beta, the version I pulled down 
has been encoding more than 1% of all my wavs frames with a bitrate 
of 320.

If I understand correctly (and I probably dont) cd ripped wavs are by 
definition using a bitrate of 256.  So... there should never be call to 
need a bitrate of 320 to encode frames - correct?

I'm pretty new to this, but I think the latest VBR fixes or the filter bank 
changes have accidentally thrown something off in the VBR bitrate 
evaluation.

All FYI, just my $0.02


Stephen Anderson
[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

Reply via email to