I started posting this message before I managed to solve the problem. However, I decide to post anyway, in case others have a similar problem when upgrading to 2.0.3.
Better half just came downstairs complaining that 'no tuner' (analog) are available after upgrading to 2.0.3 and trying to set a recording. LiveTV does not work either with "no capture devices" message.
A reboot didn't help, and there are no active recordings.
Configuration (setting/devices) suggested the Analog tuner is not present, but enabled, and the digital is both present and enabled. Error message in NPVR.log referred to MainConcept encoders not present (just like here)
I noticed that the upgrade seemed to change analogdevices.xml changed back to soft_encode from
Code:
<Device filter="Hauppauge WinTV 88x Video Capture">
<Name>Hauppauge HVR-3000/4000</Name>
<Type>HARD_ENCODE</Type>
</Device>
Changing back to HARD_ENCODE enabled the analog tuner and got rid of the MainConcept encoder error message, but did not seem to solver the original 'no tuners' problem.
So I re-registered (see here) hcw_mcmpeg2mux.ax, and a restart of the recording service and NPVR seemed to solve the problem.
So I just upgraded to 2.0.3. It fixed my Schedules Direct problem of not having any EPG data on my ATSC channels, but now the times are off by 6 hours!
Ie, 8pm CST EPG data has a daytime show that should be at 2pm.
sub....in 2.03 (maybe earlier versions as well) I am noticing when I enter a direct skip amount that the timeline does not align to what was entered.
For instance....I start playing a recording on the PCH and enter 42 and skip to go to 42 minutes into the recording.
NPVR does skip to the correct time but when I click on the info button and the timeline it shows the amount of time that the recording has been playing.....
So....if I hit 42 skip and watch for 6 minutes the recording goes to 42 minutes into the recording but the timeline shows 6 minutes.
I have used NPVR for a few monthes now on Win 7 and have used GBPVR before that.
The problem is that the recording stops working a few times a week. A message is displayed that a crashdump has been created and the program stop working until I have restarted the computer. Then it works for a few days again.
I am not sure it allways happens during recording, I don't think so, but the recording service stops and no recording av made after the crash.
I have installed the latest npvr and it works well with my Haupauge NOVA-S card (FreeSat in the UK) ... at least for recording and normal playback via NEWA (using VLC).
However, any attempt to stream either a recording or live-tv gives me a pixellated picture.
I cannot figure out if this is a VLC or nPVR issue?
I have tried VLC 117/103/099 at both ends - to no avail.
I seem to remember a similar issue with GBPVR that I think was a codec problem.
I have a DVB-S tuner at the bottom of my device list, so it should be last choice. I find that if I start playing a channel that is available only on this tuner, and then change channel - say to BBC1, which is available on my DVB-T tuners, it is still played using the DVB-S tuner. If I now try to play a DVB-S only channel on a client, then I receive a 'no tuner available' message.
Is this the intended behaviour?
I understand that I'm getting faster channel changes this way than if NPVR changed tuner to use the DVB-T tuner, but it doesn't seem to be making the best use of resources.
