<br><br><div class="gmail_quote">On 3 February 2011 08:18, Alex Butcher <span dir="ltr"><<a href="mailto:mythlist@assursys.co.uk">mythlist@assursys.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, 2 Feb 2011, Gary Dawes wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I originally saw and ignored this tread based on the title, but based on<br>
other's experiences I am now wondering if something has changed on the<br>
multiplexes somehow, and this is making the tuning unreliable and causing<br>
the tuners to crash now and again.<br>
</blockquote>
<br></div>
My system continues to behave after I fixed the auto fields and restarted<br>
the backend. A developer on the IRC channel was somewhat optimistic that<br>
specifying actual values rather than using auto would improve matters.<br>
<br>
Best Regards,<br><font color="#888888">
Alex</font><div><div></div><div class="h5"><br></div></div></blockquote><div>I ran a full rescan, which has improved things, but the cards are still failing occasionally, which is a pain.<br><br>gonna try changing any auto values to see if that helps.<br>
<br>Thanks<br></div></div><br>