NPVR Stopped working, but in a different way...

[volfin]

As of yesterday 3/15, Everything was working fine, and has been working fine for awhile now.

But then Today (3/16) Windows 10 had an update, KB3150513, which states it's an update to Compatibility definitions. But now after this update, I don't get any Video recorded.

My setup is a Ceton InifiTV 4, connecting to NextPVR using the DRI Interface. The Ceton reports everything is fine, and NPVR behaves as if everything is fine. But any attempt to record a show, or watch Live TV, just presents a black screen. There's no error messages, or failures or crashes. Just Black screen.

I wish it was the type of failure reported elsewhere, because at least there's a solution. but I'm really at a loss since there's no errors to point me in any direction.

[volfin]

Further Info. I installed SageDCT since it has a "Test" recording tab, and recording a file with that, works fine. So tuner is definitely working. Looking at the Tuner webpage when SageDCT is recording and when NextPVR is showing a black screen, the main difference I see is, SageDCT has set the RTP protocol to "Started" but with NextPVR, it's still set to "Stopped". Channel parameters seem to be set up though. So it's like it's got everything set up, but just not set the tuner to start streaming. I Tried uninstalling KB3150513, but no change, so now I'm unsure what the cause is. I can't try swapping CompPkgSup.dll, the O/S says it belongs to "TrustedInstaller" and refuses to let me overwrite it.

Update 2: I managed to get CompPkgSup.dll replaced, but that didn't fix this issue. I guess it's unrelated. I'll just go back to using Network Recorder, it seems to work.

[sub]

If you do a recording. Do you get a file with a normal looking size, or 0 bytes?

[yazrichards]

I am having similar issue with Windows 10 Version 1607 for x64-based Systems (KB4013429) this update from Microsoft has basically disabled all playback and recording. I uninstalled the update and everything appears to be working again.

[volfin]

its zero byte.

[sub]

And when you bring up the Ceton web interface when it's trying to do one of these recordings, what is it reporting is happening?

I wonder if something like the device IP address has changed or something, and it's confusing NextPVR. You'd probably find deleting the channels and rescanning for them, will fix the issue.

[volfin]

the web interface shows the correct channel tuned, and the program selected, and the frequency seems right. But it just never starts it playing. The ports seem to be the same they've always been. It's very puzzling.

I set up the NetworkRecorder and merged the 4 Network devices into the same channel listings as the 4 DRI devices (so it sees 8 sources for those listings). That way the one set guide listings works for both sets of devices. I can disable the DRI devices and use NetworkRecorder, and all is fine. But if I disable the NetworkRecorder devices and use DRI, the issue persists. So, for now I'll just use NetworkRecorder.

[sub]

If you want to post the logs, I'll take a look.

If you disable your firewall temporarily, does make any difference?

[volfin]

Ok I think we're onto something. I disabled the Firewall, and it started working again. Re-enabled it, and it stopped again.

I'm not sure what is wrong then. I see NextPVR and NRecord records on "Incoming" but not on "Outgoing". I tried adding them to "Outgoing" but no change.

I turned on logging and I see:

Code:

#Fields: date time action protocol src-ip dst-ip src-port dst-port size tcpflags tcpsyn tcpack tcpwin icmptype icmpcode info path
                                                                                                                                                                                                                2017-03-19 18:22:32 DROP UDP 192.168.200.1 192.168.200.2 43012 17240 3988 - - - - - - - RECEIVE
2017-03-19 18:22:32 DROP UDP 192.168.200.1 192.168.200.2 43012 17240 3988 - - - - - - - RECEIVE
2017-03-19 18:22:32 DROP UDP 192.168.200.1 192.168.200.2 43012 17240 7936 - - - - - - - RECEIVE
2017-03-19 18:22:32 DROP UDP 192.168.200.1 192.168.200.2 43012 17240 7936 - - - - - - - RECEIVE

192.168.200.1 is the Ceton, so it's source.... ah that's what must be missing a rule for the card. Or something, I don't know how to add a rule for a network device. o.O

[sub]

Ok I think we're onto something. I disabled the Firewall, and it started working again. Re-enabled it, and it stopped again.

That's great. At least we've narrowed the problem down significantly.

Do you have a firewall exception set up for NCableCardHost.exe?