Reply to thread

Yeah the more I thought about the MythTV shim idea (that's a good way to describe it), the more I realized it was a lot less practical.  It appears the mythtv protocol kinda sucks and half the stuff the MythTV front end does is by connecting directly to the backend mysql database. 

Here's the issue.  I'd love to start making a proper front end for xbmc to tvserver, I just can't do the xbmc/python side.  I can handle the TVServer plugin... The one there is a great start, and I'm confident I could make the tvserver plugin side of things do whatever the front end needed...

So, jez, I'm not sure what your capabilities here are, but would you be interested in doing the Python side of things?  Or anyone else for that matter?

As for the current error I'm getting, I think I found the solution.  Basically, when StartTimeShifting gets called, it gets passed a new User object, and a VirtualCard object as an out parameter.  The plugin for TVServer currently does nothing with that VirtualCard when it *should* assign the user object the Id from the VirtualCard if timeshifting started successfully.  This way, the User.cardId will not be -1 when StopTimeShifting is called, as this is what's causing the error.

Here's the patch I've made (I'll test it later, I can't from where I am right now, but it does compile.):

[CODE]

Index: ServerInterface.cs

===================================================================

--- ServerInterface.cs    (revision 2493)

+++ ServerInterface.cs    (working copy)

@@ -77,6 +77,9 @@

             {

                 _isTimeShifting = true;

                 rtspURL = vcard.RTSPUrl;

+

+                //Need to keep track of the card the user is timeshifting with or StopTimeshifting breaks

+                me.CardId = vcard.Id;

             }

             return result;

         }

[/CODE]