[schedchk] Check recording schedule and fix problems

sceptic

Forum Supporter
It would be nice if schedchk could monitor series which have ended (based on last recorded date) and when that date is over a certain user definable tolerance (number of days) then remove that entry automatically from the scheduled recording list. It would be nice not to have to do that but if you get more than a few it really starts to slow down the UI in the guide...
 
User Feedback.

The settings panel is slightly non-intuitive, or at least grammatically clumsy.

A baker's dozen of "Don't"s, each preceded by a Yes/No switch.

If I think, "No, I don't want to check for conflicts" then I set it to
"Yes - Don't check for conflicts".

I am not advocating that it's changed at this late stage, but I think from a UI POV it would have been better for the default to be positive statements.
 
OP
MymsMan

MymsMan

Ad detector
User Feedback.

The settings panel is slightly non-intuitive, or at least grammatically clumsy.

A baker's dozen of "Don't"s, each preceded by a Yes/No switch.

If I think, "No, I don't want to check for conflicts" then I set it to
"Yes - Don't check for conflicts".

I am not advocating that it's changed at this late stage, but I think from a UI POV it would have been better for the default to be positive statements.
I will agree with you on that - I can confuse myself

IF I get around to updating I am considering a three position switch with Off/Test/On for each option
 
Could I get a ruling on this notification?
Code:
29/06/2021 22:15:18 - SchedChk: *** Updated *** 29/06/21 23:10  00:45 === slot 46 === Crouchy's Year-Late Euros: Live === BBC ONE HD === Start Mismatch: 1625004600 != 1625003100
29/06/2021 22:15:21 - SchedChk: *** Updated *** 29/06/21 23:55  00:45 === slot 5 === Bates Motel === BBC ONE HD === Start Mismatch: 1625007300 != 1625005800
29/06/2021 22:15:22 - SchedChk: *** Updated *** 30/06/21 00:40  00:40 === slot 5 === Bates Motel === BBC ONE HD === Start Mismatch: 1625010000 != 1625008500
29/06/2021 23:07:24 - SchedChk: *** Updated *** 29/06/21 23:15  00:45 === slot 46 === Crouchy's Year-Late Euros: Live === BBC ONE HD === Start Mismatch: 1625004900 != 1625004600 (2 instances)
29/06/2021 23:07:27 - SchedChk: *** Updated *** 30/06/21 00:00  00:45 === slot 5 === Bates Motel === BBC ONE HD === Start Mismatch: 1625007600 != 1625007300 (2 instances)
29/06/2021 23:07:28 - SchedChk: *** Updated *** 30/06/21 00:45  00:40 === slot 5 === Bates Motel === BBC ONE HD === Start Mismatch: 1625010300 != 1625010000 (2 instances)
30/06/2021 00:46:30 - SchedChk: *** Status recording but Not recording *** - 30/06/21 00:00 00:45 === slot 5 === Bates Motel === BBC ONE HD
30/06/2021 00:46:32 - SchedChk: Unable to schedule alternate for non-recording programme -30/06/21 00:00 00:45 === slot 5 === Bates Motel === BBC ONE HD
Does this mean:-
A) That the FreeView EPG changed, SchedChk noticed and changed Humax's recording schedule or
B) That the FreeView EPG changed, Humax changed its recording schedule and SchedChk is notifying me of those changes?

In other words, would these three recordings have failed if I had not had SchedChk installed?
 
OP
MymsMan

MymsMan

Ad detector
A) That the FreeView EPG changed, SchedChk noticed and changed Humax's recording schedule
But the last message indicates that Bates Motel had not actually started when expected but there was no alternative available - It may still have recorded correctly since it was still close to the rescheduled start
 
But the last message indicates that Bates Motel had not actually started when expected but there was no alternative available - It may still have recorded correctly since it was still close to the rescheduled start
Thanks.

FYI All three recorded correctly.
 
User Feedback.

