Mailing List Archive

Zero byte recordings on same Recording Inputs
I'm getting quite a lot of zero-byte recordings. I have a HD Homerun
Quattro.

One pattern I can see is that when I press "I" on the recording the failed
ones are always one of two "Recording inputs". The Info says, eg:

Recording input: Input 37
or
Recording input: Input 37

What exactly is a "recording input" and how can I use this info to track
down the rot cause of the zero-byte recordings?

Regards,
Phill
Re: Zero byte recordings on same Recording Inputs [ In reply to ]
On Sun, 21 Jun 2020 21:56:52 +1000, you wrote:

>I'm getting quite a lot of zero-byte recordings. I have a HD Homerun
>Quattro.
>
>One pattern I can see is that when I press "I" on the recording the failed
>ones are always one of two "Recording inputs". The Info says, eg:
>
>Recording input: Input 37
>or
>Recording input: Input 37
>
>What exactly is a "recording input" and how can I use this info to track
>down the rot cause of the zero-byte recordings?
>
>Regards,
>Phill

That should be the cardid field in the cardinput table. It is not a
physical tuner number, but refers to a virtual multirec tuner. Here
is my capturecard table (MythTV v30):

MariaDB [mythconverg]> select
cardid,parentid,videodevice,cardtype,inputname,sourceid,displayname
from capturecard where sourceid!=0 order by cardid;
+--------+----------+--------------------------------------+----------+-----------+----------+-----------------+
| cardid | parentid | videodevice | cardtype | inputname | sourceid | displayname |
+--------+----------+--------------------------------------+----------+-----------+----------+-----------------+
| 1 | 0 | /dev/dvb/adapter0/frontend0 | DVB | DVBInput | 1 | DVB-T 1.1 (1) |
| 2 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVBInput | 1 | DVB-T 1.2 (2) |
| 3 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVBInput | 1 | DVB-T 1.3 (3) |
| 4 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVBInput | 1 | DVB-T 1.4 (4) |
| 5 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVBInput | 1 | DVB-T 1.5 (5) |
| 6 | 0 | /dev/dvb/adapter1/frontend0 | DVB | DVBInput | 1 | DVB-T 2.1 (6) |
| 7 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVBInput | 1 | DVB-T 2.2 (7) |
| 8 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVBInput | 1 | DVB-T 2.3 (8) |
| 9 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVBInput | 1 | DVB-T 2.4 (9) |
| 10 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVBInput | 1 | DVB-T 2.5 (10) |
| 11 | 0 | /dev/dvb/adapter2/frontend0 | DVB | DVBInput | 1 | DVB-T 3.1 (11) |
| 12 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVBInput | 1 | DVB-T 3.2 (12) |
| 13 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVBInput | 1 | DVB-T 3.3 (13) |
| 14 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVBInput | 1 | DVB-T 3.4 (14) |
| 15 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVBInput | 1 | DVB-T 3.5 (15) |
| 16 | 0 | /dev/dvb/adapter3/frontend0 | DVB | DVBInput | 1 | DVB-T 4.1 (16) |
| 17 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVBInput | 1 | DVB-T 4.2 (17) |
| 18 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVBInput | 1 | DVB-T 4.3 (18) |
| 19 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVBInput | 1 | DVB-T 4.4 (19) |
| 20 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVBInput | 1 | DVB-T 4.5 (20) |
| 21 | 0 | /dev/dvb/adapter4/frontend0 | DVB | DVBInput | 1 | DVB-T 5.1 (21) |
| 22 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVBInput | 1 | DVB-T 5.2 (22) |
| 23 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVBInput | 1 | DVB-T 5.3 (23) |
| 24 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVBInput | 1 | DVB-T 5.4 (24) |
| 25 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVBInput | 1 | DVB-T 5.5 (25) |
| 90 | 0 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 1.1 (90) |
| 91 | 90 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 1.2 (91) |
| 92 | 0 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 2.1 (92) |
| 93 | 92 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 2.2 (93) |
| 94 | 0 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 3.1 (94) |
| 95 | 94 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 3.2 (95) |
| 96 | 0 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 4.1 (96) |
| 97 | 96 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 4.2 (97) |
| 98 | 0 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 5.1 (98) |
| 99 | 98 | http://satip.jsw.gen.nz/playlist.m3u | FREEBOX | MPEG2TS | 6 | SAT>IP 5.2 (99) |
+--------+----------+--------------------------------------+----------+-----------+----------+-----------------+
35 rows in set (0.00 sec)

So for example, if I was getting errors saying a cardid number in the
range 11-15, it would be a problem with my DVB-T2 tuner on
/dev/dvb/adapter2. I have manually set up all my displayname values
to show exactly what tuner is involved. The inputname field in the
recorded table stores this information so you can tell which tuner a
recording was done on. And the mythbackend.log file identifies the
tuner on a lot of the messages. If you want more detail in your
mythbackend.log file about the recording process, add "-v record" to
your mythbackend command line. In Ubuntu, you do that in your
/etc/mythtv/additional.args file. This is what I have in mine:

ADDITIONAL_ARGS=-v record,dvbcam

Or you can tell mythbackend to add the verbose record logging while it
is running:

mythbackend --setverbose record

and turn it off again with:

mythbackend --setverbose norecord
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org