Mailing List Archive

cannot schedule both tuners on AVerMedia Twinstar
I had this USB tuner for a long time but decided to use it again now. Plugged it in and configured
the capture-card and input-connection. All tuners (there are 5 others) show up and can be tuned into in WatchTV.

The wiki says "unsupported" but it was last updated in 2014 so probably out of date?

The problem is with scheduling. I have the two Twinstar tuners set to almost the same priority.
myth refuses to use both, so (depending on the order I set) it will allow scheduling from one
and will not schedule on the other at all. I can change the priority to have it pick the other
and it then will never use the first.

I am sure that this device has two independent tuners. It shows up as two devices in /dev/dvb/.
It shows up as two in mythtv status (actually each tuner shows up as 4 by reclimit).

Looking at mythtv coming up I notice:

CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[29]: Set delivery system: DVB-T
CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[33]: Set delivery system: DVB-T
CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[37]: Set delivery system: DVB-T
CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[41]: Set delivery system: DVB-T
CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[45]: Set delivery system: DVB-T
CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[50]: Set delivery system: DVB-T
CoreContext recorders/dvbchannel.cpp:699 (Tune) - DVBChan[50](/dev/dvb/adapter-OPEN-ELEC-6/frontend0): Next tuning after less than 1000ms. Delaying by 1000ms
CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[51]: Set delivery system: DVB-T

The first cards (29-45) are the "older" USB tuners, 50 is the TwinStar does not schedule and
51 is the other tuner on the Twinstar that does schedule.

I looked over my settings and they look good to me.
I do notice One unusual message (see below). Is it related?

Bootup messages that may be related:

usb 1-4.4.2: New USB device found, idVendor=07ca, idProduct=0825, bcdDevice= 2.01
usb 1-4.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-4.4.2: Product: A825
usb 1-4.4.2: Manufacturer: AVerMedia TECHNOLOGIES, Inc.
usb 1-4.4.2: SerialNumber: 0000000000000

dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
usb 1-4.4.2: dvb_usb_v2: found a 'AVerMedia Twinstar (A825)' in warm state
dvb_usb_af9035 1-4.4.2:1.0: Device may have issues with I2C read operations. Enabling fix. <<<<<<<<<<
usb 1-4.4.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
usb 1-4.4.2: media controller created
dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))

$ uname -a
Linux e7.eyal.emu.id.au 5.13.5-200.fc34.x86_64 #1 SMP Sun Jul 25 16:19:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

$ mythbackend --version
[see attached file as requested]

TIA

--
Eyal Lebedinsky (eyal@eyal.emu.id.au)
Re: cannot schedule both tuners on AVerMedia Twinstar [ In reply to ]
On Sat, 31 Jul 2021 11:29:56 +1000, you wrote:

>I had this USB tuner for a long time but decided to use it again now. Plugged it in and configured
>the capture-card and input-connection. All tuners (there are 5 others) show up and can be tuned into in WatchTV.
>
>The wiki says "unsupported" but it was last updated in 2014 so probably out of date?
>
>The problem is with scheduling. I have the two Twinstar tuners set to almost the same priority.
>myth refuses to use both, so (depending on the order I set) it will allow scheduling from one
>and will not schedule on the other at all. I can change the priority to have it pick the other
>and it then will never use the first.
>
>I am sure that this device has two independent tuners. It shows up as two devices in /dev/dvb/.
>It shows up as two in mythtv status (actually each tuner shows up as 4 by reclimit).
>
>Looking at mythtv coming up I notice:
>
>CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[29]: Set delivery system: DVB-T
>CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[33]: Set delivery system: DVB-T
>CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[37]: Set delivery system: DVB-T
>CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[41]: Set delivery system: DVB-T
>CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[45]: Set delivery system: DVB-T
>CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[50]: Set delivery system: DVB-T
>CoreContext recorders/dvbchannel.cpp:699 (Tune) - DVBChan[50](/dev/dvb/adapter-OPEN-ELEC-6/frontend0): Next tuning after less than 1000ms. Delaying by 1000ms
>CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[51]: Set delivery system: DVB-T
>
>The first cards (29-45) are the "older" USB tuners, 50 is the TwinStar does not schedule and
>51 is the other tuner on the Twinstar that does schedule.
>
>I looked over my settings and they look good to me.
>I do notice One unusual message (see below). Is it related?
>
>Bootup messages that may be related:
>
>usb 1-4.4.2: New USB device found, idVendor=07ca, idProduct=0825, bcdDevice= 2.01
>usb 1-4.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>usb 1-4.4.2: Product: A825
>usb 1-4.4.2: Manufacturer: AVerMedia TECHNOLOGIES, Inc.
>usb 1-4.4.2: SerialNumber: 0000000000000
>
>dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
>usb 1-4.4.2: dvb_usb_v2: found a 'AVerMedia Twinstar (A825)' in warm state
>dvb_usb_af9035 1-4.4.2:1.0: Device may have issues with I2C read operations. Enabling fix. <<<<<<<<<<
>usb 1-4.4.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
>dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>usb 1-4.4.2: media controller created
>dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>
>$ uname -a
>Linux e7.eyal.emu.id.au 5.13.5-200.fc34.x86_64 #1 SMP Sun Jul 25 16:19:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>
>$ mythbackend --version
>[see attached file as requested]
>
>TIA

