Bug 131593 - Song change in last.fm stream not always detected correctly
Summary: Song change in last.fm stream not always detected correctly
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-31 16:43 UTC by Arend van Beelen jr.
Modified: 2006-08-24 09:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arend van Beelen jr. 2006-07-31 16:43:05 UTC
Version:           1.4.2-beta1 (using KDE KDE 3.5.2)
Installed from:    SuSE RPMs

When playing a stream from last.fm (Neightbor Radio in this case), it sometimes happens that when the song changes, Amarok still believes the old song is playing. You then see the progress bar has reached the end of the song, and the meta data of the previous song is still shown. The new song can already be heard and also shows up in the last.fm history, but not in Amarok's "Metadata History" of the stream. Usually the next song change after that is detected correctly again and Amarok gets back in sync with the stream. I've also seen it happen when I stopped a stream and reconnected, Amarok still thought it was streaming the previous song even though the stream had started a new one.
Comment 1 Mark Kretschmann 2006-07-31 16:52:20 UTC
Yep, this is a known problem. The source of evil is QHttp, which sometimes forgets to emit a signal. I've not been able to figure out why.
Comment 2 Mark Kretschmann 2006-08-24 09:05:27 UTC
Fixed in 1.4.2.