Hi everyone,
First i'd like to say that both amarok 1.x and 2.x are the best audio players ever released for linux and i really appreciate great amount of work&time that developers put into this project, but...

...for ****'S SAKE since v2.0 beta/alpha/whatever through stable versions to nightly 2.2 not even once was my collection built correctly. How the hell could you released 2.0/1/2 versions without such an important and essential to Amarok feature? Always albums, tracks and bands are mixed creating complete mess. And even if i manage to soirt it out a little by myself - god forbid updating the collection! Everything's messed up again or all songs are doubled.

I hope that someone's gonna read it.

Please get the 2.2.1 version of Amarok form the kubuntu backports PPA as described here:
http://www.kubuntu.org/news/amarok-2.2.1

Once you have it installed, do a full rescan of your collection on first startup, the restart Amarok. That should really fix the problems you describe.

FWIW, we did release Amarok 2.0.x as a preview and clearly stated that it was not meant to be fit for an everyday use, please read here: http://amarok.kde.org/de/node/595
This is definitely different with the 2.2 series.

What I do is to check that all the tags are correctly, with easytag or some external program, then remove the database:

Code: Select all

rm -rf .kde/share/apps/amarok/mysqle

And rescan the collection, also I have noticed that, for me, it is better to disable 'watch folders changes' option...

I am using amarok 2.2.1 and i tried removing database several times. Tags are correct cause 1.4 builds collection perfectly.

P4C0 wrote:What I do is to check that all the tags are correctly, with easytag or some external program, then remove the database:

Code: Select all

rm -rf .kde/share/apps/amarok/mysqle

And rescan the collection, also I have noticed that, for me, it is better to disable 'watch folders changes' option...

With the side effect that you will lose all the ratings and statistics. It would be more logical to do a full rescan (provided you have version 2.2.1 of Amarok), then restart Amarok.