I have a Kworld DVB-T 399UR dual DVB-T USB tuner, and on it both
tuners work, but due to some common hardware that is used by both
tuners, you can not use both tuners at once in Linux. It works fine
in Windows, which is where I am now using it.

With your tuners, have you tried setting up manual recordings with the
tuner specified manually? In LiveTV, what happens if you manually
switch to the problem tuners?
_______________________________________________
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
Re: cannot schedule both tuners on AVerMedia Twinstar [ In reply to ]
On 31/07/2021 13.25, Stephen Worthington wrote:
> On Sat, 31 Jul 2021 11:29:56 +1000, you wrote:
>
>> I had this USB tuner for a long time but decided to use it again now. Plugged it in and configured
>> the capture-card and input-connection. All tuners (there are 5 others) show up and can be tuned into in WatchTV.
>>
>> The wiki says "unsupported" but it was last updated in 2014 so probably out of date?
>>
>> The problem is with scheduling. I have the two Twinstar tuners set to almost the same priority.
>> myth refuses to use both, so (depending on the order I set) it will allow scheduling from one
>> and will not schedule on the other at all. I can change the priority to have it pick the other
>> and it then will never use the first.
>>
>> I am sure that this device has two independent tuners. It shows up as two devices in /dev/dvb/.
>> It shows up as two in mythtv status (actually each tuner shows up as 4 by reclimit).
>>
>> Looking at mythtv coming up I notice:
>>
>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[29]: Set delivery system: DVB-T
>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[33]: Set delivery system: DVB-T
>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[37]: Set delivery system: DVB-T
>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[41]: Set delivery system: DVB-T
>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[45]: Set delivery system: DVB-T
>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[50]: Set delivery system: DVB-T
>> CoreContext recorders/dvbchannel.cpp:699 (Tune) - DVBChan[50](/dev/dvb/adapter-OPEN-ELEC-6/frontend0): Next tuning after less than 1000ms. Delaying by 1000ms
>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[51]: Set delivery system: DVB-T
>>
>> The first cards (29-45) are the "older" USB tuners, 50 is the TwinStar does not schedule and
>> 51 is the other tuner on the Twinstar that does schedule.
>>
>> I looked over my settings and they look good to me.
>> I do notice One unusual message (see below). Is it related?
>>
>> Bootup messages that may be related:
>>
>> usb 1-4.4.2: New USB device found, idVendor=07ca, idProduct=0825, bcdDevice= 2.01
>> usb 1-4.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> usb 1-4.4.2: Product: A825
>> usb 1-4.4.2: Manufacturer: AVerMedia TECHNOLOGIES, Inc.
>> usb 1-4.4.2: SerialNumber: 0000000000000
>>
>> dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
>> usb 1-4.4.2: dvb_usb_v2: found a 'AVerMedia Twinstar (A825)' in warm state
>> dvb_usb_af9035 1-4.4.2:1.0: Device may have issues with I2C read operations. Enabling fix. <<<<<<<<<<
>> usb 1-4.4.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
>> dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>> usb 1-4.4.2: media controller created
>> dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>>
>> $ uname -a
>> Linux e7.eyal.emu.id.au 5.13.5-200.fc34.x86_64 #1 SMP Sun Jul 25 16:19:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>>
>> $ mythbackend --version
>> [see attached file as requested]
>>
>> TIA
>
> I have a Kworld DVB-T 399UR dual DVB-T USB tuner, and on it both
> tuners work, but due to some common hardware that is used by both
> tuners, you can not use both tuners at once in Linux. It works fine
> in Windows, which is where I am now using it.
>
> With your tuners, have you tried setting up manual recordings with the
> tuner specified manually?

Yes, and it always uses a different tuner rather than the preferred one.

> In LiveTV, what happens if you manually switch to the problem tuners?

No go. Changing to the twin tuner automatically switches to the same channel rather than the
one I selected originally.

Tuners 6 and 7 are the ones from the Twinstar.

Tune to channel 34 on tuner 7 (a scheduled recording). OK.
Tune to channel 34 on tuner 6 (live TV). OK.
Change channel on tuner 6 to 30. On same multiplex. OK
Change channel on tuner 6 to 53. A different multiplex. Myth changed to tuner 4.
Change source back to tuner 6. Myth changed from channel 53 to 30.

Myth seems to somehow know to not tune tuners 6 and 7 to different multiplexes.
How is this done?

