<br><br><div class="gmail_quote">On Sep 27, 2007 2:09 PM, Paul Onley <<a href="mailto:onley@worldnet.att.net">onley@worldnet.att.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>> By my understanding, the "extra information" you're trying to get from<br>> the backend is which capture card is being used to record the show so<br>> that you can use it to submit the commands to the STB using the proper
<br>> "remote codes."<br>> If this is the case, you have 2 (easy) options:<br>> a) Create 4 scripts, change_channel_stb1, change_channel_stb2,<br>> change_channel_stb3, change_channel_stb4. Then, map the appropriate
<br>> script to the "External channel change command" for the input connected<br>> to that STB. Since the "External channel change command" is a per-input<br>> setting, you use each of the 4 scripts for your 4 inputs.
<br>> b) Create 1 script which accepts 2 arguments: the STB identifier and a<br>> channel number. Then, for the "External channel change command" foreach<br>> input, use "change_channel 1", "change_channel 2", ... The channelnumber
<br>> will be appended to the command after the command and argumentyou<br>> specify. So, you use the STB ID (1, 2, 3, 4) to determine whichremote<br>> code to use and use the channel number to send the appropriatecodes to
<br>> the STB.<br>> So, the idea isn't to get Myth to send additional data to the channel<br>> change script, but to call the "right" script (for a, or call the script<br>> correctly, for b). I used both approaches as various times to controlmy
<br>> 2 STB's. Granted, I haven't used firewire output, before, but sinceyou<br>> mention Myth is sending channel information to an "external tuner<br>> script," I'm assuming it works exactly the same way for firewire as it
<br>> does for analog capture cards.<br><br>> HTH. And, thanks for bringing the discussion to the -users list.<br>> Mike<br><br>Hi Mike, Thanks for the reply but over the course of several replys<br>my original intent became blured.
<br><br><br>>> I am trying to create a setup where I can control multiple STBs and<br>>> navigate the Comcast OnDemand menus. I have the channel changing scripts<br>>> working using the serial ports but I can't find any way to send anything
<br>>> other than the channel info to the STB. I need to send left, right, up,<br>>> down and select to the STB but since there are 4 STBs this info will<br>>> haveto be sent through the backend to get to the right box.
<br>>> Mythtv breaks out the tuning info and sends it to the external tuner<br>>> script but I don't see any way to send other info to the external tuner<br>>> script. Is there a hook that I don't know about or is this something
<br>>> thatcould be implemented?<br><br><br>I need to send non-channel info to the STBs to use the On Demand<br>programing feature (this is channel 1 on Comcast and once there you<br>interact with onscreen menus to select a show to watch. Many feel this
<br>service has no value with a Myth system but it has great content for<br>the kids) on Comcast cable. I have the 4 STBs working and have<br>added code to DCT2000 channel_change script so that it will accept<br>a command line arg for the serial port. I then give the serial arg in
<br>the "external tuner command" area in myth so that all 4 STBs can use<br>the same script. This is all working very well. My problem is that I<br>need to be able to send other codes to the STBs to interact with on
<br>screen menus that are not part of myth. I would like to be able to send<br>these through the SAME mechanism that we have outlined here so that I<br>don't have to interogate the backend to see which tuner I am watching
<br>and then send the left, right, up, down, and select codes to a daemon<br>on the backend which will then pass them to the appropriate STB.<br><br>My first approach was to choose dummy channels and setup the lircrc<br>config file to send say 981 when you press the down arrow. Then I went
<br>into the channel_change script and setup a case that would change 981<br>to DOWN and send it to the STB. This worked like a charm but Myth will<br>not send a channel change to the STB if you are already on that channel
<br>so you could never send 2 consective down arrows for example. I posed<br>this in DEV as I thought it would be possible to preface a command<br>(esc code it if you will) so that myth would send it to the built in<br>"external tuner command" but digging into the Myth code is above my
<br>ability. The best approach I have yet been able to come up with is to<br>have lircrc call a script when the down arrow is pressed that will<br>interogate the backend to see which STB I am watching then send the<br>STBs ID and the desired code to a daemon on the backend which would
<br>forward the code to the correct STB. This is a lot more monkey motion<br>than being able to ask Myth to do it through the channel change mechanism.<br><br>Paul<br><font color="#888888"><br><br><br>--<br>Using Opera's revolutionary e-mail client:
<a href="http://www.opera.com/mail/" target="_blank">http://www.opera.com/mail/</a><br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org
</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></font></blockquote></div><br>The change channel script does not interact solely with mythtv. Sorry, If I missed the rest of your post, but I was wondering if you thought about bypassing myth's channel change to achieve what you want. Perhaps by using irexec executing the channel change command directly with arguments for up, down ,etc.
<br><br>. <br><br><br>