QUOTE(Alex B @ Oct 28 2005, 04:06 AM)
QUOTE(beowulf7 @ Oct 28 2005, 08:57 AM)
The vast majority of my MP3s are 192 kbps CBR. Then someone opened my mind (and ears!) to VBR, so I'm very much interested (and just getting started) w/ VBR. I am using LAME 3.96.1 and VBR'd a WAV file to MP3. But the time length displayed on Winamp 5.11 is incorrect. Someone in another thread noticed the same "phenomenom". The bug is either with VBR or Winamp. Since both have been around for many years, who knows.

I don't think it is a LAME VBR issue in case the files are correctly encoded. I tried to reproduce this with Winamp 5.11. I used the default Nullsoft v.3.31 decoder, Thompson mp3PRO decoder and Otachan's version of the mpg123 decoder. They all showed the same correct track lengths. It seems that Winamp reads the VBR header info correctly with all decoders. I have no idea how Winamp works, but some other programs read a small amount of frames in the beginning of the files and estimate the bitrate and track length if a compatible VBR header is not available.
I don't know if this helps anything, but you could try the Otachan's mpg123 decoder:
http://www.hydrogenaudio.org/forums/index....18530&hl=mpg123.
I used LAME 3.96.1 and tried various "--preset" options for VBR and even ABR. Both displayed incorrect times. I have a 72:43 mix and while both showed "72:43" on Winamp, when I actually played the files, by the time the last track finished, the finish times were around 72:46 or 72:47. This is really bad for me b/c I'm an e-DJ and having the proper track time is a vital requirement, especially for the cue files that I make.
So as much as what I'm about to say will be painful to many eyes and ears on the board, I've decided to stay with CBR 192 for my mixes. For individual tracks, where the displayed track time is not as important, I'll probably go with "--preset extreme", which is a VBR around the 220-250 kbps area.
Maybe the official release of LAME 3.97, whenever that comes out, will fix this. I assume the beta version of LAME 3.97 has the same bug. Yes, I'm blaming this on the VBR heading encoding of LAME rather than Winamp.