Windows 10 is phasing out the command prompt in the latest Preview.
How will this affect the way we do things, run scripts, etc, if any, in NPVR? I don't use Powershell so I don't know much about it.
Quote:Command Prompt has been around for as long as we can remember, but starting with Windows 10 build 14971, Microsoft is trying to make PowerShell the main command shell in the operating system.
Quote:As a result, PowerShell officially replaces the Command Prompt in the Win + X menu, so when you right-click the Start menu, you’ll only be allowed to launch the more powerful app. Additionally, in File Explorer’s File menu and in the context menu that appears when pressing Shift + right-click in any folder, the old Command Prompt will no longer be available.
Typing cmd in the run dialog will launch PowerShell as well, so Microsoft has made a significant step towards phasing out the traditional Command Prompt.
I upgraded to 3.9.2 a few days ago. I'm unable to delete recorded programs. The first few times a message flashed by. Now it just hangs for a few seconds, doesn't delete, and returns to the list of recorded episodes. Logs attached. Thank you for any help you can provide.
I know this sounds more like a hardware issue than NPVR, but it didn't start until updating NPVR about a month ago.
Over the past month or so my HTPC has been dead in the water when I get up in the morning. I have it setup for standard "sleep" mode (no hibernation or hybrid) after an hour of inactivity. It has a blue LED that flashes while sleeping. I noticed that the LED was off. I tried "waking" with my keyboard/mouse and nothing. When I manually push the power button the PC appears to reboot but fails with a solid red "DRAM" LED on the motherboard. I then have to either unplug or switch off the PSU for a second. After that, it boots and operates normally. No error messages or anything. I ran the Windows Mem Checker and it found no RAM problems. This has been happening for several weeks now. I have been trying to monitor for the cause. It went an entire week without issue. I also just happened to not have any scheduled recordings that week. Then I noticed that it was DOA the next morning after a recording the previous night. I haven't made any hardware changes in over a year. I'm not 100%, but it seems this started happening around the time I updated NPVR to the version prior to the most recent. I updated to the most recent version and still have the same problem.
Any ideas, help, or suggestions?
TIA
i7920
Asus Sabertooth mobo
12gb ram (3 sticks triple channel)
GTX 660 Ti
Win 10 Pro
all drivers and software up to date
I recently replaced my dual tuner card with a Hauppauge Quad Tuner card.
NextPVR server treats the new quad tuner like it is a dual tuner card.
The NextPVR server kicks off clients when a recording is started even when there are two unused tuners available.
I'm running Windows 10 with a dual core processor.
Will NextPVR be updated soon to properly handle quad tuner cards?
I had a number of episodes fail for various reasons (HD Homerun failure, signal loss, etc etc.)
I want nPVR to not see these episodes as previously recorded, so that the next time they air, it will be re-recorded and i'll have a 'clean' copy of the episode.
What is the most effective way to remove the record of these episodes being recorded so that they'll get re-recorded? Ideally, I won't have to remove the entire series, as I have ~10 seasons of this show, just a few episodes missing in each season due to corrupt (for various reasons) recordings.
I've come to discover that the NPVR Recording Service is not automatically starting when my PC reboots. If I open Services and locate NPVR Recording Service, the setting for Startup Type is set to Automatic. I would think that would do it, but apparently no? Is there something else I need to do?
Hi, currently experimenting with nextpvr but having an issue with bulk map in that I don't get prompted for the rest of the channels and it doesn't save when trying to set epg source. I tried the patch below.
Re the NLite client, Sub wrote: To run it, simply extract into a directory somewhere onto your machine, and run the nlite.exe executable. It'll auto locate and connect to your NextPVR server running on the local network.
- - -
Either by switch or a config setting, is there a way to just tell nlite.exe where the server is?
I ask because it only works on the NextPVR host PC. If I run it from any other PC on my network it does not find it.
Am I missing something, or is there a setting somewhere in NextPVR that has to be set first?
* As a side note, NEWA is easily found using port 8866 on all of my PC's
Below is the message I get when run from a PC on the same network.
Checking configuration
About to connect to server
Found interface: name=[{87D99AB7-5FC9-4E48-8F22-93BACF1AEB8F}] desc=[VirtualBox NDIS 6.0 Miniport Driver] address=[192.168.56.1] netmask=[255.255.255.0] broadcastAddr=[192.168.56.255]
Locator sent to broadcastAddr=[192.168.56.255]
Found interface: name=[{2A377CC1-98F4-47EF-A6D5-1DBD65DA42C3}] desc=[Hyper-V Virtual Ethernet Adapter] address=[10.11.0.100] netmask=[255.255.255.0] broadcastAddr=[10.11.0.255]
Locator sent to broadcastAddr=[10.11.0.255]
Failed to discover any NextPVR servers on the local network...
Unable to find and connect to a NextPVR server. Exiting.
