woo - library size may indeed be the issue. I emailed Music IP support about this and got some interesting information (which I also posted to the bug report):
With the Music IP service running, try browsing to http://localhost:10002/api/songs?extended SlimServer 6.5 tries to call that URL to retrieve a listing of all the songs Music IP knows about (at least I think that's why it makes that call). In my log file, the Slim Devices bug crew found that that URL was timing out. I tried browsing to it on my machine and it timed out for me as well. Music IP recommended I use the new "paging" option which allows you to pull back a set number of tracks from Music IP at one time, like this: http://localhost:10002/api/songs?page=0&results=100 That will return just the first 100 results (note that page is a 0-based index). "If you enable paging, then you need to make sure to change the parsing of the results, as the first thing returned will be the total number of items (so you can calculate how many pages of data need to be retrieved)." SlimServer 6.3 doesn't seem to make a call to api/songs?extended (I don't understand how it pulls data from Music IP) but I don't have the same problem in 6.3. This may shed some light on your issue, since you said your library was about 23K tracks. Mine's 29K, so maybe we're having the same issue. FYI, I'm running with the following debug flags (as recommended by Slim Devices): d_musicmagic, d_import, d_scan, d_sql -- tfish77 ------------------------------------------------------------------------ tfish77's Profile: http://forums.slimdevices.com/member.php?userid=1809 View this thread: http://forums.slimdevices.com/showthread.php?t=26275 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/beta
