NextPVR Refuses to record football games that start at the same time

[johnsonx42]

yes, I did my testing with the NFL games just to be exactly consistent with the OP's issue, not because I ever thought it had anything to do with NFL; I'm sure I could've re-produced the issue with any number of shows. Though there was a moment when I first saw that the FOX game had the unexpected "SH" unique_id where I thought that might be the problem, but that quickly proved not to be the case.

[guyinco6nito]

Hello,

I applied that patch but I'm sill seeing the same problem. I've attached my logs.
Thanks,
-guyinco6nito

I'm not sure if this is the right log file, or how to mark it as code, but this might be relevant:

2018-11-11 03:00:13.942 [INFO][10] UpdateRecurringRecording(95, 'NFL Football'):
<Rules>
<ChannelOID>0</ChannelOID>
<ChannelName>All Channels</ChannelName>
<StartTime>2018-09-23T17:00:00.0000000Z</StartTime>
<EndTime>2018-09-23T20:25:00.0000000Z</EndTime>
<PrePadding>1</PrePadding>
<PostPadding>80</PostPadding>
<Quality>0</Quality>
<Keep>0</Keep>
<AdvancedRules>title like &apos;NFL Football&apos;</AdvancedRules>
</Rules>

2018-11-11 03:00:14.035 [DEBUG][10] LoadListingByAdvancedRules(channel='all channels',advancedRules=title like 'NFL Football')
2018-11-11 03:00:14.098 [DEBUG][10] - Potential episode at: 11/11/2018 12:00:00 PM
2018-11-11 03:00:14.098 [DEBUG][10] ...check IsValid()
2018-11-11 03:00:14.098 [DEBUG][10] ...scheduling episode
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@1
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@2.0
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@2.1
2018-11-11 03:00:14.098 [DEBUG][10] CaptureSource.LoadAll()
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@2.2
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@2.2
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@2.2
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@2.2
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@2.2
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@2.3
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@2.4
2018-11-11 03:00:14.098 [DEBUG][10] ScheduleRecording@3
2018-11-11 03:00:14.113 [DEBUG][10] ScheduleRecording@4
2018-11-11 03:00:14.113 [DEBUG][10] ScheduleRecording@5
2018-11-11 03:00:14.113 [DEBUG][10] - Potential episode at: 11/11/2018 12:00:00 PM
2018-11-11 03:00:14.113 [DEBUG][10] ...check IsValid()
2018-11-11 03:00:14.113 [DEBUG][10] ...already got this episode scheduled

[johnsonx42]

All I can surmise is that you somehow failed to actually get the patched file in the right place, so you're still using the original code. The updated code definitely resolves this situation, I've tested it.

[guyinco6nito]

That's very possible, I couldn't find any notes for how to apply hotfixes. Here's what I did:

-Shutdown service
-Rename the NShared.dll (908KB) file at C:\Program Files (x86)\NPVR\ to NShared.dll.old
-Copy over the new NShared.dll (913KB) from the zip archive to that same path.
-Start the Service
-Launch the GUI
-Delete and recreate the recording job.

Unless I missed something, maybe I'll just wait for this hotfix to be incorporated in another update.
Thanks much!
-guyinco6nito

[mvallevand]

I'm not aware of any bugs in the application that could account for what you're describing, so I'm pretty sure there is a good reason why it's happening. ie, either you've recently recorded that same game so it doesn't want to record the replay, or you don't have enough tuners available so it results in a conflict.

Based on the logic sub described if your guide data is stale or bad you can miss recordings. SD uses a generic id for games until local programming is finalized.

Martin

[johnsonx42]

That's very possible, I couldn't find any notes for how to apply hotfixes. Here's what I did:

-Shutdown service
-Rename the NShared.dll (908KB) file at C:\Program Files (x86)\NPVR\ to NShared.dll.old
-Copy over the new NShared.dll (913KB) from the zip archive to that same path.
-Start the Service
-Launch the GUI
-Delete and recreate the recording job.

Unless I missed something, maybe I'll just wait for this hotfix to be incorporated in another update.
Thanks much!
-guyinco6nito

that's the correct sequence, but somehow you're still running with the old NShared. I don't know how. I do believe another 4.2.x release is coming sometime soon (I don't know exactly when, nor would I be willing to say if I did) so if you're content to wait a bit you can see if a full install solves it.

[johnsonx42]

I do believe another 4.2.x release is coming sometime soon (I don't know exactly when, nor would I be willing to say if I did)

apparently by "soon" I meant exactly 1 hour and 40 minutes later.