When I have my entire music library in the playlist the GUI freezes after 4 seconds when you change tracks. It gets released after about 2-3 seconds. It's the first 4 seconds I'm referring to. Ex. (seconds) 0 , 1 , 2 , 3 , 4 - freeze - 6 , 7 , and so on You can change songs before 4 seconds has passed but will freeze regardless once 4 seconds has passed after changing tracks Reproducible: Always Steps to Reproduce: 1. Add 20k songs 2. Change song either manually or automatically 3. Actual Results: GUI freezes Expected Results: GUI not freezing This happens regardless of database backend. Embedded or external. In my setup I use Mariadb-10.0.27 and I have had the same results with using Mysql.
Created attachment 101544 [details] Debug output This is the output from starting amarok from the terminal. amarok --debug
no wonder, you are not meant to put your entire collection in the playlist, there have been many reports about this, this is not a bug but a normal side effect. Sorry if this is not how you intend to use it, but this is definitely a use case we do not cater for. Use the various playlist capacities of Amarok instead.
Sad to hear that this is the attitude when it's clearly a bug. If it were a "side effect" as you so put it all players would have it. If there's been many reports about it baffles me even more why there's no desire to fix it.
no, not all players handle playlists the same way as amarok does, the more tracks you put in the playlist, the more tracks have to be checked for availability on startup, and that can substantially slow down the startup procedure. Just don't put all your collection in the playlist, use the playlist generator, smart playlists or the collection filters instead.
And to be more precise: this is not "fixable" in the current architecture, it would need a complete rewrite.
I start with an emply playlist due to the fact you just mentioned. The startup is very slow. Around 20 seconds. My report is about the freezing of the GUI 4 seconds after you change tracks when you have a big list loaded and not about the startup.
(In reply to Marax Faraii from comment #6) > I start with an emply playlist due to the fact you just mentioned. The > startup is very slow. Around 20 seconds. > > My report is about the freezing of the GUI 4 seconds after you change tracks > when you have a big list loaded and not about the startup. Which Phonon backend? Where are those tracks located (local, remote)? Since you use Gentoo: did you try the current git master instead? it is about 500 commits ahead of Amarok 2.8.0, and I see no freezes on track change at all, might well be something already solved.
>Which Phonon backend? >Where are those tracks located (local, remote)? >Since you use Gentoo: did you try the current git master instead? it is about 500 commits ahead of >Amarok 2.8.0, and I see no freezes on track change at all, might well be something already solved. No, I haven't tested the git master. The GUI freeze isn't a deal breaker for me as I normally do use smaller playlists and it doesn't affect audio when it freezes. I reported as I thought it might be worth looking into. The collection is local. Amarok Diagnostics General Information: Amarok Version: 2.8.90 KDE Version: 4.14.24 Qt Version: 4.8.6 Phonon Version: 4.9.0 Phonon Backend: GStreamer (4.9.0) PulseAudio: Yes Enabled Scripts: Enabled Plugins: MySQL Collection (1.0) Enabled Applets: Current Track Lyrics