Catching up with MythTV protocol changes in trunk

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Point it at a more recent Trunk build

What is the expected output? 
That it connects OK with MythTV backend

What do you see instead?
Protocol errors, new trunk currently at v48

What version of the product are you using? On what operating system?
Recent XBMC SVN build on Linux

Please provide any additional information below.

Original issue reported on code.google.com by Mark.deR...@gmail.com on 26 Aug 2009 at 12:04

[GoogleCodeExporter]

Support for protocol 48 will be in next beta release (hopefully a couple more 
weeks)

Original comment by semir.pa...@gmail.com on 28 Aug 2009 at 8:17

• Changed state: Started

[GoogleCodeExporter]

Issue 57 has been merged into this issue.

Original comment by semir.pa...@gmail.com on 28 Aug 2009 at 10:15

[GoogleCodeExporter]

You're free to edit mythprotocol.py in the meantime. Its pretty 
straightforward...

Original comment by semir.pa...@gmail.com on 28 Aug 2009 at 10:16

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have been helping the maintainer of XMBC's native myth support on the same 
problem,
details of his findings may help identify the differences. See
http://xbmc.org/trac/ticket/7080 for the details.

Original comment by Mark.deR...@gmail.com on 15 Sep 2009 at 9:02

[GoogleCodeExporter]

If there isn't any particular changes since protocol 44 I have created a patch 
that
works so it at least starts.

Added a patch earlier which I have removed because it didn't work.

Original comment by thomas.n...@gmail.com on 16 Sep 2009 at 5:15

Attachments:

• proto48_v2.diff

[GoogleCodeExporter]

Fixed in svn 1510. Protocol updated to 50

Original comment by semir.pa...@gmail.com on 17 Oct 2009 at 5:45

• Changed state: Fixed
• Added labels: Priority-High
• Removed labels: Priority-Medium