Hello.

Sorry for asking help about 1.4 version, but I have issues with my USB soundcard and Phonon, so I can't use 2.0 fully yet.

The problem in 1.4 is that I can't update collection (having about 16000 tracks) - if I click Tools -> Update Collection, nothing happens. I actually managed to update collection a week ago - suddenly it started working and did the update ~8 hours (on 64bit 2.4 GHz Athlon), but it hasn't worked since then. Rescanning seems to work though, but it takes way too much time (a day or so) to do it for every little change.

I had the problem on my previous machine (OpenSuse 11.0) and after changing machine with complete reinstall (to OpenSuse 11.1) I still experience it. As I use KDE 4.1, I launch Amarok with: export PATH="/opt/kde3/bin:$PATH" ; /opt/kde3/bin/amarok %U

Any ideas?

About rescanning. I kept an eye on collection_scan.log (is it really supposed to be overwritten with every track scan?) and I saw that the last track was rescanned while Amarok was on about 20% of the whole process. Since then amarokapp process (there's no amarokcollectionscanner process no more) just keeps doing smth (taking more or less 50% of CPU) with collection.db (it keeps getting modified, although Amarok ain't doing nothing but rescan). Currently the rescan has taken 70 minutes and it's on 32%.

atrox wrote:Hello.

Sorry for asking help about 1.4 version, but I have issues with my USB soundcard and Phonon, so I can't use 2.0 fully yet.

The problem in 1.4 is that I can't update collection (having about 16000 tracks) - if I click Tools -> Update Collection, nothing happens. I actually managed to update collection a week ago - suddenly it started working and did the update ~8 hours (on 64bit 2.4 GHz Athlon), but it hasn't worked since then. Rescanning seems to work though, but it takes way too much time (a day or so) to do it for every little change.

I had the problem on my previous machine (OpenSuse 11.0) and after changing machine with complete reinstall (to OpenSuse 11.1) I still experience it. As I use KDE 4.1, I launch Amarok with: export PATH="/opt/kde3/bin:$PATH" ; /opt/kde3/bin/amarok %U

Any ideas?

Amarok uses the directory mtime to detect collection changes. So this has a few consequences:

1) Only works with filesystems that support mtime (pretty much everything except FAT32 and maybe NFS/SMB)

2) To get a directory updated, try "touching" it (UNIX command). Example: "touch $HOME/Music/Nirvana_Nevermind". Then click "Update Collection".

1) My filesystem has always been XFS on /home, so I guess it's not an issue.

2) The update didn't occur not after renaming foldres nor after downloading several new directories during the week (I'm sure their mtimes are newer than was the last collection update).

But can you also comment on what is Amarok doing after scanning all files with collectionscanner?

BTW: status update on my rescan: has moved from 32% to 45% during the last 40 minutes.

No, I can't help you any more than that.

Also, Amarok 1.x is no longer maintained, and I haven't used it in about 2 years. So I cannot give advice about it very well.