<html>
<head>
<meta content="text/html; charset=ISO-8859-15"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/08/13 12:03, lists.md301 wrote:<br>
</div>
<blockquote
cite="mid:CALOo+-kiOeOETxQuskA_6r+HCvN3DJRWoaMUoNZRj_U06K2Nqw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Aug 8, 2013 at 12:51 PM, Phil
Bridges <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:gravityhammer@gmail.com" target="_blank">gravityhammer@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra">
<div class="gmail_quote"><br>
<div>I use LiveTV on .26-fixes quite a bit, with a
HD Homerun and a HD HomeRun Prime. </div>
</div>
<br>
</div>
</div>
<br>
</blockquote>
</div>
<br>
<div>Thank you, that's the kind of response I was hoping for.
That's helpful to hear, as that's my exact setup, though I
will either be dropping the HD Homerun, when I lose
clear-QAM, though possibly may connect it to the antenna.<br>
<br>
</div>
One particular feature I am looking forward to taking
advantage of is the separate Recording and LiveTV tuner
priorities. As I mentioned in another mailing list message, I
got "behind" on upgrading because of Gentoo ebuilds that I
felt confident about, with the abandonment of github ebuilds
and a return to official Portage support. I plan to upgrade
(in a chroot test partition initially) once 0.27 has been
released and flushed out a bit.<br>
</div>
</div>
<br>
</blockquote>
<br>
I too use 0.27 with an HD Homerun prime and 2 x HDHRs with 2
antennas (pointing to two different markets). We use four different
frontends and have few problems. The biggest being when you select
a channel which doesn't sync. I have a slingbox in the UK, and am
trying to get it to work in MythTV as an additional source. At the
moment it is not working, but if the frontend gets changed to that
source (which I know doesn't work), it will never work again as I
can't get it to change source or to a channel which does work.. (I
do have a hack which allows it to work long enough to change
channel).<br>
<br>
Essentially, if Myth changes to a channel which no longer works, it
would be great if instead of dying with "Sync Error" or whatever and
then freezing, we could have, please type alternative channel
number, it would fix 90% of the grumbling.<br>
<br>
I'm guessing this error could be duplicated in most regions with
digital TV by watching a channel, then pulling the antenna/cable
line out of the backend.<br>
<br>
<pre class="moz-signature" cols="72">--
Rob Davis
</pre>
</body>
</html>