Version: 2.0.2 (using 4.2.1 (KDE 4.2.1), Kubuntu packages) Compiler: cc OS: Linux (x86_64) release 2.6.28-11-generic Having upgraded from a standard Amarok 1 installation using an sqlite database, my collection and playlist completely mis up the metadata for songs. The title is displayed correctly, but everything else seems to be grabbed arbitrarily from other items in the collection. A screenshot of the metadata editing dialog summarizes the problem by showing both the filename and the metadata, which clearly do not match the filename.
Created attachment 32470 [details] Illustrative Screenshot
This report is a dupe, sorry (meaning, it has been reported before), and should be fixed in SVN.
(In reply to comment #2) > This report is a dupe, sorry (meaning, it has been reported before), and should > be fixed in SVN. What release will it be fixed for, and what svn revision has it been fixed in?
This is definitely NOT resolved in Amarok 2.1.1 in OpenSUSE 11.1 using KDE 4.3 final. The worst thing about it is that amarok still gets it wrong, when opening the metadata editor. It then shows e.g. completely wrong artist names. Editing the files then does not work and it seems amarok metadata handling is completely messed up. Even after rescanning the collection.
Jens and Simon, read correctly, please, when Mark says it is fixed in SVN that means in the developer version. This is fixed in 2.2-git since quite some time already, indeed.
Well, I did read that. The thing I did not understand is that it was reported for amarok 2.0.2 and it was fixed in svn on March 30 and amarok 2.1.1 was released on June 17. So I wanted to make sure it's going to disappear in the next release. To me that bug is a major PITA because it screwed up my current playlist which cannot be saved in amarok 2. So I'll have to manually go through the collection and readd the files. So IMHO of a non-developer this bugfix would justify a maintenance release by itself because like this metadata handling is severely broken.
It definitely was fixed in 2.1.1, just remove your database located in ~/.kde/share/apps/amarok/mysqle/ and rescan the collection. That has so far worked for everybody as it is due to a corrupted database. The tag editor problem is a completely different issue, fixed also in 2.2-git. For any further discussion, please join us in #amarok on irc.freenode.net or on our mailing list amarok@kde.org