[mythtv-users] xbmc with mythtv 0.25

[Raymond Wagner]

On 4/11/2012 18:25, Oliver Maunder wrote:
> On 11 April 2012 22:29, jacek burghardt <jaceksburghardt at gmail.com 
> <mailto:jaceksburghardt at gmail.com>> wrote:
>
>     I hope there is someone that can point me in right direction xbmc
>     handles few thinks better then mythfrontend
>
>
> Looking at the XBMC source code, the most recent Myth protocol version 
> supported is 64. 0.24 uses version 63 and 0.25 uses version 64.

No.  0.25 uses version 72.

> However, according to the Myth Protocol wiki page 
> <http://www.mythtv.org/wiki/Category:Myth_Protocol>, XBMC implements 
> the Myth protocol version badly - which essentially means that it will 
> pretend to support a more recent version than it really does. As the 
> wiki says - "This should be considered very dangerous behavior, and 
> should not be used to connect to any production backend."

The MythBox plugin implements the protocol properly.  However, the 
MythBox plugin only implements a content list, and points XBMC at what 
content to actually play.  XBMC in turn uses the libcmyth implementation 
which blindly parrots back the version mythbackend speaks.  Starting 
with protocol version 62, this no longer works, as the backend will 
refuse connection to anything using the wrong token for that version 
number, forcing applications to actually update themselves to support 
new protocol versions.

Last I heard, both libcmyth and MythBox were deprecated by some new 
built-in PVR support, intended to allow access to MythTV, TVHeadend, 
VDR, or any other recording backend.  I do not know the current state of 
development of that replacement.

> It looks like XBMC generally queries the MySQL database directly, 
> rather than making requests via the Myth protocol, so the protocol 
> version it supports might not matter than much. Of course, if the 
> database structure has changed then there could be problems.

At the moment, there are many things that simply require direct database 
access to accomplish.  The intent is that all such mechanisms be removed 
prior to 0.27, to allow the migration to an embedded MySQL database that 
the backend has full control over.  Beyond that point, all communication 
will have to be performed through the backend protocol, or more likely 
through the new Services API.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20120411/bdf88388/attachment.html>