2009-01-03, 10:34
@d99fish - As mentioned earlier, ping on OSX uses a different name resolution to something like nslookup. Does the hostname resolve using nslookup?
Have you tried using the IP address directly in the myth:// URL? I've only ever used the IP address rather than the hostname.
I've had some lockups playing myth:// content before, but not for ages. What version of XBMC are you using?
@Swifty - The "Client speaks protocol version 8 but we speak 43" messages in the log are normal based on my experience. I believe that protocol 8 is simply used to get the version of the MythTV backend.
What myth:// URL are you using, and what OS are you running XBMC on?
I've been using the SVN version of XBMC to communicate with the latest Mythbuntu distribution (0.21) and it's been working fine (other than the known problems with the current myth:// protocol functionality).
@Everyone - Has anyone on this list been using the XBMC myth:// protocol functionality with a 0.22 MythTV backend successfully?
Have you tried using the IP address directly in the myth:// URL? I've only ever used the IP address rather than the hostname.
I've had some lockups playing myth:// content before, but not for ages. What version of XBMC are you using?
@Swifty - The "Client speaks protocol version 8 but we speak 43" messages in the log are normal based on my experience. I believe that protocol 8 is simply used to get the version of the MythTV backend.
What myth:// URL are you using, and what OS are you running XBMC on?
I've been using the SVN version of XBMC to communicate with the latest Mythbuntu distribution (0.21) and it's been working fine (other than the known problems with the current myth:// protocol functionality).
@Everyone - Has anyone on this list been using the XBMC myth:// protocol functionality with a 0.22 MythTV backend successfully?