Version: 1.90 (using KDE 4.1.1) OS: Linux Installed from: Ubuntu Packages I have a few large compilations (between 500 and 900 tracks each). When amarok scans my collection it creates one album per track for these compilation, instead of one. It detects smaller compilations (20-30 tracks) correctly. It works well with all size compilations in amarok 1. After reading a bit the code, it seems to come from the ScanResultProcessor.cpp file, processDirectory function : //using the following heuristics: //if more than one album is in the dir, use the artist of each track as albumartist //if more than 60 files are in the dir, use the artist of each track as albumartist //if all tracks have the same artist, use it as albumartist //try to find the albumartist A: tracks must have the artist A or A feat. B (and variants) //if no albumartist could be found, it's a compilation The problem may come from this 60 limit. Why 60 ? Could it be a higher number (maybe 1000) ? or this constraint could disappear ? or become customizable ?
I can confirm that this also happens with one collection we have, "100 MTV Number one Hits" or somesuch. And it is _very_ annoying.
I should add that I was referring to Ampache. Dunno if that makes a difference.
*** This bug has been marked as a duplicate of bug 172953 ***