--
Eyal Lebedinsky (eyal@eyal.emu.id.au)
_______________________________________________
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
Re: cannot schedule both tuners on AVerMedia Twinstar [ In reply to ]
On Sat, 31 Jul 2021 20:00:37 +1000, you wrote:

>On 31/07/2021 13.25, Stephen Worthington wrote:
>> On Sat, 31 Jul 2021 11:29:56 +1000, you wrote:
>>
>>> I had this USB tuner for a long time but decided to use it again now. Plugged it in and configured
>>> the capture-card and input-connection. All tuners (there are 5 others) show up and can be tuned into in WatchTV.
>>>
>>> The wiki says "unsupported" but it was last updated in 2014 so probably out of date?
>>>
>>> The problem is with scheduling. I have the two Twinstar tuners set to almost the same priority.
>>> myth refuses to use both, so (depending on the order I set) it will allow scheduling from one
>>> and will not schedule on the other at all. I can change the priority to have it pick the other
>>> and it then will never use the first.
>>>
>>> I am sure that this device has two independent tuners. It shows up as two devices in /dev/dvb/.
>>> It shows up as two in mythtv status (actually each tuner shows up as 4 by reclimit).
>>>
>>> Looking at mythtv coming up I notice:
>>>
>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[29]: Set delivery system: DVB-T
>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[33]: Set delivery system: DVB-T
>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[37]: Set delivery system: DVB-T
>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[41]: Set delivery system: DVB-T
>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[45]: Set delivery system: DVB-T
>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[50]: Set delivery system: DVB-T
>>> CoreContext recorders/dvbchannel.cpp:699 (Tune) - DVBChan[50](/dev/dvb/adapter-OPEN-ELEC-6/frontend0): Next tuning after less than 1000ms. Delaying by 1000ms
>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[51]: Set delivery system: DVB-T
>>>
>>> The first cards (29-45) are the "older" USB tuners, 50 is the TwinStar does not schedule and
>>> 51 is the other tuner on the Twinstar that does schedule.
>>>
>>> I looked over my settings and they look good to me.
>>> I do notice One unusual message (see below). Is it related?
>>>
>>> Bootup messages that may be related:
>>>
>>> usb 1-4.4.2: New USB device found, idVendor=07ca, idProduct=0825, bcdDevice= 2.01
>>> usb 1-4.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>>> usb 1-4.4.2: Product: A825
>>> usb 1-4.4.2: Manufacturer: AVerMedia TECHNOLOGIES, Inc.
>>> usb 1-4.4.2: SerialNumber: 0000000000000
>>>
>>> dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
>>> usb 1-4.4.2: dvb_usb_v2: found a 'AVerMedia Twinstar (A825)' in warm state
>>> dvb_usb_af9035 1-4.4.2:1.0: Device may have issues with I2C read operations. Enabling fix. <<<<<<<<<<
>>> usb 1-4.4.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
>>> dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>>> usb 1-4.4.2: media controller created
>>> dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>>>
>>> $ uname -a
>>> Linux e7.eyal.emu.id.au 5.13.5-200.fc34.x86_64 #1 SMP Sun Jul 25 16:19:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> $ mythbackend --version
>>> [see attached file as requested]
>>>
>>> TIA
>>
>> I have a Kworld DVB-T 399UR dual DVB-T USB tuner, and on it both
>> tuners work, but due to some common hardware that is used by both
>> tuners, you can not use both tuners at once in Linux. It works fine
>> in Windows, which is where I am now using it.
>>
>> With your tuners, have you tried setting up manual recordings with the
>> tuner specified manually?
>
>Yes, and it always uses a different tuner rather than the preferred one.
>
>> In LiveTV, what happens if you manually switch to the problem tuners?
>
>No go. Changing to the twin tuner automatically switches to the same channel rather than the
>one I selected originally.
>
>Tuners 6 and 7 are the ones from the Twinstar.
>
>Tune to channel 34 on tuner 7 (a scheduled recording). OK.
>Tune to channel 34 on tuner 6 (live TV). OK.
> Change channel on tuner 6 to 30. On same multiplex. OK
> Change channel on tuner 6 to 53. A different multiplex. Myth changed to tuner 4.
> Change source back to tuner 6. Myth changed from channel 53 to 30.
>
>Myth seems to somehow know to not tune tuners 6 and 7 to different multiplexes.
>How is this done?

That is what I would expect from two multirec tuners attached to the
same physical tuner. So it would be a good idea to check and make
sure that your tuner numbers refer to what you think they do. This is
what the DVB-T tuners in my capturecard table look like:

