[ lame-Bugs-3466159 ] Bug in VBR quality value?

SourceForge.net <[email protected]>
Newsgroups gmane.comp.audio.mp3.lame
Message-ID <[email protected]>
Bugs item #3466159, was opened at 2011-12-27 14:49
Message generated for change (Tracker Item Submitted) made by eblanca76
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100290&aid=3466159&group_id=290

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Elio Blanca (eblanca76)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bug in VBR quality value?

Initial Comment:
I've just built lame-3.99.3, I'm now performing a series of tests on an audio clip, just tweaking the encoding quality via the `-q' and the `-V' switches.
Now in the resulting mp3, sometimes the quality factor doesn't change with the `-q' value! So, when encoding `-q 0 -V 5' the quality byte stores 50 and when I set `-q 1 -V 5' that byte is still 50. When encoding `-q 2 -V 5' the quality value is 50 as well and the same happens with `-q 3' and `-q 4'.
This value changes for `-q 5', `-q 6' and `-q 7', then it remains 43 (the same as `-q 7') for `-q 8' and `-q 9', why?
Is the same quality used under some circumstances?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100290&aid=3466159&group_id=290

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.