<br><br><div class="gmail_quote">On Nov 11, 2007 12:43 PM, Doug Young <<a href="mailto:goofdad@gmail.com">goofdad@gmail.com</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;">
<div class="Ih2E3d">On Nov 11, 2007 5:46 AM, David Shay <<a href="mailto:david@shay.net">david@shay.net</a>> wrote:<br>> A complete solution could look like this:<br>><br>> * Local .lircrc entries on each frontend with appropriate irexec entries for
<br>> the keys which you want to use to control the STB. I am assuming these will<br>> have to be a unique set of navigation and "enter" keys since otherwise they<br>> would conflict with the function and meaning of those in myth. These irexec
<br>> entries would call a script on the local frontend which would:<br>><br>> * call wget on the backend status port. Parse this to determine which the<br>> video-on-demand tuner. Personally, I would cache this output for a minute
<br>> or two locally to avoid repeated unnecessary calls to the status port. Once<br>> the tuner was determined use "rexec" or the remote-execution mechanism of<br>> your choice to call an "irsend" script on the backend with the desired
<br>> parameters.<br><br></div>OK...I may be missing something, but it seems to me that interactive<br>is potentially the wrong solution. In my area, VOD is -always- on the<br>same channels, and the sequence (down, left, enter, up,
<br>enter...whatever...) is -always- the same. This means that anytime<br>I'm tuning to channel one (for example), I need to enter the channel<br>number, wait 3 seconds, send down, left, enter, wait two seconds, send
<br>up, enter. If this is the case, then you simply need to modify the<br>script that changes channels to be a tad smarter, something like this<br>pseudocode:<br><br><change channel to> channel<br><br>if (channel == 1) then
<br> irsend <some extra codes><br>fi<br><br>With this approach, the fact that you're watching VOD becomes<br>invisible, you're doing it on the backend and have all the information<br>necessary, etc, etc, etc.
<br><br>HTH<br><font color="#888888">--<br>Doug<br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br></font><div><div></div>
<div class="Wj3C7c"><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></div></div></blockquote></div><br>I think that solution is ok for the initial setup of the VOD channel. I think he wants to be able to select any programming available as VOD, so the mechanism to input up, down , etc. still needs to be present.
<br><br>I didn't know about the /xml option in the status port. It exposes even more information for grepping, such as the Channel number so this is a reliable way of determining if one frontend is accessing VOD. Unfortunately there is no record there of which frontend is accessing which encoder which is what is really needed I think. Thats why I rrecomended a unique channel for each STB so the encoder you use with each frontend is always known. I am curious as to what table in the database holds this information.
<br><br><br>