On Jan 31, 2008 9:55 AM, Nathan Rutman <<a href="mailto:nrutman@gmail.com">nrutman@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><br><div>Anyhow, on to more useful discussion: <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>From: "Michael Rice" <<a href="mailto:mikerice1969@gmail.com" target="_blank">mikerice1969@gmail.com</a>><div class="Ih2E3d">
<br>
<br>> So I'm trying to figure out:<br><br>> c. is ss=60 (signal strength) awful? Myth can lock on with with ss=67,<br><br>Maybe it is awful. <br></div></blockquote><div><br>I'm beginning to suspect this is the problem after all. A suggestion in the<br>
SiliconDust forum led me to the frontend Settings->TV->General->Minimum<br>Signal Strength, which by default is 65. This sounded great, but lowering<br>it doesn't seem to have helped at all. (Nor does changing the timeout there<br>
seem to affect anything.)<br><br>If anyone can explain why Myth doesn't use the HDHomeRun's /tuner0/program<br>setting (or how to get it to), I would be much obliged. <br><br></div></div></blockquote></div><br>To answer your question, lets browse the code for answers...<br>
<span class="c"><br>Looking at program: </span><a title="Show the r9729:15437 differences restricted to trunk/mythtv/libs/libmythtv/hdhrsignalmonitor.cpp" href="http://svn.mythtv.org/trac/changeset/15437/trunk/mythtv/libs/libmythtv/hdhrsignalmonitor.cpp?old=9729&old_path=trunk%2Fmythtv%2Flibs%2Flibmythtv%2Fhdhrsignalmonitor.cpp">trunk/mythtv/libs/libmythtv/hdhrsignalmonitor.cpp</a> it appears that the signal strength was hardcoded to 65 - and was changed to 45 in changeset 15437.<br>
<br>Tom<br>