[mythtv-users] How to find the input used in a recording?

[Stephen Worthington]

On Fri, 23 Oct 2020 15:25:59 -0500, you wrote:

>On 10/23/20 2:53 PM, Ram Ramesh wrote:
>...
>> ... Interestingly I had some hits from your grep command even though I did not
>> have -v record switch when the error message was generated. Here is what I got:
>
>>> Oct 19 16:00:00 zym mythbackend: mythbackend[2673]: I HDHRStreamHandler tv_rec.cpp:826 (FinishedRecording) TVRec[18]:
>>> FinishedRecording(1041_2020-10-19T20:57:04Z) damaged recq:<RecordingQuality overall_score="0" key="1041_2020-10-19T20:57:04Z"
>>> continuity_error_count="0" packet_count="1388107">#012    <Gap start="2020-10-19T20:30:00Z" end="2020-10-19T20:57:04Z" duration="1624"
>>> />#012</RecordingQuality>
>...
>
>Answering the "Interesting" comment only:
>
>The log message is considered VB_GENERAL *if* the recording is thought to be
>damaged. That's based on the value of the MinimumRecordingQuality setting.
>
>With -v record (VB_RECORD,), then undamaged recordings will create the log
>message, but will say "good" where the above says "damaged" (assuming any
>recording quality data was collected.)
>
>The setting isn't changeable via the GUI and defaults to 95%.
>
>https://code.mythtv.org/cgit/mythtv/tree/mythtv/libs/libmythtv/tv_rec.cpp#n825

Thanks, it is useful to know exactly how that works.

I have found that certain sorts of damage that do not result in the
decision that the recording is to be marked as damaged are still a
problem, so I have -v record on so that there will be messages about
the damage, and I can manually schedule re-recording where possible.
One common sort of such damage I do get is where a recording has a
delay in starting, so that I lose a minute or so at the beginning of a
recording.  That happens when I have a lot of recordings starting
around the same time, and I am suspecting a bug of some sort as when
it happens, the frontend is unable to do anything either.  If a
recording is already playing, it will keep playing, but attempting to
skip forwards over an ad break will not work until the recordings that
are starting have actually started.