Version: 2.2 (using KDE 4.3.2) OS: Linux Installed from: Gentoo Packages I have a very large playlist, about 7000 tracks. I use random playing by track. When I press "next track/previous track/pause/stop" amarok is freezing for 1 - 10 seconds. I think this is the bug. Other players switches immediately
Why are you using such a giant playlist? Please consider using a Dynamic Playlist for this task, which can do exactly what you want, and much more. Also, it will be much faster.
I need exactly that giant playlist. I need not dynamic playlist. I have to use another player, in which no such bugs.
I hit this bug as well. Mark, I think it was inappropriate to close this bug as "WORKSFORME": the feature in question (large custom-sorted playlist) doesn't work for you either, you simply don't use the feature. I feel tuupic and I have a *VERY* reasonable desire: play my whole collection in a specific sorting set by me. The random jumble offered by Dynamic Playlist is useless to us. I would like to ask you to please reopen this bug report, and consider fixing this regression from Amarok 1.
*** Bug 213094 has been marked as a duplicate of this bug. ***
Reopening on user request, but this is a wish, so don't expect this to be solved any time soon.
I have found the site of the O(n) performance bug: Playlist::Model::metadataChanged( Meta::TrackPtr track ) { const int size = m_items.size(); for ( int i = 0; i < size; i++ ) { if ( m_items.at( i )->track() == track ) { [snip] break; } } } Crudely disabling this function fixes the problem.
Note: I've developed a proper fix for this bug, which refactors the PlaylistModel data structure. It also attacks a number of other issues in the ModelStack that I encountered working on this bug. A few other demands on my time have come up that hold me from tidying up and submitting the patch. However, contact me before working on this bug.
(In reply to comment #7) > Note: I've developed a proper fix for this bug, which refactors the > PlaylistModel data structure. It also attacks a number of other issues in the > ModelStack that I encountered working on this bug. > > A few other demands on my time have come up that hold me from tidying up and > submitting the patch. However, contact me before working on this bug. We are in string and feature freeze now anyway. Once you are ready, please submit your patch as a merge request to http://gitorious.org/amarok You can find more information here: http://techbase.kde.org/Getting_Started/Sources/KDE_git-tutorial
I would be very much interested in reviewing your work. If you have any questions or require assistance with ModelStack stuff don't hesitate to contact me here or in #amarok on irc.freenode.org as Teo`.
Any news on this?
The problems causing this have been fixed (by myself). Closing.