Bug 129098

Summary:	song lengthes are sometimes incorrect
Product:	[Unmaintained] taglib	Reporter:	Wenli Liu <wenlil>
Component:	general	Assignee:	Scott Wheeler <wheeler>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Wenli Liu 2006-06-13 17:16:38 UTC

Version:           1.4-4 (using KDE KDE 3.4.2)
Installed from:    Compiled From Sources
Compiler:          G++ 3.3.5 
OS:                Linux

Mostly taglib computes song lengthes correct but on some mp3 files, it does not(way from the correct length).

I checked the existing bugs and I think this is bug with tablib, or with the mp3 file. I will try to attach the sample mp3 file.

Comment 1 Wenli Liu 2006-06-13 17:21:22 UTC

Hi Scott, the mp3 file is too big to attach here. I have sent it to wheeler@kde.org. Thanks!

Comment 2 Scott Wheeler 2006-06-13 17:22:00 UTC


*** This bug has been marked as a duplicate of 86926 ***

Comment 3 Scott Wheeler 2006-06-13 17:26:12 UTC

Oops -- wrong (but similar) bug.  I think this is because of the the lack of VBR headers.  (This is actually a difficult one to fix because it requires scanning every frame of the file to find the correct length.  See #70649)

Comment 4 Debajyoti Bera 2006-10-01 18:26:56 UTC

I reported a similar problem here:
http://bugs.kde.org/show_bug.cgi?id=128388

Note that in #128388, mp3fixer.rb (amarok script to 'fix' such problems) writes a XING header (which I think is a VBR header). But even after that incorrect value is returned by taglib. Here incorrect means - its not what the actual length is and its also not what the XING header contains.

Scott, the file in question is a bit large to attach. You probably have lots of such defective files. Let me know if you need the one I have. Thanks.

Comment 5 Scott Wheeler 2008-02-01 03:40:33 UTC

I looked back into this and there are actually two problems with the file:  one is that the stream is corrupted and additionally, once repairing that with an external tool it's still a VBR file without a Xing header.  Since I don't really care about getting the right length on corrupted streams, I'm marking this as a duplicate of the Xing header thing.

*** This bug has been marked as a duplicate of 130945 ***