[mythtv-users] Scheduler sometimes seems to skip the first possible recording time

John jksjdevelop at gmail.com
Fri Feb 15 08:37:25 UTC 2019

On 15/02/2019 08:27, Stephen Worthington wrote:
> On Thu, 14 Feb 2019 22:54:38 +0100, you wrote:
>> Hello!
>> I am still on version 29.1 but I have felt for some time that the
>> scheduler sometimes seems to skip the first possible recording time.
>> Is it possible to somehow debug/follow the decisions that ends up
>> in the scheduled recording time for a specific entry?
> The output of this command might help with that:
> mythbackend --printsched
> It runs the scheduler and outputs a list of the scheduled recordings,
> including those that match a recording rule but are not chosen as a
> recording time.  You can also turn on debug output for the database
> queries and the scheduler and see what is logged when the scheduler is
> run, and then run those same queries yourself manually and see what
> they do and what output they give;
> mythbackend --setverbose database,schedule
> To turn off the extra logging:
> mythbackend --setverbose nodatabase,noschedule
> To see the other logging categories:
> mythbackend -v help
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

I have noticed that when the scheduler skips the first possible 
recording time of a show it is due to the preferred tuner being busy at 
that time even though others may be available. If this is undesirable 
check that all tuners have the same priority.

More information about the mythtv-users mailing list