[mythtv-users] Video card update fail

Allen Edwards allen.p.edwards at gmail.com
Fri Oct 12 16:12:27 UTC 2018


On Fri, Oct 12, 2018 at 1:36 AM Stephen Worthington <
stephen_agent at jsw.gen.nz> wrote:

> On Thu, 11 Oct 2018 18:46:01 -0700, you wrote:
>
> >Some more response on some of the issues
> >
> >
> >> You can check if the files are the problem by using other video
> >> players, such as mplayer or VLC.  The ultimate test is to export the
> >> file to a known good PC (running Windows?) and play it there.
> >>
> >> The images I posted of the blocks are from VLC and this looks the same
> as
> >it did when played with Mythfrontend.  Clearly in the file.
> >
> >
> >>
> >>
> >> I recommend adding the "-v record" option to the mythbackend command
> >> line to get it to do extra logging about the recording process.  Then
> >> running this command after a recording completes:
> >>
> >> grep -a "overall_score=\"0" /var/log/mythtv/mythbackend.log
> >>
> >> I was unable to figure out how to add a parameter to the launch of
> >mythbackend.  But I see these kind of messages in the log but only when a
> >recording is stopped, not short ones.
>
> Here is a thread from the past that discusses how to turn on extra
> logging:
>
> https://lists.gt.net/mythtv/mythtvnz/617939?page=last
>
> >Here is an example that corresponded to stopping a recording so maybe the
> >logging you wanted is happening by default.
> >
> >Oct 11 18:12:39 NewMyth mythbackend: mythbackend[921]: I TVRecEvent
> >tv_rec.cpp:848 (FinishedRecording) TVRec[1]:
> >FinishedRecording(1021_2018-10-12T01:12:00Z) damaged
> recq:<RecordingQuality
> >overall_score="0.269231" key="1021_2018-10-12T01:12:00Z"
> >countinuity_error_count="2" packet_count="167388">#012    <Gap
> >start="2018-10-12T01:12:00Z" end="2018-10-12T01:12:19Z" duration="19"
> >/>#012</RecordingQuality>
>
> That is a seriously bad recording quality score (0.269231), but I do
> not see why it is so low.  There are only 2 continuity errors flagged,
> and one gap.  At 19 seconds, the gap is pretty big, but you would
> normally expect to have multiple gaps for a score that low.  As it
> happens, that 19 s gap is at the end of the recording, so it is likely
> not a problem as just a few seconds will be missing at the end and you
> have likely recorded sufficiently beyond the actual end of the
> programme to cover that anyway.  I do not have HDHR tuners to know,
> but I suspect that the gap may be an artifact that happens due to how
> MythTV shuts down a recording from those tuners.  You should have a
> look at how often it happens exactly at the end of a recording if you
> stop a recording as you did for this one.  If it always happens, then
> it probably needs to be reported as a bug in mythbackend.
>
> There is known bug that using live TV to watch a programme will always
> produce a message about a big gap as mythbackend is treating live TV
> the same as if it was recording from the EPG data and calculates a gap
> between when you stop live TV and the end of the scheduled time for
> the programme in the EPG.
>
> >None with  a duration="1"
> >
> >Please let me know if I should add the -v record and if so, how do I do
> >that.  I googled without luck.
> >
> >Does this narrow down the problem at all?
>
> I believe all the messages I saw in the log were due to stopping the
recording.  This morning there were artifacts but no messages of type
overall score = 0.

After my wife was done watching, I ran this command "mythbackend
--setverbose record" and started looking at the log while recording some
random show.

What I see is a lot of messages like this
Oct 12 09:09:19 NewMyth mythbackend: mythbackend[867]: W HDHRStreamHandler
recorders/dtvrecorder.cpp:1573 (ProcessAVTSPacket) DTVRec[1]: A/V PID 0x51
discontinuity detected ((6+1)%16!=14)  0.00%

None of the score = 0 type and I have not watched the show to see if there
are issues. Are the messages that say "discontinuity detected" significant?

Allen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20181012/eb13edb5/attachment.html>


More information about the mythtv-users mailing list