Version: 1.4.7 (using KDE KDE 3.5.8) Installed from: Ubuntu Packages OS: Linux Amarok has an option titled "Resume playback on start". I would assume that this means that if I exit Amarok (or if it crashes) and then restart it, it would resume playing the same track, from the time position it was at before the closure/crash. If the track was paused, it should resume in a paused state. In Ubuntu (at least Feisty and Gutsy), it instead skips to the next track in the playlist, and starts playing from the beginning of that track.
Amarok now appears to be resuming the correct track on startup, but it does not honour the paused status. If I have a track paused when I close Amarok, it should resume as paused after starting Amarok again. Instead, it resumes playing the track from where I left off. This is especially annoying when I log into my computer, since I have Amarok saved as part of my session. I don't want to be listening to my podcasts as soon as I log in, especially when my system is already overloaded trying to load up KDE and my other apps. In such an overloaded state, listening to audio is going to be a choppy experience anyway.
I have never experienced choppy audio when restoring a session. We have also discussed restoring the "paused" status on application start and decided against it for various reasons.
> I have never experienced choppy audio when restoring a session. Just because you don't have a problem, that does not mean it doesn't happen to other people. Choppiness can be a factor of high system load, slow CPU, kernel version, and so on. When I log into KDE, I have lots of applications automatically load, including Amarok. This can take a minute or longer, and I (like many people) often go off and do something else while it's loading. If Amarok automatically starts, I'm usually not there to listen to it. After I get back to my computer, I have to manually rewind to find the spot where I left off. > We have also discussed restoring the "paused" status on application start > and decided against it for various reasons. The only reference to this I can find is Bug 113559, which seems to be asking to have the track be paused on startup regardless of whether it was playing or not the last time Amarok was closed. What I am asking for is different. I would like the play/pause status to be saved as part of the Amarok session and be honoured on Amarok startup: * if the track was playing when Amarok was last closed (or crashed), it should resume playing when Amarok starts again * if the track was paused when Amarok was last closed (or crashed), it should be paused when Amarok starts again The assumption with the current setup is that when Amarok is started, the user always wants to listen right away. This is often not the case. Many people keep Amarok open (but not playing) in the background, so that it's there when they want it. If you still wish to reject this request, please let us know why instead of just dismissing it. There are lots of people who would like this feature.
bug 150396 is what you are looking for. if you don't want music to start playing when you restore a session, exclude amarok from session restore and start it manually.
Sorry, but that bug has nothing to do with what I'm asking. That person was requesting that Amarok detect when it is being resumed from suspend/hibernation, which I understand can't be done at the moment. I am asking for Amarok to be able to honour the play/paused status of the track when it is executed. Amarok is far more than just a player these days. For one thing, it is a powerful music management application. It can fetch lyrics and artwork, connect to portable media devices, and even interact with Magnatune, just to name a few. One cannot assume that when Amarok is started the user wants to immediately listen to the songs that are currently in their playlist, since there are so many other things that it can do. Don't sell yourself short: Embrace the fact that Amarok is not just a player but an awesome music management suite.
Bug was closed due to a misinterpretation. Re-opening.
On 2007-11-05 03:06, I wrote: > Amarok now appears to be resuming the correct track on startup I'm not sure why, but the old behaviour has returned. When I load Amarok, it skips to the next track instead of resuming the current one.
This was indeed a problem in the 1.4.x release. Amarok 1.4.x is in bugfix-only mode as development is focused on Amarok 2. Unfortunately your bug will not be fixed in Amarok 1, as Amarok developers do not have the resources for it. I am therefore moving your request to Amarok 2. I cannot make any guarantee as to whether is will get implemented there or not though. Thank you for your report
If you don't want amarok to resume playback on startup then uncheck the little box that says "Resume playback on startup." That has been there forever. That is what the feature is. Resolving as invalid.
Please shelve the condescending language - it isn't helping the situation. I never said that I don't want playback to resume on startup. I said it would be more intuitive for the track to be either playing or paused depending on what state it was in when Amarok was last closed. The "Resume playback on startup" option means that if a track is playing when I close Amarok, it resumes when I next load Amarok. That's a good thing. But what happens if the track was paused when I close Amarok? The next time I start Amarok, the track is stopped. I have to press Play and listen to it from the beginning (or manually skip ahead and find where I think I was). Does this make sense? If the track was paused, I don't want to start from the beginning - I want to start from where it was paused. Since it was paused when I closed Amarok, it only makes sense for it to be resumed in the same paused state. This is a valid inconsistency in Amarok, as has been verified by at least one other person (comment #8).
To clarify even more... Assume I have "Resume playback on startup" turned on (which I do). A track can be in one of three states: * Stopped * Playing * Paused If I Stop a track and restart Amarok, the track is Stopped. If I Play a track and restart Amarok, the track resumes Playing. If I Pause a track and restart Amarok, the track is Stopped. In other words, Amarok's resume functionality is treating Pause as Stop. But Pause is not Stop - Pause is its own state. So if a track is Paused and I restart Amarok, it should resume as Paused.
Okay, there appears to have been a change in behaviour since I initially filed this bug report. Earlier on I said that Paused was treated as Play upon resume. Now it's treating Paused as Stopped. Regardless, I've never seen Amarok treat Paused as Paused.
> ------- Additional Comment #2 From Seb Ruiz 2007-11-05 03:25 ------- > We have also discussed restoring the "paused" status on application start > and decided against it for various reasons. Sridhar, As I mentioned over 12 months ago, the development core of Amarok have decided not to implement this feature. Whilst we value the feedback and requests from our users (I think we do a pretty good job of this), we can't be expected to accept every wish.