<div> </div>
<div><span class="gmail_quote">On 11/11/07, <b class="gmail_sendername">David Shay</b> <<a href="mailto:david@shay.net">david@shay.net</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><snip></blockquote>
<div> </div>
<div><span class="e" id="q_1162ec66b89b4632_1"> </span></div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div>Reading the database is not really the right approach - querying the backend via the protocol would be.</div>
<div> </div>
<div>Even that is not necessary for this piece of information -- it is available via the status port on 6544. In this case, you can get quite a bit of info from the XML status on <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://my.myth.ip:6544/xml" target="_blank">
http://my.myth.ip:6544/xml </a> You get a list of encoders, and if one is recording, you will see what program, callsign, and channel it is tuned to.</div>
<div> </div>
<div> </div></div></blockquote></div>
<div><br>A complete solution could look like this:</div>
<div> </div>
<div>* Local .lircrc entries on each frontend with appropriate irexec entries for the keys which you want to use to control the STB. I am assuming these will have to be a unique set of navigation and "enter" keys since otherwise they would conflict with the function and meaning of those in myth. These irexec entries would call a script on the local frontend which would:
</div>
<div> </div>
<div>* call wget on the backend status port. Parse this to determine which the video-on-demand tuner. Personally, I would cache this output for a minute or two locally to avoid repeated unnecessary calls to the status port. Once the tuner was determined use "rexec" or the remote-execution mechanism of your choice to call an "irsend" script on the backend with the desired parameters.
</div>
<div> </div>
<div> </div>
<div> </div>