[mythtv-users] Upcoming recordings gone

[Stephen Worthington]

On Sat, 30 Oct 2021 10:21:38 +0100, you wrote:

>On 30/10/2021 09:35, Daryl McDonald wrote:
>> On Fri, Oct 29, 2021 at 10:52 PM Stephen Worthington <
>> stephen_agent at jsw.gen.nz> wrote:
>> 
>>> On Fri, 29 Oct 2021 21:49:29 -0400, you wrote:
>>>
>>>> On Fri, Oct 29, 2021 at 9:37 PM Bill Meek <keemllib at gmail.com> wrote:
>>>>
>>>>> On 10/29/21 4:04 PM, Daryl McDonald wrote:
>>>>>>
>>>>>>
>>>>>> On Fri, Oct 29, 2021 at 3:51 PM Bill Meek <keemllib at gmail.com
>>> <mailto:
>>>>> keemllib at gmail.com>> wrote:
>>>>>>
>>>>>>      On 10/29/21 2:44 PM, Daryl McDonald wrote:
>>>>>>      >
>>>>>>      >
>>>>>>      > On Fri, Oct 29, 2021 at 6:14 AM Paul Harrison <
>>> mythtv at mythqml.net
>>>>> <mailto:mythtv at mythqml.net> <mailto:mythtv at mythqml.net
>>>>>>      <mailto:mythtv at mythqml.net>>> wrote:
>>>>>>      >
>>>>>>      >     On 28/10/2021 23:50, Daryl McDonald wrote:
>>>>>>      >
>>>>>>      >>
>>>>>>      >>
>>>>>>      >>     On Thu, Oct 28, 2021 at 5:09 PM Bill Meek <
>>> keemllib at gmail.com
>>>>> <mailto:keemllib at gmail.com> <mailto:keemllib at gmail.com
>>>>>>      <mailto:keemllib at gmail.com>>> wrote:
>>>>>>      >>
>>>>>>      >>         On 10/28/21 4:03 PM, Daryl McDonald wrote:
>>>>>>      >>         > I just upgraded and nothing for myth or mysql that I
>>> saw
>>>>>>      >>
>>>>>>      >>         It usually takes a day or so. Look in your backend log
>>> to
>>>>> see if
>>>>>>      >>         the same error is still there. If you see: BIGINT, for
>>>>> example,
>>>>>>      >>         that's a clue.
>>>>>>      >>
>>>>>>      >>         --
>>>>>>      >>         Bill
>>>>>>      >>         _______________________________________________
>>>>>>      >>
>>>>>>      >>     OK, practicing patience here. Thanks, again.
>>>>>>      >>
>>>>>>      >>
>>>>>>      >
>>>>>>      >     For any Ubuntu users using the PPA's both mythbuntu/31
>>>>> (fixes/31) and mythbuntu/32 (master) have now been updated with the fix.
>>>>>>      >
>>>>>>      >
>>>>>>      >     Paul H.
>>>>>>      >
>>>>>>      > I got the updates this morning, but still no recordings being
>>>>> scheduled.  When might things get back to functional?
>>>>>>
>>>>>>      When you try to schedule a new recording, look in the backend log.
>>>>> Is the same SQL error
>>>>>>      message there?
>>>>>>
>>>>>>      Look for this:
>>>>>>
>>>>>>      BIGINT UNSIGNED value is out of range in
>>>>> '((`mythconverg`.`c`.`recpriority` +
>>>>> `mythconverg`.`capturecard`.`recpriority`) +
>>>>>>      ((`mythconverg`.`capturecard`.`cardid` =
>>>>> `mythconverg`.`sched_temp_record`.`prefinput`) * 2))'
>>>>>>
>>>>>>      It's issue fixed for me and others reporting on the Forum.
>>>>>>
>>>>>>      --
>>>>>>      Bill
>>>>>>      __
>>>>>>
>>>>>> There seems to be some kind of dberror, here is a short log from the
>>>>> backend :
>>>>>>
>>>>>>   https://paste.ubuntu.com/p/VBVtxZJzPK/ <
>>>>> https://paste.ubuntu.com/p/VBVtxZJzPK/>
>>>>>
>>>>> Any Custom Priority rules:
>>>>>
>>>>>    mysql --user=mythtv --password --host=localhost --execute="SELECT *
>>> FROM
>>>>> powerpriority,powerpriority_tmp" mythconverg
>>>>>
>>>>> --
>>>>> Bill
>>>>>
>>>>>
>>>> daryl at trieli:~$ mysql --user=mythtv --password --host=localhost
>>>> --execute="SELECT * FROM powerpriority,powerpriority_tmp" mythconverg
>>>> Enter password:
>>>
>>>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>>>> | priorityname | recpriority | selectclause                          |
>>>> priorityname | recpriority | selectclause                          |
>>>
>>>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>>>> | CBSnotADP#0  |         -50 | channel.mplexid=6 and cardid in (1,5) |
>>>> CBSnotADP#0  |         -50 | channel.mplexid=6 and cardid in (1,5) |
>>>
>>>> +--------------+-------------+---------------------------------------+--------------+-------------+---------------------------------------+
>>>> daryl at trieli:~$
>>>>
>>>> Stephen and I just put this one in due to a less sensitive tuner card
>>>
>>> It might be an idea to reverse that rule - add 50 when the opposite of
>>> the condition applies:
>>>
>>> update powerpriority set
>>> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>>> (1,5)' where priorityname='CBSnotADP#0';
>>>
>>> (or change it via mythfrontend).
>>>
>>> That should have the same effect without causing negative priorities.
>>>
>>>   mysql> recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> (1,5)' where priorityname='CBSnotADP#0';
>> ERROR 1064 (42000): You have an error in your SQL syntax; check the manual
>> that corresponds to your MySQL server version for the right syntax to use
>> near 'recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
>> (1,5)' where pr' at line 1
>> mysql>
>> 
>You overlooked the previous line. That command should all read:
>
>mysql> update powerpriority set recpriority=50,selectclause='channel.mplexid!=6 or cardid not in
> >> (1,5)' where priorityname='CBSnotADP#0';
>
>(all on one line, of course)
>
>That all looks horrible to me and easy to get wrong. I'd do the changes using the front end, 
>manually tweaking the rules individually. Of course, that depends on how many rules you have to do.

There is just the one rule.  It adjusts the tuner priorities so that
the two virtual tuners on the physical tuner that has problems
recording from one multiplex are much lower priority for use when that
multiplex is being recorded from.  So that multiplex will only be
recorded on the other three tuners.

Changing the settings from mythfrontend has the problem that
mythfrontend (and all MythTV programs) do not allow pasting of text,
so you have to manually type it in.