[ATrpms-users] My brief experience with mythtv 0.21

[Jeffrey J. Kosowsky]

mythtv at blandford.net wrote at about 13:39:41 -0700 on Thursday, January 3, 2008:
 > Jeffrey J. Kosowsky wrote:
 > > 
 > > - Also in mythweb, I didn't see any pixmaps of the individual programs
 > >   there was just a blank small rectangular spot to the left of the
 > >   streaming buttons
 > > 
 > 
 > Mythweb requires upnp support so ensure that is enabled.

I have libmythupnp installed -- what else needs to be done to enable
upnp support?

 > I have this issue to and there is an open ticket regarding it:
 > 
 > http://svn.mythtv.org/trac/ticket/3217#comment:17
 > and
 > http://bugzilla.atrpms.net/show_bug.cgi?id=1163
 > 
 > It is being looked at.  It only happens with some people.  The first one 
 > includes a workaround that works for me.
 > 
 > > - Mythfrontend started up with a blue screen saying something like
 > >   DON'T CONNECT TO MYTHBACKEND. I wasn't sure what this meant but it
 > >   seemed to work anyway.
 > > 
 > 
 > This is because of the new auto discovery patches.  The mysql.txt file 
 > isn't used anymore to locate the mythtv backend ( but it can fall back 
 > to it ).
 > 
 > In the mythtvsetup screens, there is a new field for a pin number 
 > required to connect to the backend.  You also need to add a multicast 
 > route to your network on the backend so the clients can discover it. 
 > The next time you start the frontend, the backend will show up in the 
 > browser where is currently says 'DON'T CONNECT TO MYTHBACKEND'.  Click 
 > on your mythtv backend, enter the pin, and that should be the last time 
 > you ever see that screen.
 > 
 > I don't use mythweb flash component so I can't speak to those issues.
 > 
 > Michael
 > 
 > 
Thanks very helpful - when I get some time, I will try again...