MariaDB [mythconverg]> select
cardid,parentid,videodevice,cardtype,inputname,sourceid,displayname
from capturecard where inputname='DVB-T' order by videodevice,cardid;
+--------+----------+-----------------------------+----------+-----------+----------+----------------+
| cardid | parentid | videodevice | cardtype | inputname | sourceid | displayname |
+--------+----------+-----------------------------+----------+-----------+----------+----------------+
| 1 | 0 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.1 (1) |
| 2 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.2 (2) |
| 3 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.3 (3) |
| 4 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.4 (4) |
| 5 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.5 (5) |
| 6 | 0 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.1 (6) |
| 7 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.2 (7) |
| 8 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.3 (8) |
| 9 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.4 (9) |
| 10 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.5 (10) |
| 11 | 0 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.1 (11) |
| 12 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.2 (12) |
| 13 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.3 (13) |
| 14 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.4 (14) |
| 15 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.5 (15) |
| 16 | 0 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.1 (16) |
| 17 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.2 (17) |
| 18 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.3 (18) |
| 19 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.4 (19) |
| 20 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.5 (20) |
| 21 | 0 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.1 (21) |
| 22 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.2 (22) |
| 23 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.3 (23) |
| 24 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.4 (24) |
| 25 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.5 (25) |
+--------+----------+-----------------------------+----------+-----------+----------+----------------+

Tuners that have parentid=0 are the first tuner of a set of multirec
tuners. Where parentid is non-zero, it refers back to the cardid of a
tuner with parentid=0. I have manually adjusted my tuners so they are
all in order - yours may not be, so the cardid values may be out of
sequence in the table. I have also manually set the displayname
values so that the logs show exactly which tuner is being used.

Check that your tuners 6 and 7 both have parentid=0 and have different
videodevice values.
_______________________________________________
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
Re: cannot schedule both tuners on AVerMedia Twinstar [ In reply to ]
On 01/08/2021 00.32, Stephen Worthington wrote:
> On Sat, 31 Jul 2021 20:00:37 +1000, you wrote:
>
>> On 31/07/2021 13.25, Stephen Worthington wrote:
>>> On Sat, 31 Jul 2021 11:29:56 +1000, you wrote:
>>>
>>>> I had this USB tuner for a long time but decided to use it again now. Plugged it in and configured
>>>> the capture-card and input-connection. All tuners (there are 5 others) show up and can be tuned into in WatchTV.
>>>>
>>>> The wiki says "unsupported" but it was last updated in 2014 so probably out of date?
>>>>
>>>> The problem is with scheduling. I have the two Twinstar tuners set to almost the same priority.
>>>> myth refuses to use both, so (depending on the order I set) it will allow scheduling from one
>>>> and will not schedule on the other at all. I can change the priority to have it pick the other
>>>> and it then will never use the first.
>>>>
>>>> I am sure that this device has two independent tuners. It shows up as two devices in /dev/dvb/.
>>>> It shows up as two in mythtv status (actually each tuner shows up as 4 by reclimit).
>>>>
>>>> Looking at mythtv coming up I notice:
>>>>
>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[29]: Set delivery system: DVB-T
>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[33]: Set delivery system: DVB-T
>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[37]: Set delivery system: DVB-T
>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[41]: Set delivery system: DVB-T
>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[45]: Set delivery system: DVB-T
>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[50]: Set delivery system: DVB-T
>>>> CoreContext recorders/dvbchannel.cpp:699 (Tune) - DVBChan[50](/dev/dvb/adapter-OPEN-ELEC-6/frontend0): Next tuning after less than 1000ms. Delaying by 1000ms
>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[51]: Set delivery system: DVB-T
>>>>
>>>> The first cards (29-45) are the "older" USB tuners, 50 is the TwinStar does not schedule and
>>>> 51 is the other tuner on the Twinstar that does schedule.
>>>>
>>>> I looked over my settings and they look good to me.
>>>> I do notice One unusual message (see below). Is it related?
>>>>
>>>> Bootup messages that may be related:
>>>>
>>>> usb 1-4.4.2: New USB device found, idVendor=07ca, idProduct=0825, bcdDevice= 2.01
>>>> usb 1-4.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>>>> usb 1-4.4.2: Product: A825
>>>> usb 1-4.4.2: Manufacturer: AVerMedia TECHNOLOGIES, Inc.
>>>> usb 1-4.4.2: SerialNumber: 0000000000000
>>>>
>>>> dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
>>>> usb 1-4.4.2: dvb_usb_v2: found a 'AVerMedia Twinstar (A825)' in warm state
>>>> dvb_usb_af9035 1-4.4.2:1.0: Device may have issues with I2C read operations. Enabling fix. <<<<<<<<<<
>>>> usb 1-4.4.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
>>>> dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>>>> usb 1-4.4.2: media controller created
>>>> dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>>>>
>>>> $ uname -a
>>>> Linux e7.eyal.emu.id.au 5.13.5-200.fc34.x86_64 #1 SMP Sun Jul 25 16:19:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>>>>
>>>> $ mythbackend --version
>>>> [see attached file as requested]
>>>>
>>>> TIA
>>>
>>> I have a Kworld DVB-T 399UR dual DVB-T USB tuner, and on it both
>>> tuners work, but due to some common hardware that is used by both
>>> tuners, you can not use both tuners at once in Linux. It works fine
>>> in Windows, which is where I am now using it.
>>>
>>> With your tuners, have you tried setting up manual recordings with the
>>> tuner specified manually?
>>
>> Yes, and it always uses a different tuner rather than the preferred one.
>>
>>> In LiveTV, what happens if you manually switch to the problem tuners?
>>
>> No go. Changing to the twin tuner automatically switches to the same channel rather than the
>> one I selected originally.
>>
>> Tuners 6 and 7 are the ones from the Twinstar.
>>
>> Tune to channel 34 on tuner 7 (a scheduled recording). OK.
>> Tune to channel 34 on tuner 6 (live TV). OK.
>> Change channel on tuner 6 to 30. On same multiplex. OK
>> Change channel on tuner 6 to 53. A different multiplex. Myth changed to tuner 4.
>> Change source back to tuner 6. Myth changed from channel 53 to 30.
>>
>> Myth seems to somehow know to not tune tuners 6 and 7 to different multiplexes.
>> How is this done?
##### I still want to know the answer to this question. Anyone?