Code:
16/07/2021 07:32:02 - SchedChk: *** Updated *** 21/07/21 22:00 00:35 === slot 5 === New: This Way Up === Channel 4 HD-->16/07/21 23:10  00:30 === This Way Up === Channel 4 HD === 1-off recording (34 instances)
SchedChk seems to be tripped up by repeats broadcast in the same week as the initial showings.

It often tries to either record the repeat as well.

Or ignore the initial showing and set the series link to record the repeat only.

[Edit] The SchedChk system notification above keeps reappearing despite repeated clicking of the Acknowldge button.
 
Last edited:
OP
MymsMan

MymsMan

Ad detector
User Feedback.

Code:
16/07/2021 07:32:02 - SchedChk: *** Updated *** 21/07/21 22:00 00:35 === slot 5 === New: This Way Up === Channel 4 HD-->16/07/21 23:10  00:30 === This Way Up === Channel 4 HD === 1-off recording (34 instances)
SchedChk seems to be tripped up by repeats broadcast in the same week as the initial showings.

It often tries to either record the repeat as well.

Or ignore the initial showing and set the series link to record the repeat only.

[Edit] The SchedChk system notification above keeps reappearing despite repeated clicking of the Acknowldge button.
Schedchk is correctly identifying tonight's showings of This Way Up as one-off broadcasts - they are in the schedule without a series crid

The problem is that it believes it has successfully scheduled the programme to record but, for some unknown reason, the scheduling has not occurred and so on subsequent reruns of schedchk it is retrying the schedule and recreating the alert message.

I will try and schedule This Way Up to see if it occurs for me but could you post rsvsync.log and nugget.log entries for the period immediately around the time of one of the alert messages.

Update: I was able to recreate the issue so I will investigate further. No need to post logs.
In the meantime you could turn 1off recording checking in settings
 
Last edited:

Wildebeest

Member
Any idea why I've got a recording of "littleBe: Percy's Tiger Tales" instead of "The Inspector Lynley Mysteries"? One of the channels using an incorrect crid? Any way of avoiding this happening again in the future?

Code:
12/01/2022 22:33:46 - SchedChk: *** Updated *** 19/01/22 20:00 02:00 === slot 22 === The Inspector Lynley Mysteries === Drama-->13/01/22 09:50  00:15 === littleBe: Percy's Tiger Tales === ITVBe === Unscheduled episode
12/01/2022 22:33:50 - SchedChk: *** Updated *** 19/01/22 20:00 02:00 === slot 22 === The Inspector Lynley Mysteries === Drama-->14/01/22 09:50  00:15 === littleBe: Percy's Tiger Tales === ITVBe === Unscheduled episode
 
OP
MymsMan

MymsMan

Ad detector
Any idea why I've got a recording of "littleBe: Percy's Tiger Tales" instead of "The Inspector Lynley Mysteries"? One of the channels using an incorrect crid? Any way of avoiding this happening again in the future?

Code:
12/01/2022 22:33:46 - SchedChk: *** Updated *** 19/01/22 20:00 02:00 === slot 22 === The Inspector Lynley Mysteries === Drama-->13/01/22 09:50  00:15 === littleBe: Percy's Tiger Tales === ITVBe === Unscheduled episode
12/01/2022 22:33:50 - SchedChk: *** Updated *** 19/01/22 20:00 02:00 === slot 22 === The Inspector Lynley Mysteries === Drama-->14/01/22 09:50  00:15 === littleBe: Percy's Tiger Tales === ITVBe === Unscheduled episode
Check the crids for the two programmes - I suspect the series crids will be the same.

Crids used by one broadcaster should be unique across all their channels (but are not always) but there is nothing to ensure another broadcaster doesn't use the same crids though in practice it rarely happens.

When coding SchedChk I didn't include a channel number number check in the epg search because I wanted to be able to catch examples where, for example, the BBC shuffles programmes from BBC 1 to BBC to make way for a sports event or a BoJo Covid press conference.
It would have been better to include the boadcaster prefix (e.g. fp.bbc.co.uk) in the epg search.
 
Top