Bug 128095 - songs longer than 3:08:06 shows up as 3:08:06 long
Summary: songs longer than 3:08:06 shows up as 3:08:06 long
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: general (other bugs)
Version First Reported In: 1.4.0
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-26 22:46 UTC by pug
Modified: 2006-06-11 12:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Sample screenshot (8.48 KB, image/png)
2006-05-27 14:16 UTC, Peter C. Ndikuwera
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pug 2006-05-26 22:46:29 UTC
Version:           1.4.0 (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When playing an mp3 that's 8.5 hours long (~700 mb file, 192 kbit) the mp3 shows up as having a length of 3:08:06. I don't think there's supposed to be that kinda limit. Not sure if the limit is due to time or filelength.

Amarok will play the tune, but you are not able to search in it as the search bar only goes from 0 - 3:08:06 (should be 8:30:XX). You can search / fastforward in other players in mp3s that long, including xmms (linux) and winamp (windows).

I hope it gets fixed as I have quite a few mp3s longer than 3.08 hours ;-).

-pug
Comment 1 Peter C. Ndikuwera 2006-05-27 14:16:13 UTC
Created attachment 16297 [details]
Sample screenshot

Here's a screenshot of a long mp3 of mine. Definitely more than 3:08 hours!
Comment 2 Mark Kretschmann 2006-05-31 10:55:23 UTC
Peter: Does the seek slider work correctly though?

I can't debug it, as I don't have such a long file :(
Comment 3 Peter C. Ndikuwera 2006-05-31 13:06:01 UTC
It seeks perfectly well.
Comment 4 pug 2006-06-02 23:48:07 UTC
Turns out I must once upon a time have used a faulty program to change id3 tags on quite a number of my mp3s. 

This gave rise to a header failure in those mp3s, which led Amarok to misread the length (or whatever happend). Apparently it was only a problem for mp3s longer than 3 hours, so I haven't noticed it until now.

The faulty files showed correct length in xmms and winamp. Not in Amarok. After first deleting the id3 tag, then remaking it everything works like a charm in Amarok and the correct length is shown for all files.

*hits self over the head for not seeing this before reporting it* 

My bad.

-pug