<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Sat, Oct 13, 2018 at 8:43 AM John Pilkington <<a href="mailto:johnpilk222@gmail.com">johnpilk222@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 13/10/18 15:50, Allen Edwards wrote:<br>
> <br>
> <br>
> On Sat, Oct 13, 2018 at 7:35 AM Allen Edwards <<a href="mailto:allen.p.edwards@gmail.com" target="_blank">allen.p.edwards@gmail.com</a> <br>
> <mailto:<a href="mailto:allen.p.edwards@gmail.com" target="_blank">allen.p.edwards@gmail.com</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On Sat, Oct 13, 2018 at 2:31 AM Stephen Worthington<br>
> <<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a> <mailto:<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a>>> wrote:<br>
> <br>
> On Fri, 12 Oct 2018 09:12:27 -0700, you wrote:<br>
> <br>
> <br>
> >After my wife was done watching, I ran this command "mythbackend<br>
> >--setverbose record" and started looking at the log while<br>
> recording some<br>
> >random show.<br>
> ><br>
> >What I see is a lot of messages like this<br>
> >Oct 12 09:09:19 NewMyth mythbackend: mythbackend[867]: W<br>
> HDHRStreamHandler<br>
> >recorders/dtvrecorder.cpp:1573 (ProcessAVTSPacket) DTVRec[1]:<br>
> A/V PID 0x51<br>
> >discontinuity detected ((6+1)%16!=14) 0.00%<br>
> ><br>
> >None of the score = 0 type and I have not watched the show to<br>
> see if there<br>
> >are issues. Are the messages that say "discontinuity detected"<br>
> significant?<br>
> <br>
> Unfortunately, those discontinuity messages do not seem to be<br>
> necessarily significant. I do get them when the recording is OK - I<br>
> think they can happen when ad breaks get inserted and the video<br>
> stream<br>
> is disrupted by that. But I only seem to get them from my DVB-S<br>
> tuners via minisatip, so I have not ruled out a bug in minisatip<br>
> from<br>
> being the cause. If there are lots of them, that is likely to<br>
> indicate a problem, but an occasional burst of just one or two at a<br>
> time (like I get) does not seem to indicate a real problem. As<br>
> best I<br>
> can determine, the ones I get when the recording does have a problem<br>
> will have a final calculated % value that is non-zero. The ones<br>
> that<br>
> I get that do not correspond to a bad recording all seem to have a<br>
> final calculated value of 0.0 % or a very small number (<<br>
> 0.00001 %).<br>
> _______________________________________________<br>
> <br>
> <br>
> I see lots of the the discontinuity detected messages but looking at<br>
> the time stamps, they are in groups of one or two.<br>
> Taking yesterday as a test day, I saw glitches in programs on both<br>
> HDHomerun units, on different channels, one UHF and one VHF, and I<br>
> saw no overall_score="0". That said, I erased the show from the<br>
> second HDHomerun so I can't prove it actually recorded on that unit<br>
> so I need to repeat that.<br>
> <br>
> I will not rule out a signal strength problem but I would be very<br>
> surprised if the VHF channel had a problem. The UHF channel is<br>
> typically more difficult to get. I would also not expect<br>
> interference to hit both channels.<br>
> <br>
> The only thing I can think to do now, other than repeating the<br>
> HDHomerun experiment, is to watch a show live on the TV and then<br>
> watch the recorded version. Anyone have other ideas?<br>
> <br>
> Allen<br>
> <br>
> <br>
> I should have added that the "discontinuity detected" messages are <br>
> coming at an average rate of 11 per minute. Might be scene changes in <br>
> the source as this is a news show and they change scenes at about that rate.<br>
> <br>
> Allen<br>
> <br>
<br>
I haven't gone back through this thread for all the details, but ISTR <br>
that, unusually in the US, ypu are using EIT program info. I found, <br>
quite recently, that I got defective recordings, with packets dropped or <br>
out of order, when doing too much 'active' scanning. Look at your <br>
backend settings. Both these threads are long and not conclusive<br>
<br>
<a href="https://lists.gt.net/mythtv/dev/618967?search_string=EIT%20activity;#618967" rel="noreferrer" target="_blank">https://lists.gt.net/mythtv/dev/618967?search_string=EIT%20activity;#618967</a><br>
<br>
and possibly also <a href="https://code.mythtv.org/trac/ticket/13066" rel="noreferrer" target="_blank">https://code.mythtv.org/trac/ticket/13066</a><br>
<br>
John<br></blockquote><div><br></div><div>I do believe that I have EIT disabled as when it was enabled it overwrote my Schedules Direct listings so I only got listings for a day or so. Absolutely Mythweb shows all channels have useonairguide unchecked.</div><div><br></div><div>The last thread you linked is interesting in that the poster had the same problem I do and proved it was not in the OTA source. Then the list owner closed it as not a MythTV problem. Final comment that it might be EIT but no resolution. Anyway, I don't think I have EIT in use. I will check the backend setup to make sure it is still unchecked there.</div><div><br></div><div>Allen </div></div></div>