Version: 1.4.5 (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux When I am skipping tracks in a playlist Amarok is very slow. It takes about 1 or 2 seconds between each track. Information on Amarok setup: Amarok version: 1.4.5 Playlist size: 150 tracks, ~10 hours. Database backend for collection: PostgreSQL PostgreSQL version: 8.1.8 Songs in collection: 13708 Repeat: Playlist Random: Off I have made a script to test how long it takes to skip tracks. The script is this: (tdn@homer.) (Fri Mar 09 07:23 ) {P:0 H:1484} (~) cat bin/amarok-next-tracks.sh #!/bin/bash for i in `seq 1 $1`; do echo "[`date`] Skipping track $i" DISPLAY=:0 dcop amarok player next done Here is the output of the script skipping 10 songs: (tdn@homer.) (Fri Mar 09 07:23 ) {P:0 H:1485} (~) time bin/amarok-next-tracks.sh 10 [Fri Mar 9 19:23:22 CET 2007] Skipping track 1 [Fri Mar 9 19:23:23 CET 2007] Skipping track 2 [Fri Mar 9 19:23:25 CET 2007] Skipping track 3 [Fri Mar 9 19:23:27 CET 2007] Skipping track 4 [Fri Mar 9 19:23:29 CET 2007] Skipping track 5 [Fri Mar 9 19:23:30 CET 2007] Skipping track 6 [Fri Mar 9 19:23:32 CET 2007] Skipping track 7 [Fri Mar 9 19:23:33 CET 2007] Skipping track 8 [Fri Mar 9 19:23:34 CET 2007] Skipping track 9 [Fri Mar 9 19:23:36 CET 2007] Skipping track 10 real 0m20.845s user 0m0.484s sys 0m0.108s Here is some information my hardware: CPU: 1400MHz AMD Athlon Thunderbird RAM: 512MB Harddiscs: 7200 rpm IDE discs. Graphics: GeForce2 Pro I think that should be sufficient hardware for playing music.
I have tried watching amarokapp in top while skipping tracks. Amarok uses between 60% and 90% CPU while skipping tracks. This is a lot when it takes >50% CPU usage for about 20 seconds to skip 10 songs.
A few people on IRC have asked me if I use moodbar. I do *not* use moodbar. This is a default installation of amarok except that I have set up my collection and I use postgresql. I have even tried it on a completely fresh install of Kubuntu Feisty Fawn Herd 5. Same problem.
No idea what's going on, sorry. If your amarok is compiled with debug, you could start it from the shell and look at the debug output (there will be heaps). Amarok also prints some interesting timing data. (Build with debug: --enable-debug=full)
*** This bug has been confirmed by popular vote. ***
I also have this exact problem. It's one of the reasons I still use xmms, even though I would like to change.
Mark Kretschmann: I have just fetched the source, compiled it with --enable-debug=full. I started the "amarok" binary from the console. Nothing is printed in the console when skipping tracks. Should I use a special debug flag when running amarok? I don't see anything on this in amarok --help. I also did another test with the version I compiled from source: (tdn@homer.) (Mon Mar 19 07:36 ) {P:0 H:230} (~) time bin/amarok-next-tracks.sh 10 [Mon Mar 19 19:44:49 CET 2007] Skipping track 1 Wes - Awa awa [Mon Mar 19 19:44:52 CET 2007] Skipping track 2 Wes - Alane [Mon Mar 19 19:44:54 CET 2007] Skipping track 3 Wes - Kekana [Mon Mar 19 19:44:56 CET 2007] Skipping track 4 Wes - Wezale [Mon Mar 19 19:44:58 CET 2007] Skipping track 5 Wes - Ken mouka [Mon Mar 19 19:45:00 CET 2007] Skipping track 6 Wes - Mawaza [Mon Mar 19 19:45:02 CET 2007] Skipping track 7 Wes - Mindoulou [Mon Mar 19 19:45:04 CET 2007] Skipping track 8 Wes - Mizobiya [Mon Mar 19 19:45:06 CET 2007] Skipping track 9 Wes - Degue wegue [Mon Mar 19 19:45:08 CET 2007] Skipping track 10 Wes - Ramende real 0m21.398s user 0m0.608s sys 0m0.308s (tdn@homer.) (Mon Mar 19 07:45 ) {P:0 H:230} (~)
Please note that you need to install Amarok to actually run it. Without installing, you've probably been running your old binary.
Mark: Hehe. If course I have been running my newly compiled binary ;) I compiled and installed it to /opt/amarok and ran /opt/amarok/bin/amarok in the console.
Created attachment 20042 [details] STDERR from /opt/amarok/bin/amarokapp I figured that I needed to run the binary "amarokapp" in stead of "amarok". Here is a log with the debug output made when skipping ten songs. I have edited the filenames in the log.
Are your files on the local disk or being streamed from a server?
Seb Ruiz: My files are read from a local disk. The disk is a Seagate 250GB ATA disk with 8mb cache spinning at 7200rpm. My file system is ext3 with journal. I doubt that the file system nor the disk is the bottleneck here. Also I have tried this on several systems with very different hardware. The problem is on all the systems. The last system I tried it on was a new Intel Core 2 Duo system with lots of RAM and fast disks. Also it was the most recent version of Amarok.
What type of files are you playing? Did you rip them yourself (if so, how?). Does the same problem occur if you use a different xinelib application, such xine-ui or kaffeine ? On 4 Jul 2007 20:52:03 -0000, Thomas Damgaard <thomasdn@gmail.com> wrote: [bugs.kde.org quoted mail]
closing due to lack of feedback
What feedback do you need? Please do not close this bug yet.
Seb, could you please add a reason to why this bug has been marked invalid? Med venlig hilsen/Kind regards Thomas Damgaard Nielsen http://thomasdamgaard.dk On Thu, Jul 3, 2008 at 12:53 PM, Seb Ruiz <ruiz@kde.org> wrote: [bugs.kde.org quoted mail]
A number of reasons: a) Amarok 1.4 is not longer in production, we aren't making any changes there b) This bug is most likely invalid in Amarok2 using Phonon and KDE4 c) I last asked for feedback on 2007-07-05 and had not received any response You should try update to Amarok 1.4.9.1 and latest xine, but if you are still having problems after that then I'm afraid there isn't much we can do for you.