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

[Ram Ramesh]

On 10/24/20 2:24 PM, Klaas de Waal wrote:
> Hi Ram,
>
> To figure out which tuner did which recording you can do the following:
>
> 1. Get a list of the tuners (capture cards) with the following SQL 
> command:
> MariaDB [mythconverg]> select 
> cardid,parentid,videodevice,displayname,sourceid from capturecard;
> +--------+----------+-----------------------------+-------------+----------+
> | cardid | parentid | videodevice                 | displayname | 
> sourceid |
> +--------+----------+-----------------------------+-------------+----------+
> |      1 |        0 | /dev/dvb/adapter0/frontend0 | K0  |        1 |
> |      2 |        0 | /dev/dvb/adapter1/frontend0 | K1  |        1 |
> |      3 |        0 | /dev/dvb/adapter2/frontend0 | K2  |        1 |
> |      4 |        0 | 141013C6                    | H0  |        4 |
> |      5 |        0 | 141013C6                    | H1  |        4 |
> |      6 |        0 | 141013C6                    | H2  |        4 |
> |     16 |        1 | /dev/dvb/adapter0/frontend0 | K0  |        1 |
> |     17 |        2 | /dev/dvb/adapter1/frontend0 | K1  |        1 |
> |     18 |        3 | /dev/dvb/adapter2/frontend0 | K2  |        1 |
> |     19 |        4 | 141013C6                    | H0  |        4 |
> |     20 |        5 | 141013C6                    | H1  |        4 |
> |     21 |        6 | 141013C6                    | H2  |        4 |
> |     22 |        4 | 141013C6                    | H0  |        4 |
> |     23 |        5 | 141013C6                    | H1  |        4 |
> |     24 |        0 | 1410F45C                    | HDHR  |        4 |
> |     25 |        2 | /dev/dvb/adapter1/frontend0 | K1  |        1 |
> |     26 |        5 | 141013C6                    | H1  |        4 |
> |     27 |        5 | 141013C6                    | H1  |        4 |
> |     28 |        1 | /dev/dvb/adapter0/frontend0 | K0  |        1 |
> +--------+----------+-----------------------------+-------------+----------+
>
> The third column identifies the HDHomeRun device.
> The first column identifies the tuner (capture card) and this number 
> is used in the mythbackend logs.
>
> 2. Get the relevant lines from the mythbackend log, eg.:
>
> > grep continuity_error_count mythbackend.log
>
> This will give output like this:
> 2020-10-24 13:05:00.041774 I  TVRec[16]: 
> FinishedRecording(10411_2020-10-24T09:42:00Z) good 
> recq:<RecordingQuality overall_score="1" 
> key="10411_2020-10-24T09:42:00Z" continuity_error_count="0" 
> packet_count="36666066" />
> 2020-10-24 13:25:00.466228 I  TVRec[4]: 
> FinishedRecording(119043_2020-10-24T09:52:00Z) good 
> recq:<RecordingQuality overall_score="1" 
> key="119043_2020-10-24T09:52:00Z" continuity_error_count="0" 
> packet_count="44032547" />
> 2020-10-24 13:30:01.214219 I  TVRec[1]: 
> FinishedRecording(10411_2020-10-24T10:42:00Z) good 
> recq:<RecordingQuality overall_score="1" 
> key="10411_2020-10-24T10:42:00Z" continuity_error_count="0" 
> packet_count="21208761" />
> 2020-10-24 14:20:00.678063 I  TVRec[16]: 
> FinishedRecording(10411_2020-10-24T11:07:00Z) good 
> recq:<RecordingQuality overall_score="1" 
> key="10411_2020-10-24T11:07:00Z" continuity_error_count="0" 
> packet_count="32253338" />
>
> So for example, the recording with "TVRec[4]"  has been recorded on 
> capture card 4 and this is then HDHomeRun 141013C6.
>
> Recordings with continuity_error_count=0 and with a huge packet_count 
> are usually OK.
>
> This way you can easily identify which HDHomeRun does not work properly.
>
>
> About how to fix this, with old HDHomeRun devices it is usually the 
> power supply that gives problems.
> In your case, with two old HDHomeRun devices I would replace the power 
> supply of both.
> Updating the firmware is also a good idea but only after you have 
> replaced the power supply.
>
> Hope this helps,
> Klaas.
>
>
> _______________________________________________
> 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 did more experiments and feel that it is not the tuner, but a TV 
station. I got this impression because of the following. When I begin 
the live tv session, it goes to chan 2_1 which has a very poor signal. 
However, changing channel to 5_1 (the channel that produces 0-byte 
recording) gets me going and I see good reception.  Now if I switch to 
another input, I see that the switch first gets me to 2_1 on the new 
tuner and then switches to 5_1 (this is based on call signs shown on the 
tv).
One of the unit (older) is able to recover from failing 2_1 and go to 
5_1 in a reasonable time. However the failing tuner takes a lot longer 
as it may be trying harder (newer tuner) and this causes backend to give 
up and create a 0-byte recording when this tuner is used to tune a good 
channel.

Does this make sense? If I want to experiment further, how do I delete 
this channel from the tuner so that it does not default to this channel 
and then switch? Is there a backend setup value to set the starting 
channel to tune?

Ramesh