<div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Okay, did some tests:<br>
<br>
1) Using the linux hdhomerun_config_gui.<br>
<br>
Everything looks good (just like in Windows). So it appears not to be<br>
a hardware issue, and also appears to be MythTV-specific.<br>
<br>
2) New power wart.<br>
<br>
As I mentioned in my first post, this has already been tried.<br>
<br>
3) Dying NIC<br>
<br>
I did an ifconfig -a and saw 0 dropped packets and 0 errored packets<br>
on all interfaces. Plus, my during successful hdhomerun_config_gui<br>
attempt listed above, I seemed to be getting a pretty acceptable<br>
picture with around 15-20 Mbps data transfer rate.<br>
<br>
4) I tried deleting ALL tuners in MythTV and then readding them<br>
<br>
Oddly, seemed to help briefly, but then returned 15-20 minutes later.<br>
I am not 100% sure, but it may have coincided with a Hauppauge HD-PVR<br>
that was not reconfigured correctly. I tried to replicate the<br>
conditions (removing either my HD-PVR or HVR-850 from MythTV) but the<br>
HDHomerun is still acting up.<br>
<br>
My next theory is to drop all listing sources and tuners and readd<br>
everything again. Maybe it's a tuning frequency table thing?<br>
<br>
5) <a href="http://optimize_mythtvdb.pl" target="_blank">optimize_mythtvdb.pl</a><br>
<br>
Also have run this a few times. My backend has been shutting down due<br>
to overheating lately, even while flagging only a single show . I<br>
suspect the thermal paste needs reapplication. However, I also<br>
suspect the MythTV is trying to commflag the glitchy HDhomerun<br>
recordings and it is consuming alot of CPU trying to process it.<br>
<div><div><br></div></div></blockquote><div><br><div class="HOEnZb"><div class="h5"><br>
</div></div><br>
Since you have proven its not the tuner itself, it could be an IO issue or a playback profile issue. <br>
<br>
Unlike streaming it from hdhomerun_config Mythtv records everything to
disk, even live tv. Perhaps your disk is severely fragmented, you have
some other process consuming IO, etc.<br>
<br>
If everything looks good from a disk perspective, you might play around
with your playback profiles... disable any deinterlacing, enable/disable
vdpau, etc.<br> </div></div></div>