Hi
Is there a posibility to set two or three Automatic EPG Update - times per day.
It would very helpfully!

Thank you for your help!

kfmf

Hi, Longtime user of the program.  The one pain I've consistently had is the babysitting of OTA channel tuning updates and remapping these when they frequently change, and the playback loosing its place to seek around when watching live TV that isn't being 'recorded'.

Now, there's a new issue and I'm stumped: after rebooting my computer, the TV Guid can't find any of my channels guide information from the xml file from zap2xml.  Looking at the problem in more detail, it looks like NPVR is only seeing the numeric display-names from the XML file, when it used to capture and display the first display-name for each channel.

I've searched the settings and can't find one which lets me specify whether it uses fir first or last display-name entry for each channel.  Can anyone describe exactly how NPVR chooses which display-name to use, and how I can get deterministic control over this?

Examplea channel entry:
<channel id="I2.2.206506510.microsoft.com">
<display-name>102 MeTV</display-name>
<display-name>2.2 KATUDT2</display-name>
<display-name>2.2</display-name>
<icon src="https://zap2it.tmsimg.com/h3/NowShowing/62792/s70436_h3_aa.png" />
</channel>


it should be seeing and using 102 MeTV, but now, after no apparent changes that I've done, it's using 2.2 instead.

Attached Files

Thumbnail(s)
   

I've been fiddling with xmltv with and without FreeGuide, and it dawns on me that these are fairly old approaches that may have worked for DTV in North America, but I can't find an easy way to generate an xmltv file for use with NextPVR 5.  Apart from embedded epg info, am I missing something, or is the only really viable alternative Schedule Direct? Thanks for putting me out of my indecision and ignorance.

Hello,

I've spent this evening messing about with codecs as I've had occassional glitches since moving to a new machine.  I've now discovered that the glitches are in the recordings.    Confirmed using VLC I see the same glitches at the same points in time.

I'm 99.999% sure this is not a signal issue, as I have a good strong signal and in the last 11 years of my old HTPC using a Nova-T Dual, it would be absolutely exceptional to see a glitch in a stream.  In fact, I can't recall a case in recent history when that has happened. Sadly the new PC has no PCI slots for the old tuner.

I've updated to the latest drivers, it's Windows 10.  Not sure if there's much I can do but any tips appreciated. 

Failing that, recommendations for a rock solid tuner? 

Thanks for your help!

Hello,

Just wondering what the current thinking on remote controls is.  I have been using a Hauppauge remote and the built in receiver for over a decade (Nova-T, Win 7), but since upgrading to a new machine with a Hauppauge WinTV quadHD (and Windows 10), I'm noticing the remote can be a bit erratic.  It works great when it does, but sometimes it just stops taking commands until I restart IR.exe.  It's not as rock solid reliable as the old system.

I'm wondering what would be the recommended alternative to this?

Are there any USB IR receivers that I could programme to work with my Hauppauge remote?  Do they work well?

Thanks

I finally bit the bullet and got two SiliconDust HD HomeRun 3 channel tuners to replace my Ceton board so that I could upgrade to NextPVR 5 on Windows 10 Pro 20H2.

The problem now is that when I go to configure NextPVR it only sees the non-premium channels (i.e., those with DRM enabled such as HBO, Showtime, Smithsonian, etc.).

The HD HomeRun configuration utility sees everything as does their HomeRun client, so it is configured and ready to go.

What do I need to do to get NextPVR to see the premium channels?
.tb_button {padding:1px;cursor:pointer;border-right: 1px solid #8b8b8b;border-left: 1px solid #FFF;border-bottom: 1px solid #fff;}.tb_button.hover {borer:2px outset #def; background-color: #f8f8f8 !important;}.ws_toolbar {z-index:100000} .ws_toolbar .ws_tb_btn {cursor:pointer;border:1px solid #555;padding:3px} .tb_highlight{background-color:yellow} .tb_hide {visibility:hidden} .ws_toolbar img {padding:2px;margin:0px}

I watched a show in bed last and had this problem happen again. This time I got logs.

The RPi on the living room tv (192.168.143.26) was running Kodi & knewc and was in NextPVR on the recordings list. I used the bedroom one (192.168.143.24), launched knewc, watch a recording, and then used the NextPVR main menu option to Exit. It took me back to the Kodi menu fine. Then when I went back to the living room Pi later, I found that it was also back at the Kodi menu. As I mentioned in the other thread this seems to be happening regularly now.

Logs can be found here. The kodi debug log from the living room client is in there and shows (I think) that it got an "exit" command from the server at 21:20:02.058:

Merry Christmas to all.

It's already Christmas morning here in New Zealand. I'm up early, soaking in a bit of quiet before the rest of the family wakes and the Christmas chaos hits.

Hello,

Got an unusual one.  I finally completely moved machine from an old Win 7 based one to a brand new Win 10 one (all new hardware).  I went from a Hauppauge Nova-T Dual Tuner to a Hauppauge quadHD.  Mostly everything working as I expect.

The one big difference is the Windows screensaver.  I use the system screensaver as the PC also gets used for browser stuff (Youtube etc) and it's a plasma TV, so seems sensible to have a system screensaver.  In other words, I can't rely on the NextPVR native screensaver.

On my old machine (Win 7), the Hauppauge IR.exe calls NextPVR.  If the system screensaver was on, the Hauppauge IR.exe call to NextPVR seemed to clear the screensaver.  

On Win 10, if I launch the screensaver as a preview or from it's *.scr file, then the above behaviour works entirely as expected.  However, if the system launches the screensaver (because it has been idle), then IR.exe won't close it.  It is still able to call and execute commands, but they all appear behind the screensaver.

As a workaround, I've used 'pskill' and mapped it to a button to kill the screensaver, and this works.  It seems rather inelegant though.  Killing the process seems a brute force method.  I am guessing the issue must be one of privileges or permissions, that when the system launches the screensaver it is elevated.  Maybe not.  I'm not sure!

Just wondering if this has been encountered before?  Any thoughts appreciated.

Thank you

I installed NextPVR in my Win 7 pc and after I first configured it in the local host, it was working, albeit with some minor picture breakup/pixelation in the channels I tuned into.  I closed the application and when I tried to open it back up, the following message popped out:

"Cannot start service from the command line or a debugger.  A Windows Service must first be installed (using installutil.exe) and then started with the ServerExplorer, Windows Services Administrative tool or the NET START command."

Up until a week ago I had NextPVR installed in a Win 10 pc, and I didn't have any problems there, until that pc crashed altogether.  I'm suspecting that the root of my problem now is that I went from one pc with an Win 10 OS to another one with a Win 7 OS.  Any input that can help me in finding a solution to this issue would be greatly appreciated.