send channel chanes via winLIRC??

[mvallevand]

You'd need to post the zipped logs. It should blast once per digit. Sub did post {channel_d2} {channel_d3} {channel_d4} for three digits so if that is what your box uses that is what you need.

Sub also explained that the command line doesn't work from NextPVR because of the clipboard. This script simply uses tcp like the AutoIT script.

Martin

[chef Paula]

I took out the {channel_d1} and that seems to be blasting 3 correct digits. I need to thoroughly test with all of my channels, but seems to be sorted

Once again, a huge thank you to the guys who all chipped in to help out

[chef Paula]

Interestingly enough, after a lot of channel changing, i realised that the 0 & 1 key blasts weren't always being recognised by the STB. So, in my winLIRC config file, i changed the "Key_0" &" Key_1" codes back to the slightly dodgy looking "Key_0" & "Key_1" codes from my original (obviously botched) winlIRC config file, and that seems to have improved, ie: that stb now seems to receive the 0 & 1 digits more reliably. (Although, at this point "seems" is the word, needs more thorough testing to be sure.).
I can't tell why this is, as those 2 codes are slightly longer than the codes for the rest of the remote keys, and look a tiny bit out of place.

[chef Paula]

also, I'm gonna be copying this config over to my dad's HTPC tomorrow (he has the same STB and software setup as myself), so i'm hoping i can just copy all the NextPVR config from my machine to his, import my exported HDPVR -channels.xml file in the NextPVR Sevice settings page, and put the WinLIRC and drakeblast files in the same locations that i have them working in (same folder paths etc.).
However, his machine is Win10 Pro whereas mine (for now) is still windows7 Pro.
so, i guess i should ask, Is the poweshell script likely to work the same under win10?

Once again, thanks very much for any replies/help/pointers

[mvallevand]

The powershell script won't have any trouble on Win10 assuming no antivirus or firewall blocks the IP. Hopefully you decide to use V5 not V4.

Martin

[chef Paula]

Ok thanks for that. I'll head up there with all my files on a USB tomorrow.
Yea, i might give NPVR5 a try, i just wanted to get the migraion from old stb to new and get the blasting all set with my current version of NextPVR before trying to upgrade.

Thanks

[chef Paula]

So, lol, i went to my da's today, very carefully copied my NPVR config files, made sure that i have cooied the WinLIRC config exactly, ensured that i can successfully change the stb channels from the command lline using the drakeblast powershell script. so far so good. so i opened NextPVR, and attempted to view channels. Unfortunately, no blasting is happening whatsoever. I deleted the setup channels in NextPVR's device settings, carefully re-imported the channels xml for the HDPVR device, checked that for each channel, the blasting config is the same as mine (same executable path to Powershell.exe, and checked that this path is valid, it is), checked that the arguments line is exactly the same as on my working setup, saved the channel settings, went back to NextPVRR Channel list and changed channel lots of times, again no blasting is happening. (NextPVR does receive picture & sound from the HDPVR2, just doesn't chnage the STB channel).
I'm 100% confident that the only difference between our 2 setups is the OS version (win10 as opposed to win7), i've confirmed that i can blast any combination of digits from command line using the powershell script. But NextPVR just isn't blasting anything. (no red flashes from the IR emitter at all, unless i do it from command line).
Assuming that it could be firewall blocking the TCP port, i've tried it with Eset's firewall completely disabled, no difference.
Any ideas?
I've included a log file that shows a couple of minutes worth of me opening NextPVR, and changing channel a few times (with the blasting not happening).

Thanks for any help/tips or pointers that anyone can give

[mvallevand]

Did you try testing outside of NextPVR first? I believe you were adding some other parameter to enable powershell before.

Code:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -File C:\winLIRC\Drake.ps1 1 2

Martin

[Graham]

I've included a log file that shows a couple of minutes worth of me opening NextPVR, and changing channel a few times (with the blasting not happening).

nrecord.log has this ...

2021-01-28 15:22:59.732 [DEBUG][8] About to tune graph to:
<tuning>
  <type>HDPVR</type>
  <locator>
    <channel>777</channel>
    <input>3</input>
    <audio_input>HDMI Audio Input</audio_input>
    <blaster_executable>C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe</blaster_executable>
    <blaster_args>-File C:\winLIRC\Drake.ps1 {channel_d2} {channel_d3} {channel_d4}</blaster_args>
  </locator>
</tuning>

The log shows what NextPVR is doing ... it might be that you can diagnose the problem from the log.

And I expect that someone more helpful than me will be along soon ...

[chef Paula]

Did you try testing outside of NextPVR first?  I believe you were adding some other parameter to enable powershell before.

Code:

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -File C:\winLIRC\Drake.ps1 1 2

Martin

Yes on that machine, i can confirm that blasting works perfectly from command prompt and from a powershell command prompt.  Powershell is enabled on that machine. (win 10 machine, on which powershell was active already, and didn't need powershell scripts to be enabled)