Rescanning Estimate

[simoncn]

There have been no changes to how rescan works since we last discussed this. It still rebuilds the cache and it still makes MinimServer unavailable in control points while the rescan is happening (perhaps 2 to 3 minutes for a moderately large library with a small number of changed files, or longer if running MinimServer on a slow device). It is also possible that the control point could lose its current position in the MinimServer browse tree when it rediscovers MinimServer after the rescan.

For all these reasons, it would not be a good idea for SongKong to automatically initiate a rescan after a single change. It is better for the user to complete a set of changes and manually initiate a rescan when the user has completed their changes and wants to see them in MinimServer.