Conflict recording problem.

[mvallevand]

I created a recurring recording today from Kodi with the following rule for anytime on Tueday.

Code:

<Rules>
  <EPGTitle>Schitt&apos;s Creek</EPGTitle>
  <ChannelOID>9013</ChannelOID>
  <ChannelName>CBOT-DT</ChannelName>
  <StartTime>2019-02-13T00:00:00.0000000Z</StartTime>
  <EndTime>2019-02-13T00:30:00.0000000Z</EndTime>
  <PrePadding>0</PrePadding>
  <PostPadding>0</PostPadding>
  <Quality>0</Quality>
  <Keep>0</Keep>
  <RecordingDirectoryID>[Default]</RecordingDirectoryID>
  <Days>TUESDAY</Days>
</Rules>

I had a conflict at a 7pm recording which was ok but for some reason 3 other recordings that didn't have a conflict where also marked as conflicts

Code:

2019-02-12 18:01:39.179    [DEBUG][7]     - Potential episode at: 12/02/2019 7:00:00 PM
2019-02-12 18:01:39.184    [DEBUG][7]       ...check IsValid()
2019-02-12 18:01:39.185    [DEBUG][7]       ...this episode is on Tuesday
2019-02-12 18:01:39.185    [DEBUG][7]       ...valid days are: TUESDAY
2019-02-12 18:01:39.185    [DEBUG][7]       ...scheduling episode
2019-02-12 18:01:39.185    [DEBUG][7]    ScheduleRecording@1
....
2019-02-12 18:01:39.201    [DEBUG][7]    ScheduleRecording@6
2019-02-12 18:01:39.201    [DEBUG][7]       ...was unable to schedule recording...marking as conflict
2019-02-12 18:01:39.206    [DEBUG][7]     - Potential episode at: 12/02/2019 9:00:00 PM
2019-02-12 18:01:39.206    [DEBUG][7]       ...check IsValid()
2019-02-12 18:01:39.206    [DEBUG][7]       ...this episode is on Tuesday
2019-02-12 18:01:39.206    [DEBUG][7]       ...valid days are: TUESDAY
2019-02-12 18:01:39.206    [DEBUG][7]       ...scheduling episode

2019-02-12 18:01:39.222    [DEBUG][7]    ScheduleRecording@6
2019-02-12 18:01:39.222    [DEBUG][7]       ...was unable to schedule recording...marking as conflict
2019-02-12 18:01:39.236    [DEBUG][7]     - Potential episode at: 19/02/2019 7:00:00 PM
2019-02-12 18:01:39.236    [DEBUG][7]       ...check IsValid()
2019-02-12 18:01:39.236    [DEBUG][7]       ...this episode is on Tuesday
2019-02-12 18:01:39.236    [DEBUG][7]       ...valid days are: TUESDAY
2019-02-12 18:01:39.236    [DEBUG][7]       ...scheduling episode

2019-02-12 18:01:39.252    [DEBUG][7]    ScheduleRecording@6
2019-02-12 18:01:39.252    [DEBUG][7]       ...was unable to schedule recording...marking as conflict
2019-02-12 18:01:39.259    [DEBUG][7]     - Potential episode at: 19/02/2019 9:00:00 PM
2019-02-12 18:01:39.259    [DEBUG][7]       ...check IsValid()
2019-02-12 18:01:39.259    [DEBUG][7]       ...this episode is on Tuesday
2019-02-12 18:01:39.259    [DEBUG][7]       ...valid days are: TUESDAY
2019-02-12 18:01:39.259    [DEBUG][7]       ...scheduling episode
...
2019-02-12 18:01:39.278    [DEBUG][7]       ...was unable to schedule recording...marking as conflict

Martin

[BrettB]

I created a recurring recording today from Kodi with the following rule for anytime on Tueday.

Code:

<Rules>
  <EPGTitle>Schitt's Creek</EPGTitle>
  <ChannelOID>9013</ChannelOID>
  <ChannelName>CBOT-DT</ChannelName>
  <StartTime>2019-02-13T00:00:00.0000000Z</StartTime>
  <EndTime>2019-02-13T00:30:00.0000000Z</EndTime>
  <PrePadding>0</PrePadding>
  <PostPadding>0</PostPadding>
  <Quality>0</Quality>
  <Keep>0</Keep>
  <RecordingDirectoryID>[Default]</RecordingDirectoryID>
  <Days>TUESDAY</Days>
</Rules>

I had a conflict at a 7pm recording which was ok but for some reason 3 other recordings that didn't have a conflict where also marked as conflicts

Code:

