Any ETA on when we can expect a fully compatible mp3 reader from foobar2000 ?

most likely when people delete all broken mp3 files from their hard drives. or when they send their broken mp3 files to me so proper fix can be added.

Delete 'broken' mp3s from harddrive... hmmm, NO.
Send their broken mp3's? ok, to which email/ftp/etc ?

I have one too. But it is 6MB!

PM me to get ftp info.

jsheridan: this file has corrupted id3v2 tag, you should blame the person who wrote tagging software used on it, or just blame inventors of id3v2 for making one of shittiest "standards" ever. i'll see if i can hackfix this, but don't expect wonders...

No problem, don't read the cursed tag, just ignore the damn thing (I hate mp3tagv2 as well). However, a crash is out of the order in this case.

yeah, except your pretty id3v2 tag is almost 1 meg in size (WTF ? someone included a BITMAP FILE ?), regular "ignore-garbage-at-the-beginning-of-stream" routine has no chances against it, contents of BMP data are happily pretending to be valid mpeg headers.

so, I guess, you'll need a id3v2-skipping-system for a start

Why, yes, the ID3v2 standard does list that as one of its features. Seems stupid to be including BMP instead of JPG, though. Hurray for packing in album art, I think.

I thought id3v2 only list PNG in supported image formats.

RIV@NVX: file "fixed" after deleting all msvc temp crap and rebuilding entire project tree (damn i hate when this happens).
apparently fb2k has exceeded "critical mass" where msvc compiler bugs start to mass-appear (eg. one of templates is always compiled with wrong parameter in debug mode).

you could try fixing those MPA streams with BeSplit.

OK, thanks! What about version numbering I asked you?

Some of my old 128k blade mp3s (yes I know.. it was before I found this forum) have a very sharp glitching sound at the beginning (WA 2.81 sounds ok)

I will upload 1 or 2 samples to my webspace and PM Peter the links (hope thats ok)