Record - Record Season (All episodes on this channel) fails

[dbfs]

Hi all,

I am running the latest NextPVr (4.2.3) on a Windows 10.

Using NCIS as an example, the problem I have is that when I choose an episode on Chanel 10 and choose Record - Record Season (All episodes on this channel) the second episode will highlight as red to indicate that it will record but not the first one, the actual one I chose.

I have done the same thing with NCIS episodes on 10 BOLD and some will be set to record and not others. I have also chosen all episodes on all channels and the same thing happens. I don't want to use this "all channels" option as I don't want to record the HD channels.

Quick Record does work to record the missing episodes.

I get similar problems if I use the NextPVR app on my iPad. I have enclosed the log file and an image showing the results of choosing all episodes on channel 10 and 10 BOLD.

Regards
David

Windows 10
i5 8500 3.0 GHz, 16 Gb
2 x Hauppauge WinTV QuadHD DVB-T

[ATTACHMENT NOT FOUND]

[BrettB]

I have enclosed the log file and an image showing the results of choosing all episodes on channel 10 and 10 BOLD.

You didn't actually include any log files, so we can't verify. But from what you describe, I'm quite sure the "problem" is that you have recently recorded the specific episodes which are not being marked to be re-recorded. By default NextPVR keeps a list of specific episodes which have been recorded (even if deleted) and won't re-record them. I think the default is for 90 days, but there is a setting to configure how long to keep entries in the list. There is also a command line option to completely clear the list.

[dbfs]

Hi Brett B,

Thanks for your reply.

All the NCIS episodes are highlighted in the guide as being new. They don't currently repeat episodes at different times or channels.

I cancelled the existing recurring recording schedules for NCIS and tried the command line settings -removehistory

and then choose Record - Record Season (All episodes on this channel) for NCIS on 10 and 10 BOLD but there was no change to the erratic behavior of some episodes being set to record and not others. I then tried
-recurring
-reload
-updatedb

Still no improvement.

I think this time I have succeeded in attaching the logs.
[ATTACH=CONFIG]46523[/ATTACH]

Regards
David

Windows 10
i5 8500 3.0 GHz, 16 Gb
2 x Hauppauge WinTV QuadHD DVB-T

[Graham]

All the NCIS episodes are highlighted in the guide as being new.

Do you get different results if you select to record "new" episodes or select to record "all" episodes?

The decisions about whether an episode is new or not depends upon the content of the EPG data and that content varies depending upon the location and provider.

The npvr.log.2 has this ...

2019-02-17 18:07:06.193 [DEBUG][1] - Potential episode at: 20/02/2019 10:30:00 PM
2019-02-17 18:07:06.193 [DEBUG][1] ...check IsValid()
2019-02-17 18:07:06.193 [DEBUG][1] ...already got this episode: NCIS/61313E994049
2019-02-17 18:07:06.193 [DEBUG][1] existing status: STATUS_PENDING
2019-02-17 18:07:06.193 [DEBUG][1] existing time: 18/02/2019 7:30:00 PM - 18/02/2019 8:30:00 PM
2019-02-17 18:07:06.193 [DEBUG][1] ...already got this episode scheduled
2019-02-17 18:07:06.193 [DEBUG][1] - Potential episode at: 20/02/2019 11:30:00 PM
2019-02-17 18:07:06.193 [DEBUG][1] ...check IsValid()
2019-02-17 18:07:06.193 [DEBUG][1] ...already got this episode: NCIS/61313E994050
2019-02-17 18:07:06.193 [DEBUG][1] existing status: STATUS_PENDING
2019-02-17 18:07:06.193 [DEBUG][1] existing time: 19/02/2019 7:30:00 PM - 19/02/2019 8:30:00 PM
2019-02-17 18:07:06.193 [DEBUG][1] ...already got this episode scheduled
2019-02-17 18:07:06.193 [DEBUG][1] - Potential episode at: 21/02/2019 7:30:00 PM
2019-02-17 18:07:06.193 [DEBUG][1] ...check IsValid()
2019-02-17 18:07:06.193 [DEBUG][1] ...scheduling episode

The messages include "already got this episode scheduled" and "already got this episode". It might be that you can diagnose this by scheduling the recordings and then looking at the messages in the log.

For completeness, NextPVR starts a new log each time that the program starts and should keep the four most recent logs. Anything done before the four most recent stop & starts will not be in a log ... npvr.log is the most recent, npvr.log.1 is the next most recent and so on

[dbfs]

Hi Graham,

Thanks for the reply and the info on the logs.

I went to Feb 20 in the schedule on 10 Bold. The NCIS episode at 7:30 was scheduled to record and marked as new, but the ones at 10:30 and 11:30 pm weren't red but were both marked as new. I chose the 10:30 pm episode and chose to record all new episodes on this channel and neither the 10:30 or 11:30 episodes became red. So yes I get the same result.

[ATTACH=CONFIG]46525[/ATTACH]

