Bug 220612 - Track length is shown as 0:00 for all songs at a DAAP share
Summary: Track length is shown as 0:00 for all songs at a DAAP share
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: Collections/DAAP (show other bugs)
Version: 2.3.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-30 00:20 UTC by Diederik van der Boor
Modified: 2011-09-27 06:12 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.4.3


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Diederik van der Boor 2009-12-30 00:20:56 UTC
Version:           2.2.1 (using 4.3.4 (KDE 4.3.4) "release 2", KDE:43 / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.5-0.1-desktop

The songs at my DAAP share (mt-daapd daemon) all have a track length of 0:00 according to amarok.

This also produces a weird display for the "remaining time" label in the toolbar.
Comment 1 Thorsten Hirsch 2010-01-13 01:12:20 UTC
I can confirm this bug. I think the problem has been there in all Amarok 2.x releases.
Comment 2 Julian Pietron 2010-03-01 13:55:45 UTC
Confirm it, too. I cannot recall a 2.x version where DAAP showed track length.
Comment 3 Myriam Schweingruber 2010-03-02 10:09:04 UTC
Changing to confirmed.
Comment 4 Martin Kucko 2010-03-27 14:12:57 UTC
I found this depends on _when_ song has been added into amarok collection. Some songs which has been added before ver. 2.x has 0:00 time but when You for example change file name, amarok scans it again and time is correct from now.

Tested on amarok 2.2.2
Comment 5 Sven Krohlas 2010-03-27 14:26:06 UTC
Martin, you realized this is about DAAP shares? I guess you are talking about a local collection: you have to rescan it due to a bug we introduced. Sorry for that.
Comment 6 Martin Kucko 2010-03-27 16:51:06 UTC
Sorry, I missunderstant this description. I thought it's about local collection. My fault.
Comment 7 emil.ostwald 2010-04-22 14:24:02 UTC
Can confirm it to.
Comment 8 Andrea 2010-05-14 14:23:38 UTC
I also can confirm this bug in Amarok 2.3.0 (I'm using Ubuntu 10.04).

Has anyone found a solution or workaround for this?
Comment 9 Thorsten Hirsch 2010-06-15 22:05:40 UTC
Problem still exists in 2.3.1.

Thorsten
Comment 10 Myriam Schweingruber 2011-09-26 16:29:40 UTC
Is this still valid with Amarok 2.4.3 or current git?
Comment 11 Thorsten Hirsch 2011-09-26 17:54:01 UTC
Solved in 2.4.3.
Comment 12 Myriam Schweingruber 2011-09-27 06:12:01 UTC
Great news, thank you for the feedback :)