Registered Member
|
Hi,
My amarok in arch linux is slow to startup. I saw a suggestion to run amarok like "amarok --debug --nofork" and look for DELAY. I saw these.
I then disabled all the scripts but the remaining values remains unchanged and is still slow. Is there any way to speed up startup ???
jithin1987, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
What version of KDE SC are you using? Have you installed the normal version or the KDE-mod version of amarok?
Have you tried reinstalling amarok?
Autostart in the advanced tab of System Settings lets you start a program automaticly when you boot but I don't think that would be smart in your case. |
Registered Member
|
I am using normal version of kde. I was using kdemod few days back and then switched to normal one.
Both had same speed. I did reinstall amarok. I have 3025 tracks in my collection. Could that be an issue. The KDE SC I am using is 4.4 rc2 from kde-unstable. I am updating to 4.4 rc3 atm. Will report back if any improvements. The speed was same when I using the stable 4.3.4.
jithin1987, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
Possibly, but Amarok should be able to handle much larger collections. I'm not sure my collection is much smaller at the moment (darn HD crash!) |
Registered Member
|
I've noticed this as well. Amarok is really slow starting up, at least compared to any other application I've used, including other media players like Banshee or even Songbird. I'm using Amarok 2.2.2 and KDE 4.3.5.
|
KDE Developer
|
Well, looking at this...
...it does actually seem that a script is causing the delay. Are you really sure that none of them are running? Try to remove your Amarok config entirely once (after making a backup!):
--
Mark Kretschmann - Amarok Developer |
Registered Member
|
I'm using Amarok 2.2.90 / KDE 4.4.0 and my startup time is 2 minutes 11 seconds (!!), which is about 2 minutes 10 seconds longer than it should. Previous version wasn't this bad even though it definitely took over 10 seconds as well.
Does someone know if this is a known issue? I'm using Amarok with a rather large collection over local gigabit NFS share, so that could be one reason. However, if there's some scanning going on in background, I'd expect that it would not block the startup. Should I file a bug report about problems like this? |
KDE Developer
|
...and look for "DELAY".
--
Mark Kretschmann - Amarok Developer |
Registered Member
|
Indeed, sorry for not realizing there was already a tip for checking the delay in this thread.
It seemed that loading the existing playlists was taking a considerable amount of time, so I deleted all .m3u files. That dropped the startup time by almost a minute. Running with --debug --nofork now creates a respectable 3.7 megabyte log that includes the following delays:
Hope this helps! |
Registered Member
|
I'm glad to report that today the Amarok startup time was suddenly down to 8.6 seconds. I'm guessing there might have been something fishy going on because of the recent update to KDE 4.4.0 or similar; it may be that the delay was not Amarok's fault after all.
I'll try to investigate more closely if this happens again. And thanks for the good work with the player |
Registered users: Bing [Bot], Google [Bot]