[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 130185] Wrong (halfed) play times for mono/single channel mp3
From:       Jeff Mitchell <kde-dev () emailgoeshere ! com>
Date:       2006-12-23 14:55:45
Message-ID: 20061223145545.14206.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=130185         
kde-dev emailgoeshere com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From kde-dev emailgoeshere com  2006-12-23 15:55 -------
After some discussion with developers, we've decided to mark this invalid.  The Xing \
header exists for exactly this purpose and is supported by TagLib.  It's about ten \
years old and there's no reason any modern encoder doesn't put it on.

If we did a workaround to calculate the length from all the frames, it could slow \
down collection scanning by a good deal at best and several orders of magnitude at \
worst, depending on how many broken VBR MP3s a person has and what filesystems \
they're stored on.

The best thing for you to do is swamp LugRadio with complaints and get them to use a \
good encoder.  They're a Linux podcast...why aren't they using LAME, which besides \
having excellent sound quality, does support adding Xing headers?  (All my music is \
encoded this way with --vbr-new, and I have verified that the Xing headers do exist \
and the correct length is calculated.)

As a side fix, take a look at markey's mp3fixer script at

http://www.kde-apps.org/content/show.php?content=31539

This will fix broken frames and add Xing headers to your VBR files if they don't \
exist already.  Be warned that you should back up any important MP3s you run this on \
first, as in very rare cases it can cause some damage.


[prev in list] [next in list] [prev in thread] [next in thread]