* tfish77 shaped the electrons to say...
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):
This does shed a lot of light on the issue.
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.
Yes, that's correct - we asked for that call so that we could make just 1
HTTP request to MusicIP instead of as many songs as you have.
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).
Hmm.. there will need to be some rework to suppor this.
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.
Also correct - the ?extended feature was introduced in 6.5
6.3 makes a request to MusicIP for every song.
-D
--
<iNoah> all your base class are belong to us
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/beta
