Bug 316751 - Amarok does not show correct total playing time of a playlist during the first loading
Summary: Amarok does not show correct total playing time of a playlist during the firs...
Status: CONFIRMED
Alias: None
Product: amarok
Classification: Applications
Component: Playlist (show other bugs)
Version: 2.8.0
Platform: Slackware Linux
: NOR normal
Target Milestone: 2.8
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-15 01:35 UTC by Woodsman
Modified: 2014-08-24 09:17 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing minus sign in toolbar time (273.23 KB, image/png)
2013-03-15 23:58 UTC, Woodsman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Woodsman 2013-03-15 01:35:09 UTC
I'm a new user of Amarok 2. Importing all of my previous Amarok 1.4 data went well. After importing I performed some nominal spot checks to ensure the statistical data imported correctly, such as play counts and last played.

Every time I added a playlist from saved playlists to the playlist pane, I noticed the total playing time of the playlist was incorrect such as "24 tracks (0:04)."

By accident I noticed that after I cleared the playlist pane and then again added the same playlist from my saved playlists, the total time would be correct, such as "24 tracks (1:15:50)".

I'm using 2.7.0 on KDE 4.10.1.

I found many similar bug reports, all resolved, but looks like this bug has returned in 2.7.0.

Reproducible: Always

Steps to Reproduce:
1. Add one of the playlists from saved playlists to the playlist pane.
2. Notice the incorrect total play time.
3. Clear the playlist pane.
4. Add the same playlist to the playlist pane.
Actual Results:  
The total playlist time is always incorrect the very first time the playlist is added to the playlist pane but is correct thereafter.

Expected Results:  
Correct total play times for the playlist.

The problem persists across restarts of Amarok. All is well with the total play times during a single sessions after the second loading but they will be incorrect again the next time Amarok is started.
Comment 1 Myriam Schweingruber 2013-03-15 12:08:25 UTC
I presume your Phonon backend is gstreamer, try the vlc backend instead (you will have to restart KDE so it takes effect). I have the vlc backend here and the total payling time shows correctly for me.
Comment 2 Woodsman 2013-03-15 15:17:58 UTC
Oof. Such a simple request that ends up taking more than an hour of testing. :) The stock Slackware does not include the VLC backend so I had to build the package. End result is the same: incorrect time.

I tested the xine and mplayer backends as well ---  four backends in all. Yes, I restarted KDE each time. With that said, as the times are correct for you and as I stated in the original report about not finding related new bug reports, I'll lean toward me doing something incorrectly here. Not sure about the next step but I'll post a parallel query in the Slackware forum.
Comment 3 Woodsman 2013-03-15 16:21:21 UTC
A new observation:

In my saved playlists, with a playlist _not_ expanded in the tree view, using Add to Playlist or Replace Playlist results in the incorrect total playtime with the first load. Clearing the playlist pane and then reloading in the playlist pane results in the correct time.

In my saved playlists, with a playlist expanded in the tree view, using Add to Playlist or Replace Playlist results in the correct total playtime.

This is with the gstreamer backend.
Comment 4 Woodsman 2013-03-15 18:14:23 UTC
I received one confirmation from another Slackware user using KDE 4.10.1 and Amarok 2.6.0:

"Yes, I have recreated the same issue you have with playlist saved as files on disk, but the playlists in amarok database don't seem to have the same problem."
Comment 5 Myriam Schweingruber 2013-03-15 20:51:53 UTC
About the other phonon backends: ditch those the only two backends actively developped are the gstreamer and the vlc one.

Changed component to "Saved playlists", as it is not the playist itself that causes problem, I presume you have correct lengths showing when files are already in the playlist or newly added from the collection.
Comment 6 Woodsman 2013-03-15 23:20:29 UTC
The individual times of each song in the playlist pane all look correct. The toolbar time for the currently playing song matches the time in the playlist pane but is always oddly preceded by a minus sign.
Comment 7 Myriam Schweingruber 2013-03-15 23:38:35 UTC
(In reply to comment #6)
> The individual times of each song in the playlist pane all look correct. The
> toolbar time for the currently playing song matches the time in the playlist
> pane but is always oddly preceded by a minus sign.

Could you please attatch a screenshot of that? I have never seen a minus sign on ym toolbar.
Comment 8 Woodsman 2013-03-15 23:58:51 UTC
Created attachment 78102 [details]
Screenshot showing minus sign in toolbar time

Notice the toolbar time of -2:09, which is the time remaining. The absolute value is correct but I don't know where the minus sign comes from. Of course, my previous post about total time is correct when the song starts, not for the whole song. :)
Comment 9 Myriam Schweingruber 2013-03-16 01:08:48 UTC
Sorry, my bad, I misread the minus sign being in the playlist ttotal time, never mind.
Comment 10 Matěj Laitl 2013-05-28 18:25:08 UTC
The problem is the (main) playlist, updating component. I was able to reproduce.
Comment 11 Myriam Schweingruber 2014-08-11 21:22:26 UTC
Is this still valid with Amarok 2.8.0?
Comment 12 ruuhnr 2014-08-24 07:50:44 UTC
This is still valid for 2.8.0

This bug has many different effects on the playlist time. Sometimes the time is correct but when more tracks are added no time, or am incorrect amount will be added. When the tracks are removed from the playlist a seemingly random amount of time will be subtracted.
At other times the adding or subtracting of tracks has no effect at all. Sometimes there is no time shown at all.

I switched the backend to vlc, but no effect.
Comment 13 Myriam Schweingruber 2014-08-24 09:17:15 UTC
Thank you for your feedback.

And no, changing the backend shouldn't have an effect on this at all, as it is in Amarok code, not in Phonon.