title says it all. Amarok used to be crash-proof for playlists, but somewhere along the line that functionality disappeared. also, the fadeout option on Amarok close also seems to have gone AWOL. could anyone provide an explanation as to the fate of these two great features?

hish wrote:Amarok used to be crash-proof for playlists, but somewhere along the line that functionality disappeared.

The playlist has never been crash resistant. I've made several attempts to implement this, but it proved to be exceedingly difficult to do without performance penalties (which was my goal). Also, Amarok is getting increasingly stable (it's hard to crash it these days), so for me this feature does not have a high priority.

hish wrote:also, the fadeout option on Amarok close also seems to have gone AWOL. could anyone provide an explanation as to the fate of these two great features?

It's still there if you enable crossfading.

no, Amarok doesn't crash too often these days, but it does still happen - it would be nice if there was an option to auto-save a copy of the playlist at a configurable interval. surely that wouldn't come at too great a performance cost?
as for crossfading, Amarok used to fade on close regardless of whether or not you had fade enabled - I don't use crossfading for regular music listening, but it's a nice effect to have when I close the program.
I've been really happy with Amarok, it's by far the best audio player I've used, but reimplementing these features would make it that marginal amount -better-.

-bump- auto-save playlists? fadeout on exit? no-one else thinks these are things worth implementing? I have a somewhat unstable X configuration, so my setup ditches me periodically, it would be a great thing for Amarok to return to even a shadow of its former crash-resistant glory.

As Markey said, the various attempts at auto-save playlists have come at quite a significant cost to performance... Have you had a look through past SVN commits to have a look for yourself? Perhaps you might be able to come up with an answer as to why the implementations attempted didn't work as desired.

I'm assuming you consider fade on exit a secondary feature? Something that's nice, but not absolutely required? After all, since it's X that crashes on you, you'd rarely get to *hear* that fade on exit

You'd probably consider this a copout reply, but the devs really are working hard on stability - your requests might find their way into amarok 2.0 with refactoring of a lot of the way amarok achieves its functions.

sorry, i don't mean to take a demanding tone - I fully appreciate the effort you guys are put in to making Amarok the best audio player for Linux. it was something I recalled older versions doing and wondered about a return of. from a non coder perspective, it seems a relatively simple task to autosave the playlist to a config file - if Amarok is already sending a notification to last.fm on every track change, why not to an on-disk file as well?
I wish I could implement something using coding skills of my own, but alas, I possess none.

I also miss the fadeout on exit. I would use crossfading on manual track change, but what it goes from a manually selected track to another random one, there's a gap and the last half second of songs get cut off.

Mark Kretschmann wrote:

hish wrote:Amarok used to be crash-proof for playlists, but somewhere along the line that functionality disappeared.

The playlist has never been crash resistant. I've made several attempts to implement this, but it proved to be exceedingly difficult to do without performance penalties (which was my goal). Also, Amarok is getting increasingly stable (it's hard to crash it these days), so for me this feature does not have a high priority.

Sorry for reviving a topic from 3 years ago, but it seems nothing changed from that time.

The new Amarok 2 crashes for me from time to time, also sometimes there are X or system crashes (or there are power cuts). It would be really nice if Amarok remembered the playlist even if not closed properly. If the performance was issue 3 years ago, it shouldn't be nowadays (well, it could be an option so it could be turned off on the older computers).

senjin wrote:
Sorry for reviving a topic from 3 years ago, but it seems nothing changed from that time.
...

Please open another thread, this one was about Amarok 1.x, and Amarok 2 is is a whole new codebase. Not a good idea to mix two different version, where crash reasons can be extremly different.

The crash reasons are completely unimportant, because Amarok can be crashed as a result of the system or X server crash or power cuts. These crashes cannot be prevented by yourself, but you can deal with them. The problem are not crashes, but the loss of playlist.

senjin wrote:The crash reasons are completely unimportant, because Amarok can be crashed as a result of the system or X server crash or power cuts. These crashes cannot be prevented by yourself, but you can deal with them. The problem are not crashes, but the loss of playlist.

Regardless, please do open a new thread, this is not about Amarok 2 here!!!