First off, some specs
amarok - 1.4.3-r1
database - mysql 4.1.21
gcc - 4.1
distro - gentoo
kde - kde 3.5

Now on to the problems

Amarok starts up and configures great. I took the neccessary steps with mysql, created the database etc. The trouble is, when I try to build my collection, it gets to 66%, then tells me it cannot process a file and stops building the collection.  I know its not the file because after removing the indicated file from my music directory, it gives me the same error message on another file at 66%, and quits the same way.  First it was a wma file, then a jpg, then an mp3.

Suspecting a problem with mysql, I switched database types to sqlite, to no avail.  My music is comprised of various formats ranging, some of these are wma, mp3, mp4, and ogg.  is mounted on a FAT32 partition mounted over SAMBA, I can play music just fine off it, all the permissions appear to be fine.  Amarok itself has no issues playing files off it, it just doesn't like to add them to my collection.

Suspecting a problem with the amount of files i was adding (some 10 gig worth), I tried adding a smaller amount of music.  This completes to 100%, but the collection box doesn't update for several minutes(say 10 or 15), and only partially.

At this point, suspecting trouble with the network share, i attempted to build a collection of only local files.  This worked great, the collection built and updated almost immediately.  However I have no way of locally testing large amounts of media, so this doesn't really seem to help me with the processing error.  Again, my network permissions *should* be fine..

Any thoughts?

http://amarok.kde.org/wiki/Samba

Oh my.  I thought i had rtfm, but apparently i missed that part.  Well, that solved the problem of smaller collections not appearing, however when i try to add the entirety of my music(as opposed to a few folders), it still dies at 66%.  Much of my music(presumably that processed before the error) now appears in the collection box, so that's a step forward.

Am I really hitting a track limit, or is something wrong here?

*EDIT*
As an afterthought...I've been assuming the progress bar during collection building indicates how far the scan has progressed... however, it has occurred to me that perhaps it it the total process of building a collection? i.e. at 66%, it has finished scanning, and the error message i receive is just a notification of a failed track?  However, if that were the case, why would removal of said track simply result in another track taking it's place?

newbness sucks.