Version: 1.4.2 (using KDE KDE 3.5.4) Installed from: Gentoo Packages Compiler: gcc 4.1.1 OS: Linux I often use the "Stop Playing After Track" feature when I'm about to leave my keyboard for a while. When I return, I want to continue playing, but it starts the last played track again. I'd expect to pick the next song instead of the last one I played before I left. This is bothering me for some releases already (at least 1.4.0, but it may be earlier). I'm primarily using the random track mode, if that's of any use.
hmm. with latest svn 'stop after current track' marks next track as the active, not the one just played. i think this behaviour has been changed somewhere before at least 1.4.2 - are you sure that is the final 1.4.2 build ? anybody else can reproduce this with 1.4.2 ?
Yes, I'm really sure that I'm running 1.4.2 right now.
i agree entirely, its annoying. Unfortunately it requires quite a bit of tweaking to get better/right, because of the original design of playlist code.
ok, to clarify - this is with 'random' mode, not dynamic playlist 'random mix' or any other dynamic playlist ;)
Resently (can't give the exact rev) there is a different issue with stop playing after track. It advances two tracks. In fact it stops and the next is marked active (which would be the desired state) and after ~1sec. it advances again, and one track is not played at all when resuming playback. When i stop manually it doesn't advance the current track marker (bubble thingy) at all. So in this case the last track is played again. i'm currently using revision 589003.
I just realize this skip seems to be gone if i disable crossfading - so i think it has the same reason as http://bugs.kde.org/show_bug.cgi?id=135511
This seems to be related to bugfix of #127312. See http://websvn.kde.org/trunk/extragear/multimedia/amarok/src/playlist.cpp?rev=544148&r1=542672&r2=544148 for details. It makes amarok not deselect current item after 'stop after current track' while in random mode. Applying reverse patch fixed this for me.
In amaroK 1.4.4 I don't see this problem. But I wonder if it is a hack which accomplishes this and you want to do it the right way at a later stage. So feel free to close this bug if there are no plans to work further on it.
well with rev600764 i still got the advance of two tracks if using crossfading and stop playing after this track. I don't think 1.4.4 is newer but i'll try to test this with a current svn tomorrow.
Still see this problem in amarok 1.4.4. Track selected to stop after in random mode is played again after stop.
It seems to work ok in svn version
In amarok-1.4.5 track is still played twice if play position was changed during playback.
I can confirm this; re-opening.
Created attachment 19863 [details] Returns old playlist behaviour ( before 1.4.1 ) Since this bug is very annoying for me, I've made a small patch that returns old playlist behavior ( to reset selection after "Stop after current tack" ). I've used it since amarok 1.4.1 ( and still using on amarok 1.4.5 ) and it works fine for me so I've decided to post it here. Perhaps someone else may find it useful.
This had been working for me, but now in 1.4.6 I am having this problem again. Now what I see is that after stopping, the "stop playing after track" marker stays on the selected track, and if I press start the selected track will play again. I also notice that no statistics are updated for the track (ie. it still says play count: 0 and score: 0) My expectation would be that after stopping, the "stop playing after track" marker would disappear, the track statistics would be updated, and the next track in the list would be selected so that when I press start the track will not be repeated.
*** Bug 139864 has been marked as a duplicate of this bug. ***
I can confirm this bug still exists in 1.4.8 on Fedora 8. - Stop playing icon doesn't disappear after song finishes - Pressing play replays the same song - Score is not updated after song finishes with stop playing selected
Setting this version to 2.0... It's not easily fixed with the playlist code in 1.4, unfortunatly. It should be easier to fix in 2.0, however.
I can also confirm this bug in 1.4.9.1
In Amarok 2 amarok just crashes, when stopping an the end of a track. I'll put debug infos later, when i have debug packages installed.
I can no longer reproduce this in Amarok 2. Closing.