Lame Info tag contains information about number of MPEG frames in file, as well as about total number of bytes.

It looks like LAME stores file size as the latter value, but I think it would be better to store stream size, because various tags can be added or removed later.

By the way, foobar2000 (when using "fix header" command) stores exactly stream size.

Are there any official specifications clearing this issue?

I too, agree that it would make much more sense to store the stream size since storing the file size is close to useless. At best, it'll be the same as the file size (which we can already easily determine by looking at ...the filesize) and if we add any kind of tagging after the initial lame encode (as I'm sure 99.9% of all files encoded are), it becomes useless, except maybe for easily determining if the file has received new tags or not (but not modifications that cause no size change).

My 2 cents,
Daniel

P.S. I'm not pretending to know what's best for lame in the company of the folks on this forum, this is just my humble opinion.

No official reply from the Lame devs?

It would be great if ring0 could make his app work "in synch" with lame (or vice-versa!)

Perhaps a lame command-line parm to decide if stream size or file size is written in header??

To me it should be stream size.

I'm glad you agree, Gabriel. How does one go about requesting this kind of change in future versions of lame?

Thanks,
Daniel