ive only been using amarok for a few hours and have one huge suggestion. add more threading to reduce UI lockups.

first, my configuration FreeBSD 6, KDE 3.5, amarok 1.8. im running on mysql mode, my files are on a file server in my house (almost 30,000) and i have those mounted to the local file system via a samba mount.

Now, in the collections screen, if i change the name of an artist for example i may have ozzy ozborne, ozzy osborne, and ozzy. i want them to all be under the correct name, ozzy osborne. well each one of those may have 40 or so files under them. it seems like if i change the artist for that group, it updates the database and then updates the ID3v2 tags on the file itself in one thread. well, in my situation, it could and has brought amarok to a standstill until it finishes updating the files. in my case, it took about 5 minutes to update the files because they were over the network during that time the UI was locked up, not refreshing and when the song that was playing finished, it didn\'t start the next one until the file operation was complete.

a solution for this is when you do mass updates like that, update the DB which will allow your UI to show the correct data, then start another thread, show it as one of your background processes to update the files. this will free the UI and make it much snappier to use.

sorry, thats amarok 1.3.8

actually, your problem is because of samba.

frankly, samba sucks - the cause of all problems. You should mount it as an NFS server instead.