Reply to thread

Message

Did you turn on "Enable Debug Logging" in XBMC Settings/System? Not sure if it will give any indication of the problem, but it's worth turning it on to see if anything interesting shows up. The logging all goes into xbmc.log in the XBMC directory. Please don't post it here - I'm unlikely to find anything that you wouldn't. But report back anything that looks sinister.

You configure the plug-in after adding it, by highlighting (but not clicking on) the plug-in by name and bringing up the context menu. In XBMC for Windows that's a right-click on the plug-in name; on XBMC for XBox it's the white button on your controller. From there, choose "Plugin Settings" and you should see a screen asking for hostname, port and sharename.

The settings.xml file you found does not hold the actual settings, and instead defines how the settings page works. It holds the default values as well as GUI object types and numbers. The actual settings used and configured are saved in "XBMC\userdata\plugin_data\video\TVServer\" in a file that's also named settings.xml. You're welcome to change the settings in that file, if you can't find the context menu.

Port 9596 is the port used by the "XBMC TV Server" plug-in for MediaPortal, and not MediaPortal itself. XBMC isn't emulating a MP client, and instead it has to talk to a corresponding plug-in on the MP server. This XBMC-to-MP integration works by having a plug-in at each end, and they talk to each other over port 9596. The MP-side plug-in (the DLL) accepts a connection on port 9596 from the plug-in on the XBMC side, and translates the requests from the XBMC plug-in into MP function calls.

The XBMCTvServer.DLL I have is 36kb, dated 2008-11-14.

<blockquote data-quote="jez" data-source="post: 359644" data-attributes="member: 84238">Did you turn on &quot;Enable Debug Logging&quot; in XBMC Settings/System?&nbsp; Not sure if it will give any indication of the problem, but it's worth turning it on to see if anything interesting shows up.&nbsp; The logging all goes into xbmc.log in the XBMC directory.&nbsp; Please don't post it here - I'm unlikely to find anything that you wouldn't.&nbsp; But report back anything that looks sinister.You configure the plug-in after adding it, by highlighting (but not clicking on) the plug-in by name and bringing up the context menu.&nbsp; In XBMC for Windows that's a right-click on the plug-in name; on XBMC for XBox it's the white button on your controller.&nbsp; From there, choose &quot;Plugin Settings&quot; and you should see a screen asking for hostname, port and sharename.The settings.xml file you found does not hold the actual settings, and instead defines how the settings page works.&nbsp; It holds the default values as well as GUI object types and numbers.&nbsp; The actual settings used and configured are saved in &quot;XBMC\userdata\plugin_data\video\TVServer\&quot; in a file that's also named settings.xml.&nbsp; You're welcome to change the settings in that file, if you can't find the context menu.Port 9596 is the port used by the &quot;XBMC TV Server&quot; plug-in for MediaPortal, and not MediaPortal itself.&nbsp; XBMC isn't emulating a MP client, and instead it has to talk to a corresponding plug-in on the MP server.&nbsp; This XBMC-to-MP integration works by having a plug-in at each end, and they talk to each other over port 9596.&nbsp; The MP-side plug-in (the DLL) accepts a connection on port 9596 from the plug-in on the XBMC side, and translates the requests from the XBMC plug-in into MP function calls.The XBMCTvServer.DLL I have is 36kb, dated 2008-11-14.</blockquote>

[QUOTE="jez, post: 359644, member: 84238"] Did you turn on "Enable Debug Logging" in XBMC Settings/System? Not sure if it will give any indication of the problem, but it's worth turning it on to see if anything interesting shows up. The logging all goes into xbmc.log in the XBMC directory. Please don't post it here - I'm unlikely to find anything that you wouldn't. But report back anything that looks sinister. You configure the plug-in after adding it, by highlighting (but not clicking on) the plug-in by name and bringing up the context menu. In XBMC for Windows that's a right-click on the plug-in name; on XBMC for XBox it's the white button on your controller. From there, choose "Plugin Settings" and you should see a screen asking for hostname, port and sharename. The settings.xml file you found does not hold the actual settings, and instead defines how the settings page works. It holds the default values as well as GUI object types and numbers. The actual settings used and configured are saved in "XBMC\userdata\plugin_data\video\TVServer\" in a file that's also named settings.xml. You're welcome to change the settings in that file, if you can't find the context menu. Port 9596 is the port used by the "XBMC TV Server" plug-in for MediaPortal, and not MediaPortal itself. XBMC isn't emulating a MP client, and instead it has to talk to a corresponding plug-in on the MP server. This XBMC-to-MP integration works by having a plug-in at each end, and they talk to each other over port 9596. The MP-side plug-in (the DLL) accepts a connection on port 9596 from the plug-in on the XBMC side, and translates the requests from the XBMC plug-in into MP function calls. The XBMCTvServer.DLL I have is 36kb, dated 2008-11-14. [/QUOTE]