Initial Scan not picking up all shares

Hi,

Slightly odd this one and I'm not sure if this issue appeared with the scarletfire build or when I added a share on a different drive. I was already sharing across two drives, so either adding a third drive share has caused this or its the newest build (or perhaps when I exceeded 70k shares). Essentially the initial scan of shares does not pick up all the shares, but if I rescan after the first load then the remainder seem to get added. It's hard to figure out which files are not being loaded at first as it doesn't matter how many I count I can't get it to match exactly the amount that shows in rooms, but it doesn't seem to be all from one drive and missing the other drives - also the number loaded initally seems to vary. So i logged in today and it told me 56799 were loaded (in the room) and then I hit rescan immediately and it said another 13340 added (but I hadn't touched the shares or changed the shares in soulseek). This certainly wasn't happening two or three weeks ago. If I use the windows properties to count then I get a total of around 76000 files, but soulseek usually shows around 71000... I have always put this down to certain files being excluded or some de-duping going on perhaps, but it does make it hard to figure out what shares aren't being loaded. I can see the mp3 scanning still ticking away if i switch diagnostics on but I always figured this was a background task that continued after the client fired up so you didn't have to wait an ice age or two during start-up but the client would still know how many files were shared even if these weren't fully indexed.

Sorry I don't have anything more concrete to go on, but its a bugger to figure out what's going on cos I can't get the number to match up however I slice n dice them.

Squizz.