Version: 2.1.1 (using KDE 4.2.90) Installed from: SuSE RPMs Amarok isn't case sensitive. I had some folders and filenames which where exactly the same, but some letters were big or small. Example: ~/music/COR/ ~/music/Cor/ Amarok just scans one of these two folders. So you can't find the files in the secons folder in the collection. If you add the songs with drag & drop, amarok doesn't scan the tags too. If you have two files like this: SONG.mp3 song.mp3 Amarok is scanning just one too.
This seems very strange to me, can somebody confirm this?
Confirm it on Amarok 2.1.1 I think it's related for bug with DB not the scan.
*** This bug has been marked as a duplicate of bug 189527 ***
Alexey: no, please, do not set duplicates if you don't see the difference :( This is not the same bug AT ALL!
Confirmed
Possibly a MySQL thing. Googling for "mysql case sensitive" returns tons of pages.
Collation in the DB is indeed case-insensitive. This actually only matters when you use strings for primary/unique keys -- which we do :-| If we want to try changing this I could trawl out another DB update that changes the collation to something case-sensitive...not sure how that might affect various operations though. Maybe it'll just make things happy. :-)
*** Bug 203243 has been marked as a duplicate of this bug. ***
Any news on this, Jeff?
No, it got lost in the ether. I'll look into it again when I have time.
Looked into this a bit...something weird going on which isn't related to the collection scanning, and AFAICT isn't related to the database either, but rather somewhere in between. Also interesting: while file case-insensitivity seems to be a problem from the outset (i.e. full scan), folder case-sensitivity seems to be a problem only after an incremental scan. They'll appear on first (full) scan, but when you next open up Amarok they won't. The reason for the incremental scanning issue is that the two different paths aren't being saved into the database. This should hopefully be easy to fix. Not sure about the files, yet. Please be patient -- this is on high/top priority for my bugfixes before 2.2 but I'm super busy right now.
Fixed in git commit bc00b898a72a0f5d9b6ae10f723502efc9b638c2.