Bugzilla – Bug 2958
iTunes reload interval should be set to 0 for new scans
Last modified: 2008-09-15 14:38:10 UTC
I was only able to scan my iTunes library (10k+ songs) by setting the iTunes "reload interval" to 0 (zero). This only appears necessary for the first scan. I think the default (3600s) was cause the scan to be aborted in the middle. Suggested Fix: 1. When user selects "Clear library and rescan everything", set iTunes reload interval to 0. 2. When rescan is complete, set reload interval back to "3600" or previous values.
Note, I almost returned my Slim player due to this odd behavior. I waited an entire weekend for iTunes to update, then just before sending my player back, saw the suggestion to set update interval to '0'!
This is misleading. The reload interval should have no effect on an initial scan. The reload interval only applies when the iTunes library is changing, and only applies as an interval since the last *completed* iTunes scan.
If you are able to replicate this initial scan, try turning d_itunes and d_import on and check the log. Better yet, run c:\program files\slimserver\server\slim.exe --d_itunes --d_import from a commant prompt and see if there are any dumps to STDOUT that explain why the scan aborted. Was the iTunes library in flux? The design change is certainly possible to implement, just making sure that the reason for doing so is actually going to fix the problem at hand.
Please try the latest nightly release (either 6.2.2 or 6.5) and see if the issue is better. The rescan logic is much improved. If you are still having problems, please reopen the bug with details on your setup (library size and location, main server settings page, itunes settings page).