<br><br><div class="gmail_quote">On Mon, Feb 14, 2011 at 12:05 PM, Dan Armbrust <span dir="ltr"><<a href="mailto:daniel.armbrust.list@gmail.com">daniel.armbrust.list@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">> Let me just say that comparing apples (MythTV 0.23 on distro X, version<br>
> Y, with kernel Z and V4L/DVB subsystem A and drivers B) and oranges<br>
> (MythTV 0.24 on distro X, version Y', with kernel Z' and V4L/DVB<br>
> subsystem A' and drivers B') does not imply that MythTV 0.24 is to<br>
> blame. If you change anything in addition to changing MythTV, ...<br>
<br>
<br>
</div>Well, not to wish bad things to Mike... but I hope that you do start<br>
having this problem. Maybe then we can get some help on fixing it.<br>
<br>
:)<br>
<br>
I don't know where the problem lies, DVB driver changes, or mythTV<br>
changes. But the fact is that mythTV is very unreliable in the<br>
current Mythbuntu packaging. And my configuration worked just fine<br>
until my last update. I have seen the problem on both of my cards, so<br>
I doubt it is a hardware failure of a card. Could be pci bus, I<br>
suppose, but I highly doubt that this many people are encountering<br>
hardware failures at the same time.<br><br></blockquote><div><br></div><div>There is more than circumstantial evidence that V4L/DVB has some pretty substantial issues in current Ubuntu and derivatives. Mike is unlikely to have the issue as he rolls his own distro. While I'm sure there are exceptions, many MANY of the people reporting this issue tend to be using *buntu.</div>
<div><br></div><div>The recorder code in MythTV has not changed in *any* substantial fashion since well before .22. The *only* difference of note in recorder code between .23 and .24 is an update to the HDHR libs, which only affects those devices.</div>
<div><br></div><div>Robert </div></div><br>