> That is what I would expect from two multirec tuners attached to the
> same physical tuner. So it would be a good idea to check and make
> sure that your tuner numbers refer to what you think they do. This is
> what the DVB-T tuners in my capturecard table look like:
>
> MariaDB [mythconverg]> select
> cardid,parentid,videodevice,cardtype,inputname,sourceid,displayname
> from capturecard where inputname='DVB-T' order by videodevice,cardid;
> +--------+----------+-----------------------------+----------+-----------+----------+----------------+
> | cardid | parentid | videodevice | cardtype | inputname | sourceid | displayname |
> +--------+----------+-----------------------------+----------+-----------+----------+----------------+
> | 1 | 0 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.1 (1) |
> | 2 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.2 (2) |
> | 3 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.3 (3) |
> | 4 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.4 (4) |
> | 5 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.5 (5) |
> | 6 | 0 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.1 (6) |
> | 7 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.2 (7) |
> | 8 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.3 (8) |
> | 9 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.4 (9) |
> | 10 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.5 (10) |
> | 11 | 0 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.1 (11) |
> | 12 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.2 (12) |
> | 13 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.3 (13) |
> | 14 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.4 (14) |
> | 15 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.5 (15) |
> | 16 | 0 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.1 (16) |
> | 17 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.2 (17) |
> | 18 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.3 (18) |
> | 19 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.4 (19) |
> | 20 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.5 (20) |
> | 21 | 0 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.1 (21) |
> | 22 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.2 (22) |
> | 23 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.3 (23) |
> | 24 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.4 (24) |
> | 25 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.5 (25) |
> +--------+----------+-----------------------------+----------+-----------+----------+----------------+

My data is very similar.

+--------+----------+----------------------------------------+----------+-----------+----------+-------------+
| cardid | parentid | videodevice | cardtype | inputname | sourceid | displayname |
+--------+----------+----------------------------------------+----------+-----------+----------+-------------+
| 29 | 0 | /dev/dvb/adapter-OPEN-ELEC-1/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-1 |
| 30 | 29 | /dev/dvb/adapter-OPEN-ELEC-1/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-1 |
| 31 | 29 | /dev/dvb/adapter-OPEN-ELEC-1/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-1 |
| 32 | 29 | /dev/dvb/adapter-OPEN-ELEC-1/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-1 |
| 33 | 0 | /dev/dvb/adapter-OPEN-ELEC-2/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-2 |
| 34 | 33 | /dev/dvb/adapter-OPEN-ELEC-2/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-2 |
| 35 | 33 | /dev/dvb/adapter-OPEN-ELEC-2/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-2 |
| 36 | 33 | /dev/dvb/adapter-OPEN-ELEC-2/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-2 |
| 37 | 0 | /dev/dvb/adapter-OPEN-ELEC-3/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-3 |
| 38 | 37 | /dev/dvb/adapter-OPEN-ELEC-3/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-3 |
| 39 | 37 | /dev/dvb/adapter-OPEN-ELEC-3/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-3 |
| 40 | 37 | /dev/dvb/adapter-OPEN-ELEC-3/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-3 |
| 41 | 0 | /dev/dvb/adapter-OPEN-ELEC-4/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-4 |
| 42 | 41 | /dev/dvb/adapter-OPEN-ELEC-4/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-4 |
| 43 | 41 | /dev/dvb/adapter-OPEN-ELEC-4/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-4 |
| 44 | 41 | /dev/dvb/adapter-OPEN-ELEC-4/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-4 |
| 45 | 0 | /dev/dvb/adapter-OPEN-ELEC-5/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-5 |
| 47 | 45 | /dev/dvb/adapter-OPEN-ELEC-5/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-5 |
| 48 | 45 | /dev/dvb/adapter-OPEN-ELEC-5/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-5 |
| 49 | 45 | /dev/dvb/adapter-OPEN-ELEC-5/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-5 |
| 50 | 0 | /dev/dvb/adapter-OPEN-ELEC-6/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-6 |
| 52 | 50 | /dev/dvb/adapter-OPEN-ELEC-6/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-6 |
| 53 | 50 | /dev/dvb/adapter-OPEN-ELEC-6/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-6 |
| 54 | 50 | /dev/dvb/adapter-OPEN-ELEC-6/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-6 |
| 51 | 0 | /dev/dvb/adapter-OPEN-ELEC-7/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-7 |
| 55 | 51 | /dev/dvb/adapter-OPEN-ELEC-7/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-7 |
| 56 | 51 | /dev/dvb/adapter-OPEN-ELEC-7/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-7 |
| 57 | 51 | /dev/dvb/adapter-OPEN-ELEC-7/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-7 |
+--------+----------+----------------------------------------+----------+-----------+----------+-------------+

