<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Apr 13, 2013 at 4:58 PM, Rich West <span dir="ltr"><<a href="mailto:Rich.West@wesmo.com" target="_blank">Rich.West@wesmo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 4/13/2013 3:50 PM, HP-mini wrote:<br>
> This pops up..<br>
> <a href="http://www.mythtv.org/pipermail/mythtv-users/2013-January/345762.html" target="_blank">http://www.mythtv.org/pipermail/mythtv-users/2013-January/345762.html</a><br>
> The advice was:<br>
>>>> There was a significant fix for PVR-XXX cards that went into master<br>
>>>> and 0.26-fixes and 0.25-fixes on or about 29 November last year<br>
>>>> [2012]. Anyone with one of these cards should ensure they are<br>
>>>> running reasonable current code.<br>
<br>
Thanks! Reading that post sounds exactly like what I am going through, so<br>
there might be hope yet...<br>
<br>
All I can think of, though, is "Oh, great.." :(<br>
<br>
I'm running 0.26 via RPMfusion RPMS which are supposedly from April of this<br>
year. I looked at going back to atrpms, but I'm only seeing 0.25.3 built<br>
back in October over there. Gahh.. the though of having to go back to<br>
0.25.3 after having upgraded *everything* in the house (that's four clients)<br>
and the database..<br>
<br>
ugh.. this.. is.. terrible... doesn't look like I have a lot of options..<br>
downloading the 0.26.0 fixes branch and rolling my own RPM is probably the<br>
better method but equally as painful.<br>
<br></blockquote><div> </div></div>My two cents:<br></div><div class="gmail_extra"><br>I'm fairly certain that the newer 0.26.0-7 RPMs on rpmfusion have incorporated the PVR-XXX fix. I was having live TV issues until the most recent RPM build. They have gone away. I have a PVR-500 for my analog channels. I don't have any PVR-150s so I can't give you any more input than that.<br>
<br></div><div class="gmail_extra">Good luck!<br></div><div class="gmail_extra">Jerry<br></div></div>