<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:14pt"><div id="yiv7546100554"><div><div style="color: rgb(0, 0, 0); font-family: 'times new roman', 'new york', times, serif; font-size: 14pt; background-color: rgb(255, 255, 255);"><div id="yiv7546100554yui_3_16_0_6_1404712155067_4">Hi Rob,</div><div id="yiv7546100554yui_3_16_0_6_1404712155067_4"><br></div><div id="yiv7546100554yui_3_16_0_6_1404712155067_4">What is the location of your setup? I am in Wellington, direct line of sight with Mt. KauKau aerial transmitters, running a 6-way passive splitter to 2 x Freeview TVs & a HDHomeRun dual tuner (DVB-T) and have experienced similar problems on both TV's and Myth recordings and live TV on certain freeview channels (but never TV-One). I put it down to maybe some outside aerial/cable moisture ingress issues but haven't got around to checking that out fully. </div><div
id="yiv7546100554yui_3_16_0_6_1404712155067_4"><br></div><div id="yiv7546100554yui_3_16_0_6_1404712155067_4">I did notice that it was particularly a problem on bad weather days. </div><div id="yiv7546100554yui_3_16_0_6_1404712155067_4"><br></div><div id="yiv7546100554yui_3_16_0_6_1404712155067_4">However it could well be an issue at Mt. KauKau site.</div><div id="yiv7546100554yui_3_16_0_6_1404712155067_4"><br></div><div id="yiv7546100554yui_3_16_0_6_1404712155067_4">Regards,</div><div id="yiv7546100554yui_3_16_0_6_1404712155067_4">David. </div> <div class="yiv7546100554qtdSeparateBR"><br clear="none"><br clear="none"></div><div class="yiv7546100554yqt1517914360" id="yiv7546100554yqt82911"><div class="yiv7546100554yahoo_quoted" id="yiv7546100554yui_3_16_0_6_1404712155067_7" style="display: block;"> <div class="yiv7546100554yui_3_16_0_1_1404712155067_9017" id="yiv7546100554yui_3_16_0_1_1404712155067_9063" style="font-family: 'times new roman',
'new york', times, serif; font-size: 14pt;"> <div class="yiv7546100554yui_3_16_0_1_1404712155067_9018" id="yiv7546100554yui_3_16_0_1_1404712155067_9062" style="font-family: 'times new roman', 'new york', times, serif; font-size: 12pt;"> <div dir="ltr" id="yiv7546100554yui_3_16_0_1_1404712155067_9064"> <font size="2" face="Arial"> On Sunday, 6 July 2014 6:14 PM, Nick Rout <nick.rout@gmail.com> wrote:<br clear="none"> </font> </div> <br clear="none"><br clear="none"> <div class="yiv7546100554y_msg_container" id="yiv7546100554yui_3_16_0_1_1404712155067_9061">On Sun, Jul 6, 2014 at 6:08 PM, Stephen Worthington<br clear="none"><<a rel="nofollow" shape="rect" ymailto="mailto:stephen_agent@jsw.gen.nz" target="_blank" href="mailto:stephen_agent@jsw.gen.nz">stephen_agent@jsw.gen.nz</a>> wrote:<br clear="none">> On Sun, 06 Jul 2014 12:20:39 +1200, you wrote:<br clear="none">><br clear="none">>>Hi All,<br clear="none">>><br
clear="none">>>I've been running my Myth setup for nearly 3 years pretty successfully,<br clear="none">>>but recently I've been running into a lot of problems with failed<br clear="none">>>recordings. This started out with almost all recordings on the<br clear="none">>>MediaWorks multiplex failing, but it has since started occasionally on<br clear="none">>>the other multiplexes too. From looking at the logs this looks like the<br clear="none">>>adapter is unable to tune and eventually gives up. This appears to be<br clear="none">>>more likely when another recording is already in progress. I've done a<br clear="none">>>couple of retunes whilst this has been going on, but they didn't help.<br clear="none">>><br clear="none">>>In the last week we have also started to get a lot of interferance on<br clear="none">>>some
recordings. Last night this produced a recording which was<br clear="none">>>completely unwatchable due to picture degradation and sound blips.<br clear="none">>><br clear="none">>>Looking in the log for this recording came up with something<br clear="none">>>interesting:<br clear="none">>><br clear="none">>>Jul 5 19:25:05 laforge mythbackend[2881]: W DVBRead<br clear="none">>>dtvrecorder.cpp:1290 (ProcessTSPacket) DTVRec(7): PID 0x3ec<br clear="none">>>discontinuity detected (( 5+1)%16!= 7) 0.57985%<br clear="none">>><br clear="none">>>This message is repeated 42677 times for this recording! Which fits with<br clear="none">>>the almost constant picture issues. Aside from that myth completed the<br clear="none">>>recording 'successfully', athough another recording which started later<br clear="none">>>failed.<br clear="none">>><br clear="none">>>Since
the hardware and software didn't change since this was working,<br clear="none">>>I'm wondering if this is caused by a slow failure of the TV tuner card,<br clear="none">>>or some other part of the receiver
setup (which consists of maybe 10m of<br clear="none">>>cable to the antenna and a Kingray amplifier [with phantom power<br clear="none">>>injected from ground level]). The other option is some real interferance<br clear="none">>>- there is a ham radio operator in the next street who I've always<br clear="none">>>suspected.<br clear="none">>><br clear="none">>>The relevant details of my system are as follows:<br clear="none">>><br clear="none">>>OS: Debian Wheezy with deb-multimedia packages for myth, etc.<br clear="none">>>Tuner Card: Hauppauge HVR2200<br clear="none">>>MythTV Version: 0.26.1+fixes20140227-dmo1<br clear="none">>><br clear="none">>>I've uploaded the log from last nights recordings at<br clear="none">>><a rel="nofollow" shape="rect" target="_blank"
href="http://webworxshop.com/~robert/logs/mythbackend.log.20140705.">http://webworxshop.com/~robert/logs/mythbackend.log.20140705. </a>The<br clear="none">>>recording 'Midsomer Murders' was the corrupted one, whilst the recording<br clear="none">>>'Knowing' failed to tune.<br clear="none">>><br clear="none">>>I'm going to try and do
some investigation with tzap later today and I'll<br clear="none">>>post the results here.<br clear="none">>><br clear="none">>>Please let me know what you guys think.<br clear="none">>><br clear="none">>>Thanks in advance,<br clear="none">>><br clear="none">>>Rob Connolly<br clear="none">><br clear="none">> When one mux is giving problems, or gives more problems than the<br clear="none">> others, that usually indicates reception problems, rather than tuner<br clear="none">> problems (unless, like me, you have muxes forced to use specific<br clear="none">> tuners). Usually one mux has the worst signal, either the lowest<br clear="none">> power transmitter, or the highest frequency. So that mux is the one<br clear="none">> that gives problems first.<br clear="none">><br clear="none">> I would suspect the cabling first. Are you using good shielded aerial<br
clear="none">> cable (RG6 I think is what is best), and F-connectors everywhere you<br clear="none">> can? Is there somewhere that another power or signal cable has been<br clear="none">> installed or moved to that runs parallel near your
aerial cable? Has<br clear="none">> a cable been bumped and pulled out partially anywhere (eg while<br clear="none">> vacuuming)?<br clear="none">><br clear="none">> Check that the power supply to your aerial amplifier is still working<br clear="none">> - they are usually just wall warts and hence not usually the most<br clear="none">> reliable of things. Visually check that the aerial itself is OK and<br clear="none">> still pointing in the correct direction.<br clear="none">><br clear="none">> Try using LiveTV and see what the on-screen signal level and s/n<br clear="none">> values show, or use dvbtune. This is the command line I use for<br clear="none">> dvbtune:<br clear="none">><br clear="none">> dvbtune -f $a -qam 64 -gi 16 -cr 3_4 -bw 8 -tm 8 -m -c $ADAPTER<br clear="none">><br clear="none">> where $a is the frequency in kHz (530000, 562000, 578000 or 594000 for<br
clear="none">> Wharite), and $ADAPTER is the adapter number, which is 0 or 1 in your<br clear="none">> case.<br clear="none">><br clear="none">> Do you have another DVB-T tuner you could plug in for comparison (eg<br clear="none">> USB one on your
laptop)?<br clear="none"><br clear="none"><br clear="none">All good points, the other one is that your antenna could have<br clear="none">shifted. High winds lately? Earthquakes? Similarly a good storm could<br clear="none">get H20 into your cabling.<br clear="none"><br clear="none">><br clear="none">> _______________________________________________<br clear="none">> mythtvnz mailing list<br clear="none">> <a rel="nofollow" shape="rect" ymailto="mailto:mythtvnz@lists.linuxnut.co.nz" target="_blank" href="mailto:mythtvnz@lists.linuxnut.co.nz">mythtvnz@lists.linuxnut.co.nz</a><br clear="none">> <a rel="nofollow" shape="rect" target="_blank" href="http://lists.ourshack.com/mailman/listinfo/mythtvnz">http://lists.ourshack.com/mailman/listinfo/mythtvnz</a><br clear="none">> Archives <a rel="nofollow" shape="rect" target="_blank"
href="http://www.gossamer-threads.com/lists/mythtv/mythtvnz/">http://www.gossamer-threads.com/lists/mythtv/mythtvnz/</a><br clear="none"><br clear="none">_______________________________________________<br clear="none">mythtvnz mailing list<br clear="none"><a rel="nofollow" shape="rect" ymailto="mailto:mythtvnz@lists.linuxnut.co.nz" target="_blank" href="mailto:mythtvnz@lists.linuxnut.co.nz">mythtvnz@lists.linuxnut.co.nz</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="http://lists.ourshack.com/mailman/listinfo/mythtvnz">http://lists.ourshack.com/mailman/listinfo/mythtvnz</a><br clear="none">Archives <a rel="nofollow" shape="rect" target="_blank" href="http://www.gossamer-threads.com/lists/mythtv/mythtvnz/">http://www.gossamer-threads.com/lists/mythtv/mythtvnz/</a><br clear="none"><br clear="none"><br clear="none"></div> </div> </div> </div></div> </div></div></div></div></body></html>