Registered Member
|
I've been trying to put together play lists, and one thing that is really annoying me is that if you add tracks to the play list, Amarok will immediately start playing them if no track is currently playing.
And there seems to be no way to prevent this. Now, I could see this behavior be an option, just like you can set Amarok up to resume playback when you start the program, but in my world "Add to playlist" in no way automatically implies "...and start playing the added tracks". Indeed, if this was the case, then why won't it jump to playing the added tracks if playback is already started? |
Registered Member
|
+1
m0nk
If men could get pregnant, abortion would be a sacrament.
|
KDE CWG
|
This does not happen for me in GIT.
On the other hand, when I add new tracks to playlists already playing, Amarok *does* sometimes jump to the new tracks, even if I try to add them to the bottom of the list. |
Registered Member
|
This happens to me as well.
Man is the lowest-cost, 150-pound, nonlinear, all-purpose computer system which can be mass-produced by unskilled labor.
-NASA in 1965 |
Registered Member
|
With current git this will happen, if you add tracks through the (also annoying) pud.
m0nk
If men could get pregnant, abortion would be a sacrament.
|
Registered Member
|
After spending some time trying to figure this out, it appears that Amarok will start playing added tracks IF they were added with the context menu ("Add to playlist") AND no track is currently playing.
If added by clicking and dragging from the browser to the play list, they do NOT start playing, even if no track is currently playing. Makes for a confusing user experience, and explains why different people report different behavior. |
Registered users: Bing [Bot], Evergrowing, Google [Bot], Sogou [Bot]