I would try to use MP3val on those files instead and see what shows in fb2k afterwards... Should be OK then.
How about Rebuild MP3 stream?
Quote from: db1989 on 01 June, 2012, 07:45:37 PMHow about Rebuild MP3 stream?I am considering trying this out too, but I'm curious what exactly it does (how the file is affected) and I haven't been able to find much information yet.
Some experimentation reveals that the estimate will be always be wrong in this situation (CBR file, no VBR header), because fb2k apparently doesn't account for the 529 samples of decoder delay that it strips during decoding. I consider this to be a bug in foobar2000. It should be reporting durations 529 samples smaller than what it is actually reporting.
But ... what harm does an inaccurately reported length really do? OK, I've downloaded (oops, did I say that?) bootleg recordings with extremely wrong lengths (like, many times the true length), and of course it might be annoying to see Cage's 4'33" displayed as 4:32 ... but AFAIK, foobar2000 will play them the same?
It's not correct to think that the encoder delay is always 529, in fact it varies between different encoders.
Quote from: markanini on 02 June, 2012, 08:27:31 AMIt's not correct to think that the encoder delay is always 529, in fact it varies between different encoders.Encoder delay is the delay added by the encoder. Like padding, encoder delay is silence (or junk) samples actually encoded into the MP3. It's not normally removed during playback or conversion, unless the # of samples is written into a LAME tag.But I was talking about decoder delay, the delay added by the decoder to the output stream as the MP3 is processed. The decoder used by foobar2000 has a 529-sample delay, and foobar2000 always strips these samples during playback or conversion. When estimating the duration of CBR files, though, it's not subtracting those samples.