[mythtv-users] scheduler madness

[James]

> On 6 Apr 2022, at 10:46 pm, David Engel <david at istwok.net> wrote:
> 
> On Wed, Apr 06, 2022 at 06:46:38AM +0800, James wrote:
>>> On 6 Apr 2022, at 1:25 am, Klaas de Waal <klaas.de.waal at gmail.com> wrote:
>>> Can you please show the content of the capturecard table, e.g. the output of this mysql command:
>>> select cardid,parentid,videodevice,cardtype,sourceid,recpriority,schedorder,livetvorder,reclimit,schedgroup from capturecard order by cardid;
>>> 
>>> I expect for all entries that column sourceid shows the same number.
>>> For column recpriority all values should be 0 (they do not need to be but that is how I have it).
>>> For column schedorder all values should be 1 (or higher) when parentid is 0.
>>> For column livetvorder all values should be 1 (or higher).
>>> For column reclimit all values should be 1 or higher.
>>> For column schedgroup the values should be 0 if the parent id is not 0; the value can be 1 if parentid is 0 and you want virtual tuners to be created when needed.
>> 
>> MariaDB [mythconverg]> select cardid,parentid,videodevice,cardtype,sourceid,recpriority,schedorder,livetvorder,reclimit,schedgroup from capturecard order by cardid;
>> +--------+----------+-----------------------------+----------+----------+-------------+------------+-------------+----------+------------+
>> | cardid | parentid | videodevice                 | cardtype | sourceid | recpriority | schedorder | livetvorder | reclimit | schedgroup |
>> +--------+----------+-----------------------------+----------+----------+-------------+------------+-------------+----------+------------+
>> |      1 |        0 | /dev/dvb/adapter0/frontend0 | DVB      |        1 |           0 |          1 |           1 |        2 |          1 |
>> |      2 |        0 | /dev/dvb/adapter1/frontend0 | DVB      |        1 |           0 |          1 |           1 |        2 |          1 |
>> |      3 |        0 | /dev/dvb/adapter2/frontend0 | DVB      |        1 |           0 |          1 |           1 |        2 |          1 |
>> |      4 |        0 | /dev/dvb/adapter3/frontend0 | DVB      |        1 |           0 |          1 |           1 |        2 |          1 |
>> |      5 |        1 | /dev/dvb/adapter0/frontend0 | DVB      |        1 |           0 |          0 |           1 |        2 |          0 |
>> |      6 |        2 | /dev/dvb/adapter1/frontend0 | DVB      |        1 |           0 |          0 |           1 |        2 |          0 |
>> |      7 |        3 | /dev/dvb/adapter2/frontend0 | DVB      |        1 |           0 |          0 |           1 |        2 |          0 |
>> |      8 |        4 | /dev/dvb/adapter3/frontend0 | DVB      |        1 |           0 |          0 |           1 |        2 |          0 |
>> +--------+----------+-----------------------------+----------+----------+-------------+------------+-------------+----------+------------+
>> 8 rows in set (0.000 sec)
> 
> Your capturecare table looks okay.  Can you provide the output from
> running "mythbackend -v schedule --loglevel debug --testsched"?
> 

David I should have done that! instead I installed suse Leap 15.2, did the same setup, and everything is perfect!! I'll try to repeat on another machine. I'm starting to wonder if carelessly or network fault the sw got screwed-up, either way (it works/doesn't work)  I'll post the result
James