Summary: | Amarok doesn't submit fo last.fm the last track in the playlist | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Matteo Agostinelli <agostinelli> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | duplode_1, jrobot, lfranchi, pete |
Priority: | NOR | ||
Version: | 2.0-SVN | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Matteo Agostinelli
2008-07-26 20:20:43 UTC
Same for me on current 2.0 SVN on win32, however the track does get submitted when an additional song plays. Maybe have amarok submit the last.fm queue when a track plays or once when the playlist finishes? the way the submissions are designed right now is that a track is submitted when the next track starts p laying. i wouldn't say this is a bug, as it is a completely valid way of doing it. no data is lost, and the track is still submitted. so i'm gonna close. that said, post-2.0 one of the things i want to do is rework the scrobbling system to fix a few inconsistencies---and this is one of them. *** Bug 183518 has been marked as a duplicate of this bug. *** My experience with last.fm submission does not allow me to agree with the closure of this bug by Leo Franchi, so I ask for its reopening (by the way, I'm the author of the duplicate report mentioned above). If you close Amarok or wait for too long before playing the next track the last track is never scrobbled (I do not know whether Amarok won't send the track end signal to last.fm or last.fm won't accept the signal after a period of time). So, there is data loss. There is a workaround to this bug, namely pressing the stop button just after the last track finishes - that might help in elucidating the nature of the problem. |