Regards
David

[BrettB]

I went to Feb 20 in the schedule on 10 Bold. The NCIS episode at 7:30 was scheduled to record and marked as new, but the ones at 10:30 and 11:30 pm weren't red but were both marked as new.

The episode at 10:30 wasn't scheduled to record because it is the same episode as the episode at 7:35pm on Feb 18:

Code:

2019-02-17 21:52:20.983    [DEBUG][1]     - Potential episode at: 20/02/2019 10:30:00 PM
2019-02-17 21:52:20.983    [DEBUG][1]       ...check IsValid()
2019-02-17 21:52:20.983    [DEBUG][1]       ...already got this episode: [B]NCIS/61313E994049[/B] (already pending)
2019-02-17 21:52:20.983    [DEBUG][1]       ...already got this episode scheduled

Code:

2019-02-17 21:52:20.982    [DEBUG][1]     - Potential episode at: 18/02/2019 7:35:20 PM
2019-02-17 21:52:20.982    [DEBUG][1]       ...check IsValid()
2019-02-17 21:52:20.983    [DEBUG][1]          ..before start date
2019-02-17 21:52:20.983    [DEBUG][1]       ...already got this episode: [B]NCIS/61313E994049[/B] (already pending)
2019-02-17 21:52:20.983    [DEBUG][1]       ...doesnt match recurring rules

And the episode at 11:30 wasn't scheduled to record because it is the same episode as the episode at 7:30pm on Feb 19:

Code:

2019-02-17 21:52:20.983    [DEBUG][1]     - Potential episode at: 20/02/2019 11:30:00 PM
2019-02-17 21:52:20.983    [DEBUG][1]       ...check IsValid()
2019-02-17 21:52:20.983    [DEBUG][1]       ...already got this episode: [B]NCIS/61313E994050[/B] (already pending)
2019-02-17 21:52:20.983    [DEBUG][1]       ...already got this episode scheduled

Code:

2019-02-17 21:52:20.983    [DEBUG][1]     - Potential episode at: 19/02/2019 7:30:00 PM
2019-02-17 21:52:20.983    [DEBUG][1]       ...check IsValid()
2019-02-17 21:52:20.983    [DEBUG][1]          ..before start date
2019-02-17 21:52:20.983    [DEBUG][1]       ...already got this episode: [B]NCIS/61313E994050[/B] (already pending)

Note that in both of those cases, the earlier episode also says "already pending", so it probably wouldn't show up as red either since there is most likely another even earlier airing of that episode scheduled or the episode has already been recorded.

[dbfs]

Hi Brett/Graham,

Thanks for your assistance

I agree with your logic with the logs. The only problem is that in the schedule they are all marked as new and secondly if I choose to record all episodes on this channel I would expect it to record all episodes irrespective of them being repeats. If I choose record all new episodes that would be a different matter. I might note that the episodes in question on 10 Bold are reruns of old episodes but they have not been played on this channel before. They are not playing the same episode multiple times during the week or within the last 90 days. There must be something wrong with how 10 and 10 Bold supply the episode information in the EPG.

I have just had a look at the pending recordings and there are episodes listed there to be recorded that are not showing as red in the schedule so that adds another layer of confusion. For instance tomorrow's episode (19th) at 7:30 wasn't showing up as red in the schedule so I did a Quick Record to set it but when I go into pending recordings it is now listed twice. Likewise the 7:30 episode on the 20th is not red in the schedule but in the pending recordings it is listed to record.

Regards
David

[sub]

I agree with your logic with the logs. The only problem is that in the schedule they are all marked as new and secondly if I choose to record all episodes on this channel I would expect it to record all episodes irrespective of them being repeats. If I choose record all new episodes that would be a different matter.

It's worth noting, that if NextPVR doesn't know if an episode is a "new" (first-airing) or "repeat" episode, then it's treated as "new". In your case, you're using the DVB EPG, which does not transmit a new/repeat indicator with the EPG, so all episodes have to be treated as 'new' - so "record all episodes" and "record all NEW episodes" are effectively the same thing. If you were using an EPG that did supply this info, then NextPVR would have behaved more like you describe.

Either way though, as described above, it wont bother scheduling re-recordings of shows it already has recorded, pending, or recently deleted.

[Graham]

The only problem is that in the schedule they are all marked as new and secondly if I choose to record all episodes on this channel I would expect it to record all episodes irrespective of them being repeats.

You might be able to get the result that you want by changing "Avoid duplicate recordings where possible" at NextPVR Settings --> Recordings ... http://www.nextpvr.com/nwiki/pmwiki.php?...ding#toc12

[dbfs]

Hi everyone,

Thank you for your assistance. I understand the behaviour a lot better now.

However it doesn't explain why tomorrow's 7:30 episode does not appear as red in the TV schedule to indicate that it will be recorded but it does show up in the pending recording that it will be recorded. I think that this behaviour is one on the reason for my confusion about what is to be recorded.

Regards
David