No Devices Scanned

[mvallevand]

It looks like you haven't installed the HDPVR on Win 11. You also didn't answer my earlier question about installing the SiliconDust software

Will I need to switch to the SiliconDust HDHomeRun?

I don't have a clue what this means.

Martin

[jcole998]

You are correct about the HDPVR. I won't be using it on the laptop.

About the HDHomeRun: I meant moving to this device for compatibility with the SiliconDust software. I've run the SD software and got the following results pictured below. I wrote to SD about it and they simply said their software is imcompatible tihe the Hauppauge DCR-3250. I understand this is to install BDA drivers. Do I have that right?

JohnC

[mvallevand]

I don't know enough about these devices to answer and I don't know why v4 works on the same machine.

Does the old protocol find your device?

"C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe" discover

From your previous posts you have trouble with HDHR mode in V5 because of TCP issues and ultimately that is is the problem not V5 itself. I don't believe it is a widespread problem with the Hauppauge DCR tuners.

Martin

[jcole998]

I've done more hacking by uninstalling HDHomeRun software and installing the version I use on my desktop with V4. This produced HDHomeRun VIEW on the desktop so I tried it. To my surprise it found and started viewing WCBS-DT perfectly! I took it a step further and was able to start two more instances of VIEW each playing a different HD channel. All three tuner LEDs were lit.

I then tried "hdhomerun_config.exe" discover:

C:\Program Files\Silicondust\HDHomeRun>hdhomerun_config.exe discover
hdhomerun device 20200EC0 found at 192.168.1.155

My laptop showed the network media it found so the Hauppauge device is there. See below.

Regarding my previous posts, I can  only guess that my desktop cannot keep up with TCP protocol of V5. I'm hoping my much newer laptop can handle the load...if I can get V5 to work. V4 works just great and is very reliable. But with streaming catching on, I'd like to get the "-extra" devices back.

I'm hoping there is more we can try.

JohnC

[mvallevand]

I'm hoping there is more we can try.

Are you saying NextPVR is still not detecting your device after restarting the service?

Martin

[sub]

I wonder if nrecord.exe is being blocked by your firewall. It sends a udp broadcast on port 45000 on each nic device to discover HDHR/DCR style devices

[jcole998]

Martin: Still no devices after web app startup. Logs attached.

I've looked at what Win11 presents after searching "Firewall." below screen captures show what presented:
- Initial window listing the NextPVR* apps
- Details of the top NextPVR entry
- Details of the other NextPVR* entries

I'm not sure what I'm looking at but if these snapshots don't help, I can try to dig some more.

Sub: You mentioned port 45000 may be blocked. Wouldn't that block affect V4 setup? V4 works fine.

JohnC

[mvallevand]

I would disable the firewall to be sure and I will step aside and let sub diagnose the NextPVR issue.

Since command line discovery workedyour extra should run with the older hdhomerun_config Test your batch file outside NextPVR to confirm.

Martin

[sub]

Sub: You mentioned port 45000 may be blocked. Wouldn't that block affect V4 setup? V4 works fine.

Windows keeps per-process rules on what processes can access network, and which aren't, so it would have been easy to have a v4 that was allowed access, and a v5 that wasn't.

[sub]

The application that needs to have access is C:\Program Files\NextPVR\NextPVRServer.exe