Hi all, I set the EPG to update at 0300 in nextPVR, but I notice the epg.xml file in the scripts folder hasn't been updated in a while (3 days). The batch file/command should work since I used the same file to generate the epg.xml file in the first place. I attached logs if someone can take a look to see what could be going on. Thank you.
Since around the time I updated my NextPVR software to v4.0.4 (170820), I have experienced program crashes each day. I haven't noticed any pattern to it beyond that. Usually I find the NPVR Recording Service is no longer running, though on rare occasion Services indicates it is still running, but I none-the-less have to restart it to restore proper functionality.
Let me back up a bit to describe my installation. I have NextPVR installed on a Win7 pro desktop which is primarily used for this purpose. I have an HDHomeRun tuner (two tuner model) configured on NextPVR. In another room, where my TV resides, i have a Raspberry Pi with OSMC installed and the NextPVR PVR Client. The remote works fine for selecting recordings for playback, but is lacking in other areas such as being able to delete recordings. So... I'm using a laptop to access NextPVR's web interface for that purpose... I also find it convenient for scheduling recordings.
The symptoms I get that indicate the NPVR Recording Service has shut down include the web interface failing, an inability to play back a recording, or missed records. Strangely (to me anyway), sometimes the recordings are missed altogether, and sometimes they just don't show up in the list, but do after I start the NPVR Recording Service.
There is an error in the computer's Application event log... event ID 1000, source "Application Error". I have attached a text file including a few variations on that error, though most of the time it involves "Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll". It also seems to be NRecord.exe that is reported as the faulting application.
I attached a zipped log file from when I most recently found the NPVR Recording Service not running, as well as another zipped file after i started it. There does NOT seem to be a crash.mdmp file in the temp folder.
Hopefully I have provided enough info to assist in trouble shooting.
Hello everybody idont know if im at the right section but i dont know what else to do please help.
I want to use Npvr to control my haupauge HD PVR 2 With wintv there blast config app does not detect my COMCAST BOX.
So i went ahead and bought a USB-UIRT and integrated it with HIP and it worked It detected my control and chose NPVR as an auto app to start Hip. I Just cant get it to blast. I looked and used hipsend and nothing i used usbuirt.exemade by someone in the Npvr community and nothing now it detects my remote but it does not blast now when the remote is learned i press test send in hip it changes the channel or powers up my box but when i go to NPVR I DONT KNOW WHAT TO DO TO MAKE IT WORK.
Now I know that there was some refernce on The old GPVR FORUMS or Obselete any help would be appreciated thanks.
I recently made the painful switch from Windows Media Centre & Windows 7 to building a new PC with Windows 10. I installed an Hauppauge WinTV HVR-1800 card from an older PC and Windows device manager says the device is working properly.
When I go into the settings for NextPVR and select the devices tab it's listed as Hauppauge WinTV 885. I am using a cable box so I select QAM and run the scan on Default Cable Frequencies, Default Cable Frequencies 70+, and HRC Cable Frequencies and wait for the scan to complete and no channels are listed.
I am using a Shaw Cable digital cable box (ARRIS DCX-32000M) as I need it to decrypt the signal (apparently) and using an HD converter to downgrade the video from the HDMI cable to S-video and connecting that to the tuner card. Not pretty, but it worked on the Windows Media Centre PC.
I tried taking the coxaxial cable from the cable box and connected that to the tuner card and same result: no channels listed.
What am I doing wrong? Do I need to have the WinTV software installed?
I want to try and let my server rest occasionally so I have set up USB drives to boot my PCHs, which work great, but I want to implement WOL to nudge the server. The old posts on how to set this up suggest ether-wake but the link to Martins zip no longer works - any chance I can get a copy from somewhere, assuming that's still the best option.
Cheers for all and any instructions/help.
I rebooted my HTPC at about 14:25 this afternoon. I had updated the firmware level on my HDHomeRun and during that process HDHomeRun detected that NextPVR was using some of its function, and asked if it could stop the NextPRV service. To make sure that there were no problems, I decided to do a reboot of Windows which would restart the NPVR Recording Service cleanly.
With the HDHomeRun firmware change, I thought a test to make sure that NextPVR could still access the tuner was appropriate , so I scheduled a recording from 15:00 to 16:00. The recording was fine. However, after the recording the HTPC didn't enter sleep which I would have expected it to - by 18:05 it was obvious it was not going to sleep. The only thing running on the system is NextPVR and then MCEBuddy from 23:45 to whenever it finishes early in the morning.
Unfortunately, like many Windows 10 users I have encountered the screen flickering problem following Windows sleep after the forced update to the fall 2017 Creators release. Only with a reboot of the system can I again see information on my monitor. So I had to reboot at 16:05 to be able to examine the NextPVR log to see what was going on. Hence the logs containing the times of interest are xxxxxx.log.1
When I examined NPRV.log1 and NRecord.log.1, I discovered that starting at about 16:20 this afternoon the system was going into standby and then waking about 1 minute and 10 seconds later. This is not the first time I have encountered this problem - when I researched the problem earlier this month I discovered that a solution that would prevent the problem was to restart the NPVR Recording Service frequently which I have been doing by rebooting the system.
Today I checked the Windows event log again using a filter I created earlier this month. I found the system is entering sleep due to 'Sleep Reason: System Idle', followed by a system waking message just over 1 minute later. The source of the wake up is 'Wake Source: Timer - NRecord.exe'. This is a repeating pattern with time stamps that closely match the 'System is going into standby' messages in the NPVR.log.1 and the 'Resuming...' messages in NRecord.log.1.
Questions:
1) When examining the NPVR.log.1 it appears that NextPVR is busy processing when Windows thinks the system is idle. After the recording finished shortly after 16:00, I have no idea what NextPVR was doing but it is clearly doing something per the logs until the first standby message at 2017-11-29 16:20:08.723.
2) Why did NextPVR wake the system at 2017-11-29 16:21:16.846 (The event log clearly states that it was a NextPVR timer that woke it).
3) Why does NextPVR and Windows enter a battle of trying to sleep the system and wake it after this first sleep / wake event?
4) Is NextPVR doing useful processing just before the sleep and after the wake? I ask as I don't recall NextPVR doing this sort of processing in other NPVR.logs I have looked at. Is it in some sort of a loop?
5) Is there a setting or another solution to prevent this? This experience tells me that stopping and starting the NPVR Recording Service as suggested by others in the NexpPVR forum is not a long lasting solution - the sleep / wake cycle started to occur only 2 hours after my reboot of Windows and after only one recording had been done.
Note: I have added one file to the LOGS directory under USER/PUBLIC/NEXTPVR/LOGS before zipping it. It is called 'Sleep - wake events ....' and is an extract of the Event Log on Windows containing the sleep and wake events from this afternoon. It can be viewed, including details of each event, with the Event Viewer Snapin from Windows.
Environment: Windows 10 plus fall 2017 Creators Update, NextPVR" version="4.0.4" buildDate="171121"
Electricity has become expensive in the Toronto area, and sleeping the HTPC when there is nothing to do is very important. Today's events suggest the stopping and starting the NPVR Recording Service nightly is not a solution. Since many others have encountered this, finding the root cause and developing a solution is important.
I had a recording failure last night. Checking the NRecord log I found 'Recording due to start pre-padding, but tuner not available'. Please seen NRecord.log.2 at this time stamp 2017-10-27 22:58:00.133 for this repeating message. A subsequent recording 3 hours later worked fine with no intervention by me. However, it too had the tuner not available message until immediately before the show started at 23:00. We didn't know the one recording had failed and the other had succeeded until this morning when I happened to be checking the 'What's New' GUI.
I have attached logs that we zipped this morning.
My OTA tuner is a HDHomeRun Connect with two tuners. What I think the message means is that when NextPVR requested a tuner for recording, the HDHomeRun box responded that no tuner was available - that both tuners were in use. I do know that that this should not have been true - zero tuners should have been in use when NextPVR requested one.
Can someone confirm that NextPVR does not keep track of what tuners are in use, and that it can only find out that there is no tuner available when it requests a tuner. I am trying to make sure that this could not be a NextPVR problem before I open another problem with the HDHomeRun team. This problem happened last spring and it appears to be usage related - after some large number of requests for a tuner, the HDHomeRun says none are available, and a power off, power on cycle of the HDHomeRun initially eliminates the problem, but it will reoccur after many more requests for a tuner.
Sorry to ask for details on how this works, but I am trying to avoid a finger pointer match between NextPVR support and HDHomeRun support with me in the middle.
I am getting pixilated video on all channels for a new service I am trying. Random free IPTV sites look fine. Both services work well in VLC and also plays fine on an AppleTV 4 App.. I have played with all the decoder options but that does not seem to be the issue. The only difference in the two streams is the size and quality of the video. See attached screenshots and the relevant section of the log file. If you want the full logs let me know and I will add them.
I've been having this problem for a while, sporadically. The default recording settings are to stop 3 minutes after the EPG's end time. However, some recordings actually end several minutes before the EPG's end time instead. I haven't been able to determine the problem and no error messages have appeared anywhere. Yesterday, two shows had this problem - "Scorpion" and "A Very Pentatonic Christmas". Looking at the ndigitalhost-20.log.1 I see the start and stop end of these recordings and the stop times are incorrect compared to those shown in the Nrecord.log.1 file, which is correct per the EPG. I hope someone can help me fix this issue.
I am using Kodi 17 to schedule recordings and NPVR 4.0.4 (170820) with 2 Happaugh recorders along with Windows 10 Home creator's update.
I am just starting down the road with NPVR and Kodi as a front-end. However, I find the Kodi interface a bit fussy and I like the cleaner, simpler NPVR screens so am thinking of just using NPVR. BUT, whilst I can get live TV via Kodi, when I try in NPVR, most of the time I get a black screen and no sound, not always, sometimes it works. I have tried LAV and ffshow decoders but still have the issue.
Any thoughts/suggestions would be welcome.
Thanks,
Stanno
