Comment 11 for bug 63851

Tobias: I have archives of the Amarok mailing list going back two years and I have no record of an email from you to the list, which is probably why you never got a reply.

Anyways, as has already been discussed here, this is a TagLib bug, not an Amarok bug. There are reasons that it wasn't fixed before, one of which is that it takes an order of magnitude (or several) longer to calculate the correct length of a VBR file without a Xing header than with one -- and you'll incur this penalty every time the file is scanned or read. So really, the best answer by far is to pop a Xing header onto your file (in your case, once it's finished being ripped from a stream).

That being said, Scott Wheeler is currently in bugfixing mode (perhaps for an upcoming release?) and before he releases (or just when he gets the time) he likes to go and close all open bugs. The time it takes him to do that usually relates to the complexity of the patch and how long it takes him to verify correct functionality. http://bugs.kde.org/show_bug.cgi?id=130185 is still open so I guess he hasn't gotten to that yet.

So the best answer that anyone can give you right now is: We don't know when TagLib 1.5 will be released, but chances are this problem will be fixed, either through your patch or something similar, before then.