[mythtv-users] Capturecard names and multirec tuners

[Stephen Worthington]

On Thu, 4 Apr 2019 17:38:05 -0400, you wrote:

>I have three HDHomeRun (HDHR4-2US) units, with two tuners each, for a
>total of 6 physical tuners. When adding them and creating the inputs
>(allowing a max recordings of 2) I've of course ended up with a total
>of 12 capturecard records:
>
>select cardid, inputname, sourceid, displayname from capturecard;
>+--------+-----------+----------+-------------+
>| cardid | inputname | sourceid | displayname |
>+--------+-----------+----------+-------------+
>|      1 | None      |        1 | HDHR 1      |
>|      2 | None      |        1 | HDHR 1      |
>|      3 | None      |        1 | HDHR 2      |
>|      4 | None      |        1 | HDHR 2      |
>|      5 | None      |        1 | HDHR 3      |
>|      6 | None      |        1 | HDHR 3      |
>|      7 | None      |        1 | HDHR 4      |
>|      8 | None      |        1 | HDHR 4      |
>|      9 | None      |        1 | HDHR 5      |
>|     10 | None      |        1 | HDHR 5      |
>|     11 | None      |        1 | HDHR 6      |
>|     12 | None      |        1 | HDHR 6      |
>+--------+-----------+----------+-------------+
>12 rows in set (0.00 sec)
>
>Unless I'm mistaken, when creating the two rows there per physical
>tuner based on the max recordings, I don't think mythtv-setup gives
>you any means of giving different names to each of the two in a pair.
>I'm fairly sure I've read here on the list at some point that some
>users manually rename these to make things less confusing...for
>example in the above case, HDHR 1-1 and HDHR 1-2 or whatever in place
>of two with HDHR 1.
>
>Has anyone done that? Also, am I better off putting the name in the
>existing displayname, or in the inputname?
>
>I'm also unclear as to exactly what that would affect. I've seen some
>places in the frontend UI (as well as mythweb) that display the
>existing HDHR names above. However there are some places, for example
>the Upcoming Recording screen in the frontend seems to use the ids
>(1-12) and I'm unclear if that would change.
>
>Thanks in advance for any clarification!
>
>Tom

I have never found a way to adjust the names for the multirec tuners
in mythtv-setup.  It is possible it is there now, but I am missing it.
In any case, it was not there when I did it many years ago.  So what I
did was to use SQL to directly edit the displayname fields in the
database.  If you use one of the many GUI tools (eg Heidi SQL for
Windows), it is not too difficult.  Or you can write a simple SQL
script, for example, put this in a file "displaynames.sql":

update capturecard set displayname='HDHR 1.1 (1)' where cardid=1;
update capturecard set displayname='HDHR 1.2 (2)' where cardid=2;
update capturecard set displayname='HDHR 2.1 (3)' where cardid=3;

I leave the rest of the typing for you.  To run that script, do this:

sudo mysql
use mythconverg
source displaynames.sql

I have 5 multirec tuners per physical tuner for my DVB-T tuners, plus
my DVB-S2 tuners accessed via SAT>IP protocol with 2 multirec tuners
per SAT>IP network tuner:

MariaDB [mythconverg]> select cardid, inputname, sourceid, displayname
from capturecard where sourceid=1 or sourceid=6 order by displayname;
+--------+-----------+----------+-----------------+
| cardid | inputname | sourceid | displayname     |
+--------+-----------+----------+-----------------+
|      1 | DVBInput  |        1 | DVB-T 1.1 (1)   |
|      2 | DVBInput  |        1 | DVB-T 1.2 (2)   |
|      3 | DVBInput  |        1 | DVB-T 1.3 (3)   |
|      4 | DVBInput  |        1 | DVB-T 1.4 (4)   |
|      5 | DVBInput  |        1 | DVB-T 1.5 (5)   |
|      6 | DVBInput  |        1 | DVB-T 2.1 (6)   |
|      7 | DVBInput  |        1 | DVB-T 2.2 (7)   |
|      8 | DVBInput  |        1 | DVB-T 2.3 (8)   |
|      9 | DVBInput  |        1 | DVB-T 2.4 (9)   |
|     10 | DVBInput  |        1 | DVB-T 2.5 (10)  |
|     11 | DVBInput  |        1 | DVB-T 3.1 (11)  |
|     12 | DVBInput  |        1 | DVB-T 3.2 (12)  |
|     13 | DVBInput  |        1 | DVB-T 3.3 (13)  |
|     14 | DVBInput  |        1 | DVB-T 3.4 (14)  |
|     15 | DVBInput  |        1 | DVB-T 3.5 (15)  |
|     16 | DVBInput  |        1 | DVB-T 4.1 (16)  |
|     17 | DVBInput  |        1 | DVB-T 4.2 (17)  |
|     18 | DVBInput  |        1 | DVB-T 4.3 (18)  |
|     19 | DVBInput  |        1 | DVB-T 4.4 (19)  |
|     20 | DVBInput  |        1 | DVB-T 4.5 (20)  |
|     21 | DVBInput  |        1 | DVB-T 5.1 (21)  |
|     22 | DVBInput  |        1 | DVB-T 5.2 (22)  |
|     23 | DVBInput  |        1 | DVB-T 5.3 (23)  |
|     24 | DVBInput  |        1 | DVB-T 5.4 (24)  |
|     25 | DVBInput  |        1 | DVB-T 5.5 (25)  |
|     90 | MPEG2TS   |        6 | SAT>IP 1.1 (90) |
|     91 | MPEG2TS   |        6 | SAT>IP 1.2 (91) |
|     92 | MPEG2TS   |        6 | SAT>IP 2.1 (92) |
|     93 | MPEG2TS   |        6 | SAT>IP 2.2 (93) |
|     94 | MPEG2TS   |        6 | SAT>IP 3.1 (94) |
|     95 | MPEG2TS   |        6 | SAT>IP 3.2 (95) |
|     96 | MPEG2TS   |        6 | SAT>IP 4.1 (96) |
|     97 | MPEG2TS   |        6 | SAT>IP 4.2 (97) |
|     98 | MPEG2TS   |        6 | SAT>IP 5.1 (98) |
|     99 | MPEG2TS   |        6 | SAT>IP 5.2 (99) |
+--------+-----------+----------+-----------------+
35 rows in set (0.01 sec)