For some reason I have had poor luck running any version of NPVR since 3.9. Any of the newer versions have not time skipped correctly, even with the patch files. I managed to get it to function better by checking the box to use legacy TSreader, but even then it would occasionally freeze during playback and would have to ctrl-alt-del to kill it. NPVR record service would occasionally stop and miss some shows also. Do you think it is a hardware issue on my aging win10 computer? Perhaps the video card, since it is now in legacy status and AMD is no longer making updated drivers for it?
I'm running Win10 x64 Pro V1703
AMD Phenom II X4 3.2ghz
8gb ram
AMD Radeon HD 6670
Avermedia A188C tuner cards
Between 1700 and 1830 on 11-23-2018 I was watching Lucifer and the system hung and NextPvr locked up. Had to kill it using task manager then restart. Did it a couple of times hung in the same place. Sometimes occurs randomly, but most of the time it works great. Attached are the logs.
I have a Radeon 7870 2GB GPU with default clocks at 1100 GPU/1250 Memory running the latest AMD drivers with WIN10 64-bit. When the system is idle the GPU runs at 300 and memory at 150 clocks. Whenever I start a live TV feed in NextPVR the GPU clock goes to 1000 and memory to 1200. After closing NextPVR the GPU drops back to 450 but memory stays at 1200 permanently and when running other video apps or games memory stays at 1200 and GPU goes back to only 1000. I'm unable to change the clocks even with AMD overdrive and have to restart my system to get the clocks to act normally again. Any idea what is going on with this?
I just recently noticed that the "new" tag shown of the TV Guide doesn't show up on a client. Only the "Prem" tag. Guide on the server shows everything nicely. Is their a folder involved that I may have clobbered?
The area around the back of my TV is a veritable mass of cables; HDMI, Ethernet, Google Chromecast, even some old RCAs.
The worst issue though is the Power Bricks on 8 or 10 plug extension boards. Horrible.
Has anyone tried to use PoE with a splitter to power e.g. the PCH-A110 (12V, 3A, 2.5mm Centre Positive, OD 5.5mm/ID 2.5mm).
Or any other of the Client Boxes out there? I know you might be replacing them with PoE Splitters which are ugly too but I could at least hide these close to the devices. My server lives upstairs, wired Ethernet cable (Cat. 5E) down through the wall.
I also have a 5 port umanaged switch (Linksys G205) [Power 12W max. and 12V @ 1.0A DC input Power consumption (max) GS205: 3.56W]. Would PoE run that too?
If so do folks have 802.311at Switches/Injectors? Or the lower Power 802.311af ones?
I am looking at a small project that would likely see NPVR used with abotut 3 Hauppauge HD PVR Rocket (USB things). I use KODI normally, however it seems kinda redundant to use NPVR to capture the streams then stream it to a KODI client when i could just use NPVR as the server and client(s).
However this raises a question about skinning, can i show a capture source in a "section" on the skin, playing, like a smaller window somewhere. Ive posted a beta design image, your see the section to the right (lighter color), the location i would want the media playing from one of the above HDPVR Rocket units.
Hi, NPVR used to be listed on Hauppauge website as a support PVR, however there appears to be another Australian company now (Capture4ME)... did something happen?
Why is it that I get this error when trying to connect my browser to 192.168.1.5:8866?
Code:
Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
OK thanks to you all, I got it working.
Thought I would throw this here on my steps how I got it to work as I am new to this and was totally lost for the most part.
I did however, already have my HDHomerun Prime and Hauppauge Quad OTA cards working but this device wouldn't scan in.
![[Image: 2018-01-21-layout.png]](http://www.ashleygriffin.ca/temp/gbpvr/2018-01-21-layout.png)
