Upgrading from NPVR4 to NPVR6

[sub]

ie, if you open a command prompt and run the following, does it change channels?

"C:\Program Files (x86)\NPVR\HaupBlast.exe" 13

[mlopez1007]

2022-09-25 14:25:52.601 [INFO][4] Running blaster: C:\Program Files (x86)\NPVR\HaupBlast.exe 13

Is that path correct? I've added logging for the next build so that I can tell from the logs if it exists or not (which is currently not logged in the build you're using).

Also, if you run the Hauppauge BlastCfg app, is it configured for the correct set top box, and able to send numbers? The HaupBlast.exe utility just tells BlastCfg to send number x, and BlastCfg takes care of the details of blasting, and the type of set top box signal etc.

That path is correct. I've also tried ‪\Program Files\NextPVR\HaupBlast.exe. 

BlastCfg is configured for the proper set top box. Running a simple test off that program will trigger the blaster to change the channel. I see the blaster blink red, and I have confirmed that the channel does change. 

Additionally, the blaster works just fine in NPVR V4.

It seems as if haupblast in V6 just isn't really talking to the blaster, where as V4 has no issues.

[sub]

It seems as if haupblast in V6 just isn't really talking to the blaster, where as V4 has no issues.

NextPVR doesn't talk to the blaster itself. It just runs HaupBlast.exe with the correct parameters.

I've attached an updated DeviceHostWindows.exe. Replace your existing file with this new one. Reproduce the error, and post a new set of logs. This one logs more info around running HaupBlast.exe.

[mlopez1007]

ie, if you open a command prompt and run the following, does it change channels?

"C:\Program Files (x86)\NPVR\HaupBlast.exe" 13

It does change channels.

[sub]

As mentioned above, replace your DeviceHostWindows.exe with the newer one, and capture some updated logs for me.

[mlopez1007]

As mentioned above, replace your DeviceHostWindows.exe with the newer one, and capture some updated logs for me.

Here you go.

[sub]

Are you sure you replaced the DeviceHostWindows.exe with the new one? I can't see the new logging I added. It looks like it's still the old one.

[mlopez1007]

Are you sure you replaced the DeviceHostWindows.exe with the new one? I can't see the new logging I added. It looks like it's still the old one.

I did. After that reply, I restarted the NPVR service for good measure. An updated log is provided.

[sub]

2022-09-25 16:51:25.138 [INFO][5] Running blaster: ‪C:\Program Files\NextPVR\HaupBlast.exe 4
2022-09-25 16:51:25.138 [INFO][5] blaster executable not found

The logging is there now.

There must be a slight difference to the name or path. The HaupBlast.exe file is not found in the location it's looking.

ie, check "Program Files" vs "Program Files (x86)", and "NextPVR" vs "NPVR" etc.

[sub]

The funny thing is that your earlier example used a different path, so I suspect you've got some channels set differently to other channels.