On Mon, Jun 4, 2012 at 6:39 PM, Jean-Yves Avenard <span dir="ltr"><<a href="mailto:jyavenard@gmail.com" target="_blank">jyavenard@gmail.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 class="im">On 3 June 2012 18:38, Karl Dietz <<a href="mailto:dekarl@spaetfruehstuecken.org">dekarl@spaetfruehstuecken.org</a>> wrote:<br>
<br>
> One is that the channel scanner stores the center frequency instead of<br>
> the offset frequency of the transports which makes successful tuning<br>
> harder depend on the quality of your DVB-T frontend.<br>
> <a href="http://code.mythtv.org/trac/ticket/9777" target="_blank">http://code.mythtv.org/trac/ticket/9777</a><br>
<br>
</div>This issue is mostly specific to the DVB-T adapter used and none of<br>
them will behave the same.<br></blockquote><div> </div><div> Agree, and this one worked fine on 0.20.<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
The better solution is to stick with DVB-T adapters known to work with MythTV<br></blockquote><div><br> Such as? <br><br> Looks like there should be a list of tuners best supported per MythTV release :)<br><br></div></div>