Jamcast

Hi Steve,

Sorry to hear you ran into troubles with this. Hopefully I can be of some assistance to you.

The realtime library synchronization feature is designed to auto-detect changes to your media library as they are made, thereby eliminating the need to rescan your entire library every time you make a change to it. Jamcast receives notifications at both the file and folder level any time there is a add, update, or delete to files within folder's you've shared to Jamcast. It's worth noting that these notifications are not available from network drives.

If you take a look at the importlog.txt (located in the Jamcast installation folder), you'll see logging related to individual files and folders as changes are detected. If you'd like to post your logfile to http://pastebin.org and share it here, I'd be happy to take a look at it for you. It seems strange that miscellaneous updates to your media collection here and there would trigger a 10 minute scan (and that much CPU usage), but I've seen cases where antivirus or backup software in the background triggering these notifications. But to be clear, Jamcast will not take any action on its own without Windows first notifying the server of a change.

If I've misunderstood and this 10 minute scan is occurring only when you start the Jamcast service, this is expected. Jamcast will rescan all of your shared folders at startup, but this process is highly optimized in the sense that all of the heavy lifting is done only on media that hasn't been previously imported, and has not changed (according the modified timestamp on the file) since the last scan. However, the high CPU utilization is not expected.

Hope this helps. Let me know what else you're finding on your end. I'm also curious as to what type of CPU you've got -- when I do a full scan against an empty database, my CPU is never up over 10% or so. It's the disk(s) that are taxed the most by the scanning process.

Thanks!