mudlark wrote: > no. I can change sever either way, but using the LMS screen leaves the > picoreplayer gui inoperative. > > The obvious way to deal with this problem is to make sure that any > changes of LMS machine must be put in place in the picoreplayer web gui, > but this means noting the required LMS IP in the LMS gui and then only > making the change with the picoreplayer gui.
I am trying to recreate the problem you describe so that I might understand the failure and give you some advice. From the description provided, there are many assumptions I make in how you found the problem. Using my assumptions, I do not see the same problem. If you can be a little more specific, then I (or others) may be able to give you some more productive advice. Here is my approach: Environment - LMS instance 1 - DNS:McPVR, Windows 7 SP1, Logitech Media Server, LMS 7.7.3 - 1375965195 @ Mon Aug 12 11:14:33 CUT 2013 LMS instance 2 - DNS:Vortexbox, Fedora Linux, Vortexbox RC 2.3, LMS 7.8.0 - 1391769631 @ Wed Feb 26 13:12:02 EST 2014 Player 1 - DNS:TestPlayer, Tiny Core Linux, PiCorePlayer v1.14d Session - (make sure everything is powered up and connected) 1) Start a clean instance of Google Chrome 2) In browser first tab address bar enter "\\mcpvr:9000" - this is the default instance of LMS and will capture any player using autodiscovery 3) Click "settings" option in lower right hand corner - this should bring up a new browser tab with the Settings screen for instance 1 4) Click the "Information" tab in the Settings window 5) Verify that "TestPlayer" IS listed in the Player Information area 6) Start a new browser tab 7) In browser third tab address bar enter "\\vortexbox:9000" 8) Click "settings" option in lower right hand corner 9) Click the "Information" tab in the Settings window - this should be the browser fourth tab open now 10) Verify that "TestPlayer" is NOT listed in the Player Information area 11) Start a new browser tab 12) In browser fifth tab address bar enter "\\testplayer:8077" - this should be the piCorePlayer splash screen 13) Click "Squeeezelite settings" menu bar option 14) Enter "12.168.1.138" in the Squeezelite server IP entry box - this IP address is found in the browser fourth tab in the Logitech Media Server Status section. Your address in likely different. 15) Click "Submit" button - this should produce output from the variable updates, verify the "SERVER_IP=" is correct 16) Click "Restart" button - this should show stop/start of Squeezelite 17) In browser fourth tab do the following: Refresh (F5), select "Information" tab, Verify that "TestPlayer" IS listed in Player Information To me, this represents a recreation in my environment of what I assume you are doing. When I do this there is not a problem. If you can provide more details I will try to give better advice. ------------------------------------------------------------------------ mcdudeabides's Profile: http://forums.slimdevices.com/member.php?userid=57765 View this thread: http://forums.slimdevices.com/showthread.php?t=97803 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
