Hello, I have a few thousand songs, and my collection has been building for two hours now and is at 25%. Amarok is using max 0.5% of cpu, and I hardly ever see the hard drive light come on. However, the progress bar is slowly inching forwards. Why is it being so lazy?

I too am experiencing this problem....

I'm using mySQL with 1.4.9.1 on Ubuntu 8.04

Any ideas?

Hi all,

I have exactly the same issue since I upgraded Amarok to 1.4.9.1. I'm using the official packages of Debian Testing. Does anyone have any hints on what's going on?

This may or may not be an issue, but if you guys are using databases on separate servers over wi-fi connections that might be the problem.  I have about 8k songs and (see my other thread that I bumped here: http://amarok.kde.org/forum/index.php/topic,14813.0.html ) when I was trying to rebuild it from scratch over wifi it would take an eternity.  Like, 2 hours to get to about 20%.  Plugged 'er in to plain 'ol ethernet and it went along like normal.  No CPU usage worth mentioning while trying to do it over wi-fi, either, but over wired it uses a steady 20-30% of my laptop's 1.6ghz/800fsb c2d.  I have B wireless here but I can't believe bandwidth was the problem...the server is plenty fast enough for this application, too.

I could be totally off my rocker, too, because what are the chances that all you guys are on wifi LANs and are running mysql on separate boxes?

Remote scans are going to be quite slow. I suspect it's the issue with the other two. For some MP3s and other types, taglib has to read the whole file to find the data.

My problem was present with a local collection, so remote shares were not the source of it. Anyway, it disappeared yesterday after a package upgrade: now amarok has returned to be as responsive as usual. I am not completely sure, but I think that it was solved by an upgrade of the sqlite shared library.

So, I0m thinking that it was not an amarok problem, but a distribution issue.