<br><br><div class="gmail_quote">On Fri, Aug 3, 2012 at 6:08 AM, Lee Koloszyc <span dir="ltr"><<a href="mailto:pantslessape@gmail.com" target="_blank">pantslessape@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Fri, Aug 3, 2012 at 5:16 AM, James Purl <span dir="ltr"><<a href="mailto:convbox@jamespurl.com" target="_blank">convbox@jamespurl.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>I will begin digging deeper this weekend--just wanted to see if there was a "Oh yeah, you have to do -blank- to the channel or tuner setup" out there.</div><div><br></div><div>Thanks</div><span><font color="#888888"><div>
James</div>
</font></span></blockquote></div><br></div>Have you updated to the latest firmware on the HDHR Prime. I recall something similar happening with the original firmware I had on my Prime. I updated at that point and it has worked fine since.<span class="HOEnZb"><font color="#888888"><br>
<br>Lee<br></font></span><br></blockquote><div>Yeah, when I downloaded the latest Windows installer and ran it, it immediately upgraded the firmware on the Prime to 20120405. I suspect I'm just finding an edge-case Myth issue with my system. When I get a chance, I'll turn up the logging and see what the backend says when it is failing. Also, as a kluge to have to stop checking that the Prime doesn't get assigned one of the bad channels (which I then add an override to the recording to have it "prefer" one of the CETON inputs), I'm gonna setup an extra video source with the bad channels set to "not visible".<br>
<br></div></div>