Amarok does not show correct total playing time of a playlist during first loading
Every time I add a playlist from saved playlists to the playlist pane, the total playing time of the playlist is incorrect, such as "24 tracks (0:04)." By accident I noticed 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 found many similar bug reports about Amarok, but all have since been tagged as resolved and nobody seems to be reporting this problem as having returned.
* Add one of the playlists from saved playlists to the playlist pane.
* Notice the incorrect total play time.
* Clear the playlist pane.
* Add the same playlist to the playlist pane.
* Notice the correct total play time.
The problem persists across restarts of Amarok. All is well with the total play times during a single session after the second loading but they are incorrect again the next time Amarok is started.
I've tried four different phonon backends: gstreamer, mplayer, xine, and vlc. I installed VLC from Eric's repo and then rebuilt phonon-vlc because I'm using 4.10.1 rather than 4.8.5. I don't think I need to rebuild VLC.
I don't know if the gstreamer plugins make a difference, but I did not have gst-bad or gst-ugly installed when I built the Amarok package.
Can anyone else confirm the problem?
Edit: Amarok 2.7.0 in KDE 4.10.1 on Slackware 14
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.
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.
I have KDE 4.10.1 but I noticed my amarok is 2.6 and there is a newer version 2.7 release in January, so maybe the bugs you found marked as fixed, were fixed in 2.7?
Oops! I forgot to mention I'm using Amarok 2.7.0 in KDE 4.10.1 on Slackware 14. So no, the problem exists in 2.7.0 if you are confirming. I filed a bug report if you want to add a comment.
|All times are GMT -5. The time now is 02:25 AM.|