I recently installed the latest version of npvr & applied the patches as directed. Howevever when I do a channel scan it crashes. I am running windows xp pro on an intel quad core 2.5ghz processor using a pinnacle pctv 2001e dual tuner. Any help would be greatly appreciated.
Reproduce the problem, them zip and attach the npvr.log and I'll see if anything stands out.
jonesy2456 Wrote:I recently installed the latest version of npvr & applied the patches as directed. Howevever when I do a channel scan it crashes. I am running windows xp pro on an intel quad core 2.5ghz processor using a pinnacle pctv 2001e dual tuner. Any help would be greatly appreciated.
Make sure you dont have DVB fix installed.
Yes I did have dbv fix installed. I have removed it and now when doing the channel scan nothing happens. There is no crash and the scan dialog box doesn' freeze.
Its another "Async stop taking way too long " problem from the log.
I have this exact same problem and reference in the Log. This happens on both a machine running XP and one running Win 7. Hardware is completely different with One being an i7, x58, dual Nvidia card setup, the other being an old athlon 64 X2 with an AMD video card. Also uses different decoders, one using ffdshow, the other used microsoft's DTV filters that come with win7 media center. Scans worked fine last time I tried 2 months ago. Help.
Important section from the log.
2011-12-05 12:49:19.661 [DEBUG][1] Frequency has changed, so stopping recording from previous frequency. (Handle 10)
2011-12-05 12:49:19.661 [DEBUG][1] DigitalRecorderDVBT::Tune@1
2011-12-05 12:49:19.661 [DEBUG][1] DigitalRecorderDVBT::Tune@2
2011-12-05 12:49:19.661 [DEBUG][1] DigitalRecorderDVBT::Tune@3
2011-12-05 12:49:19.661 [DEBUG][1] DigitalRecorderDVBT::Tune@4
2011-12-05 12:49:19.671 [DEBUG][1] DigitalRecorderDVBT::Tune@5
2011-12-05 12:49:19.671 [DEBUG][1] DigitalRecorderDVBT::Tune@6
2011-12-05 12:49:33.635 [DEBUG][1] DigitalRecorderDVBT::Tune@7
2011-12-05 12:49:33.635 [DEBUG][1] Calling LockChannel()
2011-12-05 12:49:33.650 [DEBUG][1] locked=0, present=0, strength=0, quality=0 (took 16ms to check)
2011-12-05 12:49:33.650 [DEBUG][1] DigitalRecorderDVBT::Tune@8
2011-12-05 12:49:33.650 [INFO][1] DigitalRecorder.StartStream() allocated handle: 0xB
2011-12-05 12:49:33.650 [INFO][1] DigitalRecorder.StopStream() handle: A
2011-12-05 12:49:38.663 [DEBUG][1] Scan completed. Checking if any 'unknown' channels were found, and whether their names can now be resolved...
2011-12-05 12:49:38.691 [INFO][1] DigitalRecorder.StopAllStreams()
2011-12-05 12:49:38.692 [DEBUG][1] About to request async graph stop
2011-12-05 12:49:38.693 [DEBUG][5] About to stop network provider
2011-12-05 12:49:38.893 [DEBUG][5] Stopped network provider
2011-12-05 12:49:38.893 [DEBUG][5] Graph stopping... (async)
2011-12-05 12:49:46.693 [DEBUG][1] Async stop taking way too long
2011-12-05 12:49:52.699 [DEBUG][1] Removing filter MPEG-2 Sections and Tables
2011-12-05 12:49:52.699 [DEBUG][1] Removing filter MPEG-2 Sections and Tables
2011-12-05 12:49:52.700 [DEBUG][1] Removing filter MPEG-2 Sections and Tables
Line 10 in the log does not look too good:-
locked=0, present=0, strength=0, quality=0 (took 16ms to check)
For a normal tuner that would suggest there is a problem with the tuner as it is not "present".
jcjefferies Wrote:Line 10 in the log does not look too good:-
locked=0, present=0, strength=0, quality=0 (took 16ms to check)
For a normal tuner that would suggest there is a problem with the tuner as it is not "present".
You need to look through the rest of the log as it was doing a channel scan and detecting channels fine with non zero stats for the things you quoted. I think there it was scanning a frequency that no longer has any channels on it (my region has been moving mux's quite a lot recently due to switchover). So it not getting any signal from that frequency is expected behavior....
Resolved this on both my machines by doing a clean de-installation (including deleting the public\NPVR directory) and then re-installing with the latest patches. Disappointed in the lack of response to this thread even just to say that re installation might be an option, even if it is obvious.