philippe_44 wrote: 
> Thanks for the clear log & feedback. To solve problem #1 and if your
> uPnP device configuration does not change, use the <upnp_scan_interval>
> to 0. That will totally prevent the rescan of upnp devices. Some devices
> tend to not respond in time (quick enough) to the regular upnp rescan
> process and then are removed from the list. But if your config does not
> change, you do not need a rescan. I will also add a parameter in 0.2.0.0
> to give more time to rescan
> 
> For the <accept_next_uri> paramater, after looking at the log, you
> indeed need to set it to 0 because your player does not accept the next
> song to play to be set in advance (error 401). This is exactly what this
> parameter is made for, so everything is fine
> 
> NB: The automatic addition of newly discovered players in LMS is not
> similar to disable uPnP player discovery . The idea is that, newly
> discovered uPnP players can still be listed in file when a "save"
> command is entered on the command line, even if they are not added to
> LMS

Hi Philippe, thank you very much for your prompt suggestion and clear
explanation.  I changed the value of <upnp_scan_interval> to '0' and am
playing the long song list as a stress test.  No unexpected termination
so far.  I would update you with the result.



LMS 7.8.0 w/SSOTS 4.14 on QNAP TS-439 Pro.  Touch, Duet, Boom, Classic,
PiCorePlayer w/Dac, BT or DLNA speakers.  SqueezeLite on two PCs. 
Squeeze Player + Squeeze Commander on Android cell & tab.  Onkyo 5.1
Amplifier, passive & powered speakers.
------------------------------------------------------------------------
firebelli's Profile: http://forums.slimdevices.com/member.php?userid=63867
View this thread: http://forums.slimdevices.com/showthread.php?t=102496

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to