On Wed, 02 Feb 2005 09:23:56 -0500, Kirk Anderson <[EMAIL PROTECTED]> wrote: > jds wrote: > > >hey kirk, > > > >just some thoughts... > >a) have you tried restarting mythtv-backend as noted in my writeup? > > see "IMPORTANT NOTE #1" in stage 5 at > > http://losdos.dyndns.org:8080/public/mythtv-info/IR-BLASTER-HOWTO.html > >b) are you putting the complete pathname into the mythtv-setup dialog? > >c) when all else fails, perhaps reboot and try again? > > > >let us know how you make out. > > > >regards, > >jds > > > > > Tried the restart thing numerous times. No help. > Tried the reboot thing numerous times (just to be safe). No help. > The external changer field DOES have the complete path to the executable > script. > It appears from the verbose debug messages that the front end at least > knows it > wants to change the channel. I'm guessing it might be some communication > issue > between my frontend and backend and then the backend just never bothers > calling > the script. > > I had already tried modifying my script to dump stuff to a file in /tmp, > just to see if > it was ever being invoked. Nothing ever showed up implying that my > channel changer > script just isn't ever being called. > > Still looking into it though ..... > > > > > > > > >>But when I enter ANY script name into mythtv-setup, in the > >>"External Channel Change Script" field, it never appears to > >>get called when I do a remote control channel change operation. [snip]
As hokey as it sounds, I had to do the following to get my external channel-change stuff to work (ir blaster for Expressvu dish) during system bootup (part of the ivtv init script). It's ugly, but it works for me. YMMV. /usr/init.d/mythtv-backend restart
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
