VBR bitrate and time display bug of in_mp3

ttarchal · 14th March 2001, 18:01

Hi Winamp people

You really make people go through hoops just to submit a bug report to you... anyway, I searched this forum and saw similar bugs submitted a few times, but mine is slightly different and I have a sure way to replicate it.

Here's the Bug: With LAME-encoded VBR MP3's, if an ID3V2 header has been added, Winamp displays average bitrate even if jumping bitrate was selected in options. It also gets the playing time estimate wrong. The LAME options responsible are --addid3v2, or any of the ID3 fields spanning beyond the V1 limit, e.g. --tl "The Rise And Fall Of Ziggy Stardust And The Spiders From Mars".

To replicate:
* turn off average bitrage display on VBR files (in the in_mp3 input plugin options)
* encode a wav with LAME -V4 -q1
* encode another wav with LAME -V4 -q1 --addid3v2 --tc "A comment spanning more than 30 characters here"
* compare results; the second mp3's bitrate will display as average and time will be off

Why I think it's not a LAME bug:
* the MAD plugin plays both files correctly

Why I think it's not a VBR header bit bug:
* it doesn't matter if I use LAME -t or not

My config:
* WinAmp 2.73 (why does it still show 2.72 as latest on your site?)
* LAME 3.87b
* EAC is my ripper
* Windows 2000, no SP
* Athlon 800MHz w/quarter gig of RAM

And could you please autosort the files launched from Explorer in a multiple selection, too? I know this is a Windows bug but annoying.

Cheers
Tomasz

LameDude · 16th March 2001, 20:14

I get the same miss read of the time when I encode and play back the MP3s in Winamp. So is it the ID3v2 tags that mess the Mp3s? or confuses Winamp??
Can I fix it?

nogoro · 19th March 2001, 19:11

Hi

I use lyric display plugins on winamp and I notice that
the time display for mp3s (regardless of id tags) starts
off ok but gradually slows down compared to the song.
Gets to be about one second off pace and so the lyrics are
messed too.

The problem has persisted since before 2.6 I think...
When I want more accurate timing I use the shibatch mpg123
plugin, but it would be better if in_mp3.dll can do the
job too. (I like to set the buffer to 50mb so the whole
song gets copied to memory and doesn't have to seek the cdr
hehehe)

thanks for your attention.

16th March 2001, 20:14	#2
LameDude Junior Member Join Date: Mar 2001 Posts: 1	Ditto I get the same miss read of the time when I encode and play back the MP3s in Winamp. So is it the ID3v2 tags that mess the Mp3s? or confuses Winamp?? Can I fix it?

19th March 2001, 19:11	#3
nogoro Junior Member Join Date: Mar 2001 Posts: 1	similar problem Hi I use lyric display plugins on winamp and I notice that the time display for mp3s (regardless of id tags) starts off ok but gradually slows down compared to the song. Gets to be about one second off pace and so the lyrics are messed too. The problem has persisted since before 2.6 I think... When I want more accurate timing I use the shibatch mpg123 plugin, but it would be better if in_mp3.dll can do the job too. (I like to set the buffer to 50mb so the whole song gets copied to memory and doesn't have to seek the cdr hehehe) thanks for your attention.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

14th March 2001, 18:01	#1
ttarchal Junior Member Join Date: Mar 2001 Posts: 1	Hi Winamp people You really make people go through hoops just to submit a bug report to you... anyway, I searched this forum and saw similar bugs submitted a few times, but mine is slightly different and I have a sure way to replicate it. Here's the Bug: With LAME-encoded VBR MP3's, if an ID3V2 header has been added, Winamp displays average bitrate even if jumping bitrate was selected in options. It also gets the playing time estimate wrong. The LAME options responsible are --addid3v2, or any of the ID3 fields spanning beyond the V1 limit, e.g. --tl "The Rise And Fall Of Ziggy Stardust And The Spiders From Mars". To replicate: * turn off average bitrage display on VBR files (in the in_mp3 input plugin options) * encode a wav with LAME -V4 -q1 * encode another wav with LAME -V4 -q1 --addid3v2 --tc "A comment spanning more than 30 characters here" * compare results; the second mp3's bitrate will display as average and time will be off Why I think it's not a LAME bug: * the MAD plugin plays both files correctly Why I think it's not a VBR header bit bug: * it doesn't matter if I use LAME -t or not My config: * WinAmp 2.73 (why does it still show 2.72 as latest on your site?) * LAME 3.87b * EAC is my ripper * Windows 2000, no SP * Athlon 800MHz w/quarter gig of RAM And could you please autosort the files launched from Explorer in a multiple selection, too? I know this is a Windows bug but annoying. Cheers Tomasz