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

[Ram Ramesh]

On 10/22/20 9:46 PM, Stephen Worthington wrote:
> On Thu, 22 Oct 2020 20:32:05 -0500, you wrote:
>
>> One of my tuner is bad and it produces 0 byte recordings whenever that
>> tuner is used. I am not sure which one it is. How do I find out from the
>> recorded program information? I mean, when I look up previously recorded
>> programs, I do not get input information. Is that kept in the database,
>> if so how do I get it?
> On a recording, push the I key twice and scroll down if necessary to
> find the "Recording Input:" field.  In the database, this is the
> recorded.inputname field.  It does rely on you having set up the names
> for the tuners in mythtv-setup so that you can differentiate them.
>  From SQL a query like this should work:
>
> select chanid,starttime,title,inputname from recorded where filesize=0
> order by starttime desc limit 10;
>
> You can also look in mythbackend.log.  I do this grep command daily to
> check for damaged recordings:
>
> grep -a "overall_score=\"0" /var/log/mythtv/mythbackend.log
>
> However, the log lines that relies on may only be there if you have
> the "-v record" option set on your mythbackend command line.  I always
> have that option set.  Here is the sort of message that grep will
> find:
>
> Oct 17 04:51:47 mypvr mythbackend: mythbackend[3235]: I TVRecEvent
> tv_rec.cpp:826 (FinishedRecording) TVRec[92]:
> FinishedRecording(10007_2020-10-16T15:51:26Z) damaged
> recq:<RecordingQuality overall_score="0"
> key="10007_2020-10-16T15:51:26Z" continuity_error_count="0"
> packet_count="116465">#012    <Gap start="2020-10-16T15:20:00Z"
> end="2020-10-16T15:51:27Z" duration="1887" />#012    <Gap
> start="2020-10-16T15:51:47Z" end="2020-10-16T16:10:00Z"
> duration="1092" />#012</RecordingQuality>
>
> The tuner number is available as the [92] in TVRec[92] in that
> message.  I believe all messages referring to a tuner will have the
> tuner number in that format.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
I added -v record to mythtv-backend service and restarted the service. 
Interestingly I had some hits from your grep command eventhough 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>

> Oct 19 16:22:29 zym mythbackend: mythbackend[2673]: I TVRecEvent 
> tv_rec.cpp:826 (FinishedRecording) TVRec[18]: 
> FinishedRecording(1041_2020-10-19T21:00:00Z) damaged 
> recq:<RecordingQuality overall_score="0" 
> key="1041_2020-10-19T21:00:00Z" continuity_error_count="0" 
> packet_count="9976787">#012    <Gap start="2020-10-19T21:22:27Z" 
> end="2020-10-20T00:15:00Z" duration="10352" />#012</RecordingQuality>

This does not match the 0byte recording as the incident time does not 
match. My 0byte recording program starts at 17:30
(NBC nightly news).

Ramesh