No HDHR tuner connection on system start

[othello]

One more step towards autonomous bliss. This new NextPVR is now starting up before Kodi and it's green but the tuners aren't there.
NextPVR console shows all of my HDHomerun tuners as "unavailable" and trying to start a stream with the client gets the dreaded "Unable to find available capture device"
and the Web client shows "failed to start requested stream" error.

This will continue until I restart the NPVR service. Once restarted everything works and Kodi is happy.
Windows 10 Pro on NUC10i7FNH and fresh NextPVR install.

Attached the cold start logs.

[mvallevand]

You can't have it both ways. Although I have asked sub to change the logic, NextPVR doesn't retry when it launches before the network is available and can't connect to the HDHR. His solution is to use delayed start.

You can use delayed started and then see if you use NextPVR scripts to launch Kodi if that is your main concern.

Martin

[othello]

Not intending to whine about it but, no wait yes I can whine about it. This did not happen with NextPVR 4. It was quite solid no matter how flaky Kodi got.
I use the Launcher4Kodi to start up Kodi. I tried making it wait for a bit but this gets very tricky and annoying having to now wait several minutes for NPVR to catch up.
I guess I have some decisions to make before my hard drive for recordings arrives.

[mvallevand]

I don't support whiners it isn't productive.

Martin

[sub]

Not intending to whine about it but, no wait yes I can whine about it. This did not happen with NextPVR 4. It was quite solid no matter how flaky Kodi got.

In theory it's exactly the same as v4. It could also try to use a network tuner before the network was up.

Were you using the HDHR or DVB/ATSC style device on v4? It's possible the latter has some different behaviour to HDHR - I'm not sure if SiliconDust implement some sort of delay or retry in their BDA drivers.

[sub]

Does the problem only happen on a reboot, or does it also happen on wake from standby?

I'll look at putting a fix in, but want to make sure I understand the problem correctly first.

[sub]

You could see if this updated NShared.dll helps, at least for the on-reboot scenario.

[othello]

The problem happens only on reboot. If the service is set to Automatic then it starts quick but won't see the HDHR tuners. (HDHR, not ATSC) If the service is set to Delayed Start then Kodi will fail to connect to the NPVR backend unless the auto-start is set to wait up to 2 minutes, and Kodi has a similar problem to NPVR that it won't retry a failed plugin. When both NPVR and Kodi are working hand-in-hand (like in v4) then you get that clean worry-free appliance feel. I never even saw my desktop unless I exited Kodi.

I just tried your updated NShared.dll file. Shut down service, replaced file, restarted computer to test. No change in behavior, the tuners are still marked "unavailable" on the browser admin client.
But I thank you profusely for the effort to help.

[mvallevand]

Could you send the log again to help sub out?

There seems to be something quite odd in your startup since Kodi tries to connect to NextPVR for 30 seconds after it starts, it would be interesting to see an Kodi debug log.

For Matrix I can see probably add a setting to wait longer for startup.

Martin

[sub]

Yeah, I'll definitely need to see the logs. Please use this slightly later NShared.dll though:
https://forums.nextpvr.com/showthread.ph...#pid541550