I used to see something like this (many SC versions ago - I'm running 7.1). I *think* it was caused when the SC rescan was long enough for another MIP scan to start before SC had finished; SC saw that MIP's data had changed, and started scanning again... (As far as I can tell, every scan when MIP is enabled acts like a full scan; at least, the MIP section of the scan always takes 30 minutes, whether it's full or new/changed.)
It went away when I set the MIP rescan interval (in SC's settings) to zero (i.e. never). Now I only run MIP rescans manually from the GUI (after ripping sessions), then close the GUI and reload the cache using the MIP server webiface. -- Brian -- Brian Ritchie ------------------------------------------------------------------------ Brian Ritchie's Profile: http://forums.slimdevices.com/member.php?userid=2319 View this thread: http://forums.slimdevices.com/showthread.php?t=51586 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