2019-02-12 18:01:39.179    [DEBUG][7]     - Potential episode at: 12/02/2019 7:00:00 PM
2019-02-12 18:01:39.184    [DEBUG][7]       ...check IsValid()
2019-02-12 18:01:39.185    [DEBUG][7]       ...this episode is on Tuesday
2019-02-12 18:01:39.185    [DEBUG][7]       ...valid days are: TUESDAY
2019-02-12 18:01:39.185    [DEBUG][7]       ...scheduling episode
2019-02-12 18:01:39.185    [DEBUG][7]    ScheduleRecording@1
....
2019-02-12 18:01:39.201    [DEBUG][7]    ScheduleRecording@6
2019-02-12 18:01:39.201    [DEBUG][7]       ...was unable to schedule recording...marking as conflict
2019-02-12 18:01:39.206    [DEBUG][7]     - Potential episode at: 12/02/2019 9:00:00 PM
2019-02-12 18:01:39.206    [DEBUG][7]       ...check IsValid()
2019-02-12 18:01:39.206    [DEBUG][7]       ...this episode is on Tuesday
2019-02-12 18:01:39.206    [DEBUG][7]       ...valid days are: TUESDAY
2019-02-12 18:01:39.206    [DEBUG][7]       ...scheduling episode

2019-02-12 18:01:39.222    [DEBUG][7]    ScheduleRecording@6
2019-02-12 18:01:39.222    [DEBUG][7]       ...was unable to schedule recording...marking as conflict
2019-02-12 18:01:39.236    [DEBUG][7]     - Potential episode at: 19/02/2019 7:00:00 PM
2019-02-12 18:01:39.236    [DEBUG][7]       ...check IsValid()
2019-02-12 18:01:39.236    [DEBUG][7]       ...this episode is on Tuesday
2019-02-12 18:01:39.236    [DEBUG][7]       ...valid days are: TUESDAY
2019-02-12 18:01:39.236    [DEBUG][7]       ...scheduling episode

2019-02-12 18:01:39.252    [DEBUG][7]    ScheduleRecording@6
2019-02-12 18:01:39.252    [DEBUG][7]       ...was unable to schedule recording...marking as conflict
2019-02-12 18:01:39.259    [DEBUG][7]     - Potential episode at: 19/02/2019 9:00:00 PM
2019-02-12 18:01:39.259    [DEBUG][7]       ...check IsValid()
2019-02-12 18:01:39.259    [DEBUG][7]       ...this episode is on Tuesday
2019-02-12 18:01:39.259    [DEBUG][7]       ...valid days are: TUESDAY
2019-02-12 18:01:39.259    [DEBUG][7]       ...scheduling episode
...
2019-02-12 18:01:39.278    [DEBUG][7]       ...was unable to schedule recording...marking as conflict

Martin

Martin, Martin, Martin. Where are the logs??????

[mvallevand]

Brett I added the relevant log in my original (when you use Kodi scheduling is all in web.log) but I kept it if was needed. If you see anything useful let us know. I will let this run for my EPG update and I have put a similar fake entry in for next Tuesday to see if the same thing happens and I will post again.

Martin

[mvallevand]

Ok attached are the NRecord log and the NextPVR -recurring logs and both of them have the same problem marking shows with no conflict as Conflicts.

Martin

[sub]

I've taken a good look at the logs, but it's not immediately clear to me what is happening. If you want to supply your npvr.db3, I'll run up "nextpvr.exe -recurring" in the debugger, and check these specific attempts to see what it is conflicting with.

[mvallevand]

Here you go https://1drv.ms/u/s!Ar-w3NVk_f-Mjy_q9CkdsfDiUPQk

While you are in the debugger Radio XY channel 700 is the Internet Radio station that doesn't play.

Martin

[sub]

It looks like it's failing because it cant find an available capture source.

More specifically.... 9013 (CBOT-DT) is only available on one capture source, an HDHomeRUN, but that device marked as 'present=N' so it's not attempting to schedule against that device, leaving no available capture source.

[mvallevand]

Thanks for looking into it so you are saying that because my HDHR is offline I can't create recurring recordings on it. I often have it unplugged.

Martin

[sub]

Thanks for looking into it so you are saying that because my HDHR is offline I can't create recurring recordings on it. I often have it unplugged.

NextPVR only looks for and updates tuners where you visit the Settings->Devices screen. When you last visited the Settings->Devices screen, you didn't have the device, much like a user unplugging a PCIe tuner they previously had channels on, so it marked the device as present=false (ie 'not available for use').

[mvallevand]

Ok not great because I am in there a lot with my device off lately but at least now I now how to manage it using the database.

Martin