[mythtv-users] Pixelation Cause
Michael Wisniewski
mikewiz38 at gmail.com
Thu Oct 1 00:41:56 UTC 2015
Hi!
I'm running MythTV on a backend, a seperate box for a frontend, and a HDHR
Prime as my tuner. A few months ago, I was getting pixelation due to
network errors. I was able to diagnose this by running a hdhr debug
command to print dots (.) to see if it's a network, transport, or something
else. I figured the NIC on the backend was getting overloaded and dropping
packets. I added a new NIC and this seem to fix the problems for awhile.
Just last night, I started noticing more pixelation. Going through my
recordings, I've seen a good amount of "damaged recq"...
Sep 29 17:57:15 snoopy mythbackend: mythbackend[2261]: I TVRecEvent
tv_rec.cpp:834 (FinishedRecording) TVRec[7]:
FinishedRecording(1212_2015-09-29T22:38:27Z) damaged recq:<RecordingQuality
overall_score="0" key="1212_2015-09-29T22:38:27Z"
countinuity_error_count="4" packet_count="7962930">#012 <Gap
start="2015-09-29T22:00:00Z" end="2015-09-29T22:38:28Z" duration="2308"
/>#012 <Gap start="2015-09-29T22:57:11Z" end="2015-09-29T23:00:00Z"
duration="168" />#012</RecordingQuality>
I was wondering if Myth has an option to determine if it's a transport
problem (coax) or network problem. The other question is why the
"overall_score" shows a 0 when it should probably be something other than
0.
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20150930/0efb9242/attachment.html>
More information about the mythtv-users
mailing list