Blaster Options?

[ddaggett]

I'm having issues in V5 with the Blaster Executable Path. I'm recording from a Dish STB using a Hauppauge Colossus 2 card, and it doesn't always accept the IR signal the first time. For example, if the STB was in "sleep" mode, it appears that the first part of the IR signal wakes the STB and then the STB is awake but does not select the right channel. This apparently is not that uncommon, and I found a fix to it online that worked with NextPVR V4. Basically, the fix was to call a cmd file, instead of HaupBlast.exe, and the cmd file ran HaupBlast.exe, waited a few seconds, then called it again, then waited a few seconds, then called it again. With this fix, the STB became 100% reliable on a channel change.

When I upgraded to V5, inputting the name of the command file instead of the .exe file doesn't appear to work. Should it work? If so, is there different syntax I need to use within the NextPVR V5 UI? If this is not something that currently works, is there a way to add it to NextPVR V5? Thanks!!!!

[sub]

If you want to post the logs, I'll see if there is any errors noted when trying to call your cmd file.

For work around, you can always use "c:\windows\system32\cmd.exe" as the executable, and "/C c:\path\to\blaster.cmd {channel}" as the arguments.

[ddaggett]

Thanks. I'll try both. Quick (probably stupid) question - I know in V4 there was a way to change details for channels (e.g., to change the what video and audio were being used) without clearing the channel list and starting over. Is there a way to edit that information for the current channel set, so I can change the blaster command and arguments without deleting everything and starting over? Thanks again!

[sub]

No not at this stage. I will be adding something like this.

[shspvr]

I'm having issues in V5 with the Blaster Executable Path. I'm recording from a Dish STB using a Hauppauge Colossus 2 card, and it doesn't always accept the IR signal the first time. For example, if the STB was in "sleep" mode, it appears that the first part of the IR signal wakes the STB and then the STB is awake but does not select the right channel. This apparently is not that uncommon, and I found a fix to it online that worked with NextPVR V4. Basically, the fix was to call a cmd file, instead of HaupBlast.exe, and the cmd file ran HaupBlast.exe, waited a few seconds, then called it again, then waited a few seconds, then called it again. With this fix, the STB became 100% reliable on a channel change.

When I upgraded to V5, inputting the name of the command file instead of the .exe file doesn't appear to work. Should it work? If so, is there different syntax I need to use within the NextPVR V5 UI? If this is not something that currently works, is there a way to add it to NextPVR V5? Thanks!!!!

You disable sleep mode

[ChrisHammond56]

I am loving the new v5, and I am running in a DOcker on a Synology (DS918+). Everything seems to be working except i cannot find the GUI settings to provide the PreTunung batch file like i used to have on the Windows NextPVR v4. Is this available on the V5 for a Docker install.

I have already converted my windows batch file into Bash/Python so would need to be able to execute a Bash script.

Thanks

[mvallevand]

I am loving the new v5, and I am running in a DOcker on a Synology (DS918+). Everything seems to be working except i cannot find the GUI settings to provide the PreTunung batch file like i used to have on the Windows NextPVR v4. Is this available on the V5 for a Docker install.

I don't know if IPTV  (which sadly I have to assume you are using since you didn't provide logs) supports a blaster in v5.

Martin

[sub]

I am loving the new v5, and I am running in a DOcker on a Synology (DS918+). Everything seems to be working except i cannot find the GUI settings to provide the PreTunung batch file like i used to have on the Windows NextPVR v4. Is this available on the V5 for a Docker install.

I have already converted my windows batch file into Bash/Python so would need to be able to execute a Bash script.

Thanks

What type of tuner are you using?

[ChrisHammond56]

Thanks for responding so quickly. I should have elaborated....

For hardware, I am using a local sat receiver with a TBS-2603 encoder (HDMI-HTTP stream). I am running Emby on a Synology NAS (DS918+) and using a VM for Windows 10 NPVR (same NAS). I also have a Broadlink IP Remote IR Controller for changing channels which is driven by Python

In my current v4 install on Windows 10 VM (working setup) I use NPVR to add the TBS as an IPTV source multiple times for each channel that I require (lets say channel 118 for ITV2 HD, 119 for ITV3 HD Etc). I then use the pre-tuning batch file capability to call a script that has the {channel} number. The script takes the channel number and 'process' the keys required for the Broadlink IR remote into python and executes, and this changes the channel on the sat receiver.

I have already converted the DOS batch file I use to BASH so that I from a command shell in the Docker container, change the channel (this is also working).

So, in v5, i just need the original capability of running a pre-tuning script for my channels the same as in v4, however, I cannot seem to find where that is (referenced in this thread earlier). I effectively need this capability:

<executable>./volume1/Emby/scripts/BroadlinkChannelChange.sh</executable>
<args>{channel}</args>

This is an excerpt of my exported channel config from my v4 install

<Channel>
<Name>ITV2 HD</Name>
<Number>118</Number>
<ServiceType>1</ServiceType>
<tuning>
<type>IPTV</type>
<locator>
<source>http://192.168.xxx.xxx:8080/tbs</source>
<executable>C:\Users\Public\NPVR\Scripts\BroadlinkChannelChange.bat</executable>
<args>{channel}</args>
</locator>
</tuning>
<EPGSource>Schedules Direct</EPGSource>
<epg>
<source>Schedules Direct</source>
<station>69228</station>
</epg>
</Channel>
<Channel>
<Name>ITV3 HD</Name>
<Number>119</Number>
<ServiceType>1</ServiceType>
<tuning>
<type>IPTV</type>
<locator>
<source>http://192.168.xxxx.xxxx:8080/tbs</source>
<executable>C:\Users\Public\NPVR\Scripts\BroadlinkChannelChange.bat</executable>
<args>{channel}</args>
</locator>
</tuning>
<EPGSource>Schedules Direct</EPGSource>
<epg>
<source>Schedules Direct</source>
<station>69374</station>
</epg>
</Channel>

[mvallevand]

It looks like that would be pretty easy implement as an extra in v5. Try creating a script that does

Code:

blastercmd $1
#add brief wait if neccessary
curl -s http://192.168.xxxx.xxxx:8080/tbs

then test this script with a channel number

./test.sh 123 | ffmpeg -i pipe: -f mpegs /dev/null

or view it with

./test.sh 123 | ffplay -i pipe: -f mpegs

If those work I can help you create the extra

Martin