There are some strange behaviors in amaroks database.

1. the database is shrinking if I update the collection. I don't know which files are disappearing but I can see it on the counter in the collection-browser. Just a global rescan of the collection works fine and amarok says that I have abaout 13,100 songs. If I update the collection I will have about 12,800 or even less.

2. Sometimes the songs have strange tags. I inserted the songs of the album Sandinista! from the Clash to my database and rescanned it. Now nearly every song of the Clashs album "From Here To Eternaty" is now tagged as a song from Sandinista! Just the first song is correct. Only the database shows this wrong stuff. The files didn't changed.

EDIT: I'm using Amarok 2.1.85 at the moment.

Now I found two albums which will be deleted from the database if I update it.

The songs are tagged with id3v1 and have filenames like "01 Song One.mp3".

The console also tells me this if I update:

TagLib: MPEG::Header::parse() -- Invalid sample rate.

EDIT: Amarok has problems with id3v1 Tags. I converted some files with
id3v2 -C filename.mp and updated the database. After a restart of amarok the files where still in the database but the year-tag wasn't correct. So I updated the year-tags in amarok and rescanned the database again. The files were in the database again. I checked them with id3v2 -l filename.mp3 and the tags were id3v1 again. This shouldn't happen.

This should be solved now with the commits made yesterday.

Ok, I will test it again when there is a new package from the Suse-team.