cardid's are unusual due to cards replaced etc (e.g. sourceid=1 was from the analogue days).

> Tuners that have parentid=0 are the first tuner of a set of multirec
> tuners. Where parentid is non-zero, it refers back to the cardid of a
> tuner with parentid=0. I have manually adjusted my tuners so they are
> all in order - yours may not be, so the cardid values may be out of
> sequence in the table.

I used 'order by videodevice,cardid' to get the ordered list.

> I have also manually set the displayname
> values so that the logs show exactly which tuner is being used.

Good idea, I now renamed them too.

> Check that your tuners 6 and 7 both have parentid=0 and have different
> videodevice values.

They have, see cardid 50 and 51. They are really different devices (minor):

$ ls -l /dev/dvb/adapter-OPEN-ELEC-?/frontend0
crw-rw----+ 1 root video 212, 6 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-1/frontend0
crw-rw----+ 1 root video 212, 11 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-2/frontend0
crw-rw----+ 1 root video 212, 18 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-3/frontend0
crw-rw----+ 1 root video 212, 23 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-4/frontend0
crw-rw----+ 1 root video 212, 27 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-5/frontend0
crw-rw----+ 1 root video 212, 7 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-6/frontend0
crw-rw----+ 1 root video 212, 19 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-7/frontend0

--
Eyal Lebedinsky (eyal@eyal.emu.id.au)
_______________________________________________
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
Re: cannot schedule both tuners on AVerMedia Twinstar [ In reply to ]
On Sun, 1 Aug 2021 16:03:12 +1000, you wrote:

>
>
>On 01/08/2021 00.32, Stephen Worthington wrote:
>> On Sat, 31 Jul 2021 20:00:37 +1000, you wrote:
>>
>>> On 31/07/2021 13.25, Stephen Worthington wrote:
>>>> On Sat, 31 Jul 2021 11:29:56 +1000, you wrote:
>>>>
>>>>> I had this USB tuner for a long time but decided to use it again now. Plugged it in and configured
>>>>> the capture-card and input-connection. All tuners (there are 5 others) show up and can be tuned into in WatchTV.
>>>>>
>>>>> The wiki says "unsupported" but it was last updated in 2014 so probably out of date?
>>>>>
>>>>> The problem is with scheduling. I have the two Twinstar tuners set to almost the same priority.
>>>>> myth refuses to use both, so (depending on the order I set) it will allow scheduling from one
>>>>> and will not schedule on the other at all. I can change the priority to have it pick the other
>>>>> and it then will never use the first.
>>>>>
>>>>> I am sure that this device has two independent tuners. It shows up as two devices in /dev/dvb/.
>>>>> It shows up as two in mythtv status (actually each tuner shows up as 4 by reclimit).
>>>>>
>>>>> Looking at mythtv coming up I notice:
>>>>>
>>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[29]: Set delivery system: DVB-T
>>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[33]: Set delivery system: DVB-T
>>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[37]: Set delivery system: DVB-T
>>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[41]: Set delivery system: DVB-T
>>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[45]: Set delivery system: DVB-T
>>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[50]: Set delivery system: DVB-T
>>>>> CoreContext recorders/dvbchannel.cpp:699 (Tune) - DVBChan[50](/dev/dvb/adapter-OPEN-ELEC-6/frontend0): Next tuning after less than 1000ms. Delaying by 1000ms
>>>>> CoreContext cardutil.cpp:1173 (SetDeliverySystem) - CardUtil[51]: Set delivery system: DVB-T
>>>>>
>>>>> The first cards (29-45) are the "older" USB tuners, 50 is the TwinStar does not schedule and
>>>>> 51 is the other tuner on the Twinstar that does schedule.
>>>>>
>>>>> I looked over my settings and they look good to me.
>>>>> I do notice One unusual message (see below). Is it related?
>>>>>
>>>>> Bootup messages that may be related:
>>>>>
>>>>> usb 1-4.4.2: New USB device found, idVendor=07ca, idProduct=0825, bcdDevice= 2.01
>>>>> usb 1-4.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>>>>> usb 1-4.4.2: Product: A825
>>>>> usb 1-4.4.2: Manufacturer: AVerMedia TECHNOLOGIES, Inc.
>>>>> usb 1-4.4.2: SerialNumber: 0000000000000
>>>>>
>>>>> dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
>>>>> usb 1-4.4.2: dvb_usb_v2: found a 'AVerMedia Twinstar (A825)' in warm state
>>>>> dvb_usb_af9035 1-4.4.2:1.0: Device may have issues with I2C read operations. Enabling fix. <<<<<<<<<<
>>>>> usb 1-4.4.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
>>>>> dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>>>>> usb 1-4.4.2: media controller created
>>>>> dvbdev: DVB: registering new adapter (AVerMedia Twinstar (A825))
>>>>>
>>>>> $ uname -a
>>>>> Linux e7.eyal.emu.id.au 5.13.5-200.fc34.x86_64 #1 SMP Sun Jul 25 16:19:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
>>>>>
>>>>> $ mythbackend --version
>>>>> [see attached file as requested]
>>>>>
>>>>> TIA
>>>>
>>>> I have a Kworld DVB-T 399UR dual DVB-T USB tuner, and on it both
>>>> tuners work, but due to some common hardware that is used by both
>>>> tuners, you can not use both tuners at once in Linux. It works fine
>>>> in Windows, which is where I am now using it.
>>>>
>>>> With your tuners, have you tried setting up manual recordings with the
>>>> tuner specified manually?
>>>
>>> Yes, and it always uses a different tuner rather than the preferred one.
>>>
>>>> In LiveTV, what happens if you manually switch to the problem tuners?
>>>
>>> No go. Changing to the twin tuner automatically switches to the same channel rather than the
>>> one I selected originally.
>>>
>>> Tuners 6 and 7 are the ones from the Twinstar.
>>>
>>> Tune to channel 34 on tuner 7 (a scheduled recording). OK.
>>> Tune to channel 34 on tuner 6 (live TV). OK.
>>> Change channel on tuner 6 to 30. On same multiplex. OK
>>> Change channel on tuner 6 to 53. A different multiplex. Myth changed to tuner 4.
>>> Change source back to tuner 6. Myth changed from channel 53 to 30.
>>>
>>> Myth seems to somehow know to not tune tuners 6 and 7 to different multiplexes.
>>> How is this done?
> ##### I still want to know the answer to this question. Anyone?
>
>> That is what I would expect from two multirec tuners attached to the
>> same physical tuner. So it would be a good idea to check and make
>> sure that your tuner numbers refer to what you think they do. This is
>> what the DVB-T tuners in my capturecard table look like:
>>
>> MariaDB [mythconverg]> select
>> cardid,parentid,videodevice,cardtype,inputname,sourceid,displayname
>> from capturecard where inputname='DVB-T' order by videodevice,cardid;
>> +--------+----------+-----------------------------+----------+-----------+----------+----------------+
>> | cardid | parentid | videodevice | cardtype | inputname | sourceid | displayname |
>> +--------+----------+-----------------------------+----------+-----------+----------+----------------+
>> | 1 | 0 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.1 (1) |
>> | 2 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.2 (2) |
>> | 3 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.3 (3) |
>> | 4 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.4 (4) |
>> | 5 | 1 | /dev/dvb/adapter0/frontend0 | DVB | DVB-T | 1 | DVB-T 1.5 (5) |
>> | 6 | 0 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.1 (6) |
>> | 7 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.2 (7) |
>> | 8 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.3 (8) |
>> | 9 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.4 (9) |
>> | 10 | 6 | /dev/dvb/adapter1/frontend0 | DVB | DVB-T | 1 | DVB-T 2.5 (10) |
>> | 11 | 0 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.1 (11) |
>> | 12 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.2 (12) |
>> | 13 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.3 (13) |
>> | 14 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.4 (14) |
>> | 15 | 11 | /dev/dvb/adapter2/frontend0 | DVB | DVB-T | 1 | DVB-T 3.5 (15) |
>> | 16 | 0 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.1 (16) |
>> | 17 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.2 (17) |
>> | 18 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.3 (18) |
>> | 19 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.4 (19) |
>> | 20 | 16 | /dev/dvb/adapter3/frontend0 | DVB | DVB-T | 1 | DVB-T 4.5 (20) |
>> | 21 | 0 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.1 (21) |
>> | 22 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.2 (22) |
>> | 23 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.3 (23) |
>> | 24 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.4 (24) |
>> | 25 | 21 | /dev/dvb/adapter4/frontend0 | DVB | DVB-T | 1 | DVB-T 5.5 (25) |
>> +--------+----------+-----------------------------+----------+-----------+----------+----------------+
>
>My data is very similar.
>
>+--------+----------+----------------------------------------+----------+-----------+----------+-------------+
>| cardid | parentid | videodevice | cardtype | inputname | sourceid | displayname |
>+--------+----------+----------------------------------------+----------+-----------+----------+-------------+
>| 29 | 0 | /dev/dvb/adapter-OPEN-ELEC-1/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-1 |
>| 30 | 29 | /dev/dvb/adapter-OPEN-ELEC-1/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-1 |
>| 31 | 29 | /dev/dvb/adapter-OPEN-ELEC-1/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-1 |
>| 32 | 29 | /dev/dvb/adapter-OPEN-ELEC-1/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-1 |
>| 33 | 0 | /dev/dvb/adapter-OPEN-ELEC-2/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-2 |
>| 34 | 33 | /dev/dvb/adapter-OPEN-ELEC-2/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-2 |
>| 35 | 33 | /dev/dvb/adapter-OPEN-ELEC-2/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-2 |
>| 36 | 33 | /dev/dvb/adapter-OPEN-ELEC-2/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-2 |
>| 37 | 0 | /dev/dvb/adapter-OPEN-ELEC-3/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-3 |
>| 38 | 37 | /dev/dvb/adapter-OPEN-ELEC-3/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-3 |
>| 39 | 37 | /dev/dvb/adapter-OPEN-ELEC-3/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-3 |
>| 40 | 37 | /dev/dvb/adapter-OPEN-ELEC-3/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-3 |
>| 41 | 0 | /dev/dvb/adapter-OPEN-ELEC-4/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-4 |
>| 42 | 41 | /dev/dvb/adapter-OPEN-ELEC-4/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-4 |
>| 43 | 41 | /dev/dvb/adapter-OPEN-ELEC-4/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-4 |
>| 44 | 41 | /dev/dvb/adapter-OPEN-ELEC-4/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-4 |
>| 45 | 0 | /dev/dvb/adapter-OPEN-ELEC-5/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-5 |
>| 47 | 45 | /dev/dvb/adapter-OPEN-ELEC-5/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-5 |
>| 48 | 45 | /dev/dvb/adapter-OPEN-ELEC-5/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-5 |
>| 49 | 45 | /dev/dvb/adapter-OPEN-ELEC-5/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-5 |
>| 50 | 0 | /dev/dvb/adapter-OPEN-ELEC-6/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-6 |
>| 52 | 50 | /dev/dvb/adapter-OPEN-ELEC-6/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-6 |
>| 53 | 50 | /dev/dvb/adapter-OPEN-ELEC-6/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-6 |
>| 54 | 50 | /dev/dvb/adapter-OPEN-ELEC-6/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-6 |
>| 51 | 0 | /dev/dvb/adapter-OPEN-ELEC-7/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-7 |
>| 55 | 51 | /dev/dvb/adapter-OPEN-ELEC-7/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-7 |
>| 56 | 51 | /dev/dvb/adapter-OPEN-ELEC-7/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-7 |
>| 57 | 51 | /dev/dvb/adapter-OPEN-ELEC-7/frontend0 | DVB | DVB-T | 2 | OPEN-ELEC-7 |
>+--------+----------+----------------------------------------+----------+-----------+----------+-------------+
>
>cardid's are unusual due to cards replaced etc (e.g. sourceid=1 was from the analogue days).
>
>> Tuners that have parentid=0 are the first tuner of a set of multirec
>> tuners. Where parentid is non-zero, it refers back to the cardid of a
>> tuner with parentid=0. I have manually adjusted my tuners so they are
>> all in order - yours may not be, so the cardid values may be out of
>> sequence in the table.
>
>I used 'order by videodevice,cardid' to get the ordered list.
>
>> I have also manually set the displayname
>> values so that the logs show exactly which tuner is being used.
>
>Good idea, I now renamed them too.
>
>> Check that your tuners 6 and 7 both have parentid=0 and have different
>> videodevice values.
>
>They have, see cardid 50 and 51. They are really different devices (minor):
>
>$ ls -l /dev/dvb/adapter-OPEN-ELEC-?/frontend0
>crw-rw----+ 1 root video 212, 6 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-1/frontend0
>crw-rw----+ 1 root video 212, 11 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-2/frontend0
>crw-rw----+ 1 root video 212, 18 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-3/frontend0
>crw-rw----+ 1 root video 212, 23 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-4/frontend0
>crw-rw----+ 1 root video 212, 27 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-5/frontend0
>crw-rw----+ 1 root video 212, 7 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-6/frontend0
>crw-rw----+ 1 root video 212, 19 Jul 31 10:10 /dev/dvb/adapter-OPEN-ELEC-7/frontend0

That all looks OK. So now I think you need to turn on the -v record
option in mythbackend and post the full section of mythbackend.log
when you try to use both of the new tuners. To turn that option on,
run:

mythbackend --setverbose record

To turn it off again afterwards run:

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