Posts: 2
Joined: Jan 2005
Reputation:
0
rubenonrye,
thanks for the quick reply. to newegg i go! ;-)
this look very promissing. i appreciate the hard work you guys have put in!
thanks
Posts: 3
Joined: Nov 2003
Reputation:
0
i have installed the latest cvs builds of xbmcmyth but i'm now getting the following error when selecting recorded shows :
23-01-2005 19:41:58 info traceback (most recent call last):
23-01-2005 19:41:58 info file "q:\scripts\mytv.py", line 39, in oncontrol
23-01-2005 19:41:58 info win = mythtvrecorded.recordedwin()
23-01-2005 19:41:58 info file "q:\scripts\mythtvrecorded.py", line 32, in
23-01-2005 19:41:58 info self.loadrecordedshows()
23-01-2005 19:41:58 info file "q:\scripts\mythtvrecorded.py", line 115, in loadrecordedshows
23-01-2005 19:41:58 info self.indexrows()
23-01-2005 19:41:58 info file "q:\scripts\mythtvrecorded.py", line 135, in indexrows
23-01-2005 19:41:58 info if recording.starttime() > self.recordings[show].starttime():
23-01-2005 19:41:58 info file "q:\scripts\mythtvprogram.py", line 135, in starttime
23-01-2005 19:41:58 info return sre.sub( "[:|\\-| ]", self.__data[11])
23-01-2005 19:41:58 info typeerror: sub() takes at least 3 arguments (2 given)
any ideas ?
Posts: 22
Joined: Oct 2004
Reputation:
0
i'm running mythtv cvs as of about a month ago.
xbmc 1.1.0 release. anything later than this seems to be really unstable for me...
a few issues can make livetv crappy, but tha main solution for me is just to turn all your xbmc caches off. i run my xboxes/backend off a 802.11g bridged wifi and livetv is fine.
the reason livetv drops back to the guide is because xbmc has a cache of the livetv buffer that is old, then it starts reading the new buffer from the location at the end of the cache which doesn't exist, so it crashes. we ae working on a few ways to sort this, but the easiest way for me is just to kill the caches...
Posts: 3
Joined: Nov 2003
Reputation:
0
thanks for the fix which manages to bypass the previously reported error but unfortunately i'm still using mythtv 0.16 which uses protocol 13 and doesn't work at the moment. i guess it's all about being patient and waiting until more of the bugs are eradicated. i would imagine though that the majority of mythtv users are running 0.16 as it's the latest released stable version.
is there anyone out there who has managed to get the current scripts working with mythtv 0.16 ?? i read about a temporary fix in a previous post in this thread but things have moved on since then.
my current problem with the protocol is :-
01-02-2005 18:45:22 info file "q:\scripts\mythtvprogram.py", line 208, in programflags
01-02-2005 18:45:22 info raise mythtv.protocolversionexception, "unsupported call for protocol version"
01-02-2005 18:45:22 info protocolversionexception: unsupported call for protocol version
Posts: 11
Joined: May 2004
Reputation:
0
smurf2
Junior Member
Posts: 11
hello
i am using 0.16 and have issues with playing live tv and scheduling recordings .i hope this will be fixed with imminant release of .17 sometime this week / weekend
i guess my question is a little off topic.it is the xebian install with the mythfrontend .how have you guys got the xebian install to work with the cvs / .17 with the new protocol .i would ask at the xbox mythtv frontend bbs but it was hacked and hasn't come back up yet
any help or pointers would be apreciated
latz mary