[jeffparnau]

I have not read pages 2 & 3 of this thread, but I thought I would pass along something that stumped me. I would import, say, 13 MP3G pieces, and only 9 would show up in a search, yet they existed in the database. I fixed it by doing this:

I downloaded a free MP3 Tag editor called Mp3Tag. I unzipped any MP3-CDG zip files, and opened the MP3s. I found that on the problem files, Hoster would use the Title tag in building its KMH cross reference, and that would also show up in the resulting database. Because the title is what Hoster searches for, it never found these files. Typically this happened when there was SOMETHING in the mp3 tag title like this: TRACK 5 or like this: tSinger.

With an MP3 tag editor, you can type in the real name and artist, and it will then show up in searches after you rebuild your database. (Pretty easy for 100 files, but obviously this will get tedious if you have to fix 3000 of them. Whatcha gonna do, hey?) I suggest you kill the associated kmh files, just to be sure Hoster doesn't ignore it, thinking it was already correct.

This did not seem to occur when the files had no mp3 tag Title at all. So you may be having the same problem. I was surprised to see that about 20 percent of my existing library had problems like this.

It's easy to check if you get an mp3 tag editor, or simply turn on the "Title" field in Windows explorer. I strongly suspect you will see discrepancies in the mp3 title field. I also suspect this is the result of files having a "questionable history" of legality. I purchase most new music from apparently legitimate websites, but many of the files I get have this peculiar problem.