2. "The PVR250 and PVR350 have single instance drivers, so its critical that you kill WinTV and/or MCE background services. These hold onto the device, and it'll get the failure you're seeing in GB-PVR."
I found it myself, but then also the quoted post from sub (he is the master ). http://forums.nextpvr.com/showthread.php...-tv-screen
So, start the Services.msc, scroll down to the HauppaugeTVServer, and set it to "Disabled". Maybe you could also use "Manual". Note that WinTV 7 will not work until you restart that service. If you also have a PVR150 in the same machine, you may be in trouble, because it requires a single start/stop of WinTV otherwise you get no sound. However, on my machine PVR150 worked "out of the box" (did not need to fiddle with HauppaugeTVServer, but needed the start/stop of WinTV). And the PVR350 never had any problems with GB-PVR (ever since 2003...), even on Win7.
Now my PVR350 also works in NPVR after reboots. Will post update if there are any problems.
OK, it happened again. I am getting single byte recordings on an Australian channel called GEM. Yesterday morning I retuned all channels and did a quick check - I was getting a recording on GEM.
This morning I set a manual recording on all channels and GEM has again failed with a zero byte file. I checked Live TV and I get a good picture. Just in case there was a problem with the PostProcessing script I disabled it but I still have a zero byte recording on this channel.
I don't know if I'm the only one experiencing this but here is the scenario.
After a manual scheduled recording is complete, I can go to "What's New", and the recordings are shown as "Failed" with the error message of "Recording service not running at recording time". This is incorrect as the shows were recorded correctly.
Any thoughts? I'm happy because they did record, but the conflicting error I thought I should share.
I've been using NPVR for a bit. Last night, I added some new channels that came through ClearQAM, and they, along with a few other old channels, no longer show up in NEWA. They show up fine in the local guide, recordings work, and if I go to "Mange Recordings" in NEWA, the shows I've set to record are there as well.
I looked in the log, and I'm getting this message. "2011-02-25 17:46:24.407 [ERROR][4] Unexpected error in EPGEvent.LoadByOID(): System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at NUtility.EPGEvent.GetListingsForTimePeriod(DateTime startTime, DateTime endTime)"
I did delete one channel as well. Would that possibly have had something to do with it?
On my system NPVR always crashes during channel scan.
System:
NPVR 1.5.36 with NPVR 1.5.36 Patches Final.zip applied
Win7 Ultimate 64bit
DVB-S Technisat Skystar2
The programs start to load and wireshark shows that some tcp and vnc traffic ensues.
The mvpmc dongle gives me more clues. It completes the loading process through the screen that shows http://www.mvpmc.org and the eight squares, it then starts the red progress bar, and then finally shows the "starting application..." screen. Then it restarts back to the http://www.mvpmc.org screen. If I hit the "ok" button on my remote immediately after the red progress bar, then I am put into mpvmc menu where I can see the filesystem or enter emulation mode. It is only when I enter emulation mode that this restarting occurs.
Don't even know if it is televised, but if it is, is anyone in a position to record the California Broncos tomorrow? We'', not so bothered about the game but daughter-in-law is singing the National Anthem. TIA
I am trying out NPVR for the first time (long-time gb-pvr user) and I am having issues getting NPVR to detect any channels with my hdhomerun tuner. I have verified that the hdhr works with a number of other apps. A log file is attached of my channel scan activities. I have checked the firewall, I am aware that it is a common issue, but it is disabled and npvr is marked to be allowed anyway.
Here is a chunk of the log file showing that npvr detected a strong signal from channel 48.
). 
