Correct check for lame info tag from versions before 3.95.1

Hi,

I've stumbled over an old TODO in mpg123 for taking into account that
older LAME versions used 83 dB as reference for ReplayGain instead of
89 dB. I read that this change happened in 3.95.1 .
Now, as I don't have all LAME releases of the past 10 years installed,
what is a robust test for versions before that? The relevant encoder
string has 9 characters, the first of which are "LAME", leaving 5
characters for the release number, right?

I see such strings (ignore the "Note: Info: Encoder: ", that's from
mpg123 -vvv output):

Note: Info: Encoder: LAME3.97 
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.70
Note: Info: Encoder: LAME3.70
Note: Info: Encoder: LAME3.70
Note: Info: Encoder: LAME3.97 
Note: Info: Encoder: LAME3.92 
Note: Info: Encoder: LAME3.95 
Note: Info: Encoder: LAME3.95 
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.95 
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.95 
Note: Info: Encoder: LAME3.95
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.97
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.96r
Note: Info: Encoder: LAME3.90.
Note: Info: Encoder: LAME3.92
Note: Info: Encoder: LAME3.96r

At least after version 3.90.x, somebody seems to have noticed that this
three-part version number does not fit into the 5 characters left.
So... I suppose "LAME3.95 " is from 3.95.0. How does the string from
3.95.1 look, exactly? Is it "LAME3.95r"?

I see that madplay 0.15.2b added code for this situation, trying to
parse the numerical part into "%u.%u.%u", what is a bit difficult with
two digits in the middle and only 5 characters total...

I'd be grateful for a simple info on what version number parsing is
safe here.


Alrighty then,

Thomas.


PS: Is it already possible that LAME writes an audiophile ReplayGain
value? The docs and available files say No. Is there a specific reason
why there is no mode to compress a set of files together and compute
audiophile gain from the set? Actually, I'd already be happy to provide
both ReplayGain values to lame on the command line, as I take compute
those values externally already. But then, writing a stand-alone tool
that just changes those values in the header would also work, only that
must have a look at the LAME version and adjust for 6 dB if it's an old
file;-)

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/

_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev