Jacob, Would it not be easier to base the command on the protocol version of mythtv? I believe 0.23 is running protocol version 56. So figure out where/when the message changed? Did it change in version 55, 54, etc???? Then mvpmc could just do a if on the protocol version.
Mike ----- Original Message ---- > From: Jacob Grydholt Jensen <[email protected]> > To: [email protected] > Cc: [email protected] > Sent: Sun, May 9, 2010 6:59:49 PM > Subject: Re: [Mvpmc-devel] [Mvpmc-users] MythTV 0.23rc > > On 3 May 2010 02:27, Dave Topan < > href="mailto:[email protected]";>[email protected]> > wrote: > Migrating to a new server I was forced to upgrade to 0.23rc. Now > I keep > getting errors saying that the connection to mythtv was lost. I > am > assuming from previous threads that this is due to the protocol > being > changed. Please let me know what traces are needed to assist in > resolving > this. Hi, I recently upgraded to Mythbuntu 10.04 > which follows the 0.23 branch, and ran into this problem as well. When a > recording is shown, the connection is lost after some period of > time. I believe I have tracked it down to the fact that the mythtv > protocol has changed. The culprit seems to be the > RECORDING_LIST_CHANGE message. In order to improve performance for the mythtv > frontend, this message now has two alternatives. One is ADD which is not > really a problem for mvpmc since it will just be reported as an > unknown message. The other is UPDATE which poses a problem since it carries > a proginfo structure with it. Since mvpmc is unprepared for this, it will > end up in an undefined state and will disconnect when the next myth backend > message arrives. I have attached a patch which works for me with > Mythbuntu 10.04. I haven't tried it with other versions, but I believe that > it handles the old RECORDING_LIST_CHANGE message correctly. A dongle > with the patch applied to the git HEAD can be downloaded > from http://www.grydholt.dk/dongle.bin.mvpmc. If you have the time > please check it out. If you run into any problems please run mvpmc with > the -M option and redirect the log output to a mount with plenty of > room and mail the log file to mailing list. Best regards, Jacob > Grydholt ------------------------------------------------------------------------------ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
