I posed this question on the Amarok development mailing list and got this response from Mark Kretschmann, a lead developer of Amarok. Basically, Amarok isn't meant to be used for huge playlists like this, so he recommends not doing it :)
Therefore, I'm closing the bug. If you're looking for a player to manipulate a huge playlist, then you should be using a player more like XMMS. I think you're trying to fit a square a peg into a round hole! Thanks for the report. On 4/27/07, Mark Kretschmann <[EMAIL PROTECTED]> wrote: > On Friday 27 April 2007, Andrew Ash wrote: > > A ubuntu user [1] is having problems with Amarok taking a long time > > (60sec) to startup when having a rather large playlist already open > > (~4400 files). The user found that decreasing the playlist size > > directly corresponds with the time taken on startup. I was wondering > > if there was any work being done to optimize Amarok in this respect > > recently. > > Well yes. Basically, don't do this. Amarok was never meant to be used this > way. Use smaller playlists and the rich features of the collection interface. > > Do we plan to improve Amarok's performance with giant playlists? Not really. > In fact Amarok2 is being designed in such a way as to discourage this misuse > right from the start. The playlist will occupy muss less screen space and > should work best with less than 100 tracks. > > Not to sound like a total asshole, I'll explain the reasoning behind this > move ;) Amarok1 has its roots in a XMMS like design: There is no collection, > but instead the user loads the whole collection into one playlist. Later on > we've added the collection, which quickly became Amarok's center. Still, the > GUI layout of Amarok1 (huge playlist area) suggests that it works like a XMMS > class player, which it is really not meant to be. So we're going to correct > this in Amarok2. The player is no longer playlist centered, but rather > information centered. The playlist is just one tool for organizing your > music. > > -- > Mark ** Changed in: amarok (Ubuntu) Assignee: Andrew Ash => (unassigned) Status: Needs Info => Rejected -- amarok uses 100% CPU for 60sec at startup in gnome https://bugs.launchpad.net/bugs/108573 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for amarok in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs