>After I did the custom scan export, I switched to the headless Web UI >to resume validation. But there it reports around 2,000 more tracks >requiring validation compared to the MIP GUI. Wonder why? > Did you save the MIP GUI and then reload the cache in Headless web UI before the custom scan export, or any other activity in SC? eg. playing a song would pass a new playcount to MIP and therefore overwrite the cache?
>Another discrepancy is SC reports my total songs as one more than MIP, >but I'm not going to worry about a difference of 1. > SC supports more file formats that MIP, so that could explain it. Or a song has moved and an SC rescan is required to delete an extra song that doesn't exist anymore? >If I set the desktop program to watch the same music folder that SC >watches, will that have no effect on the headless server? The MIP desktop application and MIP headless server should be configured to use the same MIP library cache. The headless server doesn't automatically scan any folders - you have to tell it to look for new files by entering a path each time. I find it easier to start the MIP desktop app to automatically find new music, then stop analysis, save the library, then reload the library cache in the headless web UI. When adding new music into the MIP library, you should add files using the same music folder path as SC (i.e. same drive letter). _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
