OK, upgraded to 1.5.36, ensured I the latest DirectX update, and made sure I have all the patches (although I'm not sure where haupblast.exe goes). The problem persists. I have attached the most recent logs.
Sorry, but I've got no idea. Its really sounds like something funky related to the HDHR drivers. Its hard to guess what exactly though.
If you havnt already tried it, it might be worth trying with the app set to 'Other ATSC/QAM' if it's set to 'GBPVR'. Also, maybe try disabling the 'auto select from available tuners' setting.
I already had it set to Other and to not auto-select. I'll see if I can find other options to fiddle with. If others have the problem with every NPVR, and I think it used to work for me, perhaps there's some system configuration change somewhere that seems unrelated that breaks it. It is strange that I get the problem using one HDHR tuner and the digital on the HVR-1600, and that both stop recording at the same time.
petercooperjr Wrote:It is strange that I get the problem using one HDHR tuner and the digital on the HVR-1600, and that both stop recording at the same time.
Yes, I agree - but I still cant look past the fact that everyone involved has had a HDHR so far.
I'm still thinking about it, but havnt come up with a possible reason for this problem yet.
I have a HDHR and after installing all the patches in the Getting Started thread, I can record two shows at once again. I was experiencing this problem after installing 1.5.36 initially.
I just upgraded to Win7 last week and have been messing with all the computer settings this weekend. I have no idea what fixed it.
Are you sure that the error "FindFilterByName failed to locate filter: Microsoft Network Provider"
is not the cause of the problem, could be HDHR specific?
That is the only difference between my working HDHR config and your logs, unless it's the HDHR drivers (haven't updated in awhile).
Is there a way to force that error with my working config to check if it's the problem or not?
nobody Wrote:Are you sure that the error "FindFilterByName failed to locate filter: Microsoft Network Provider"
is not the cause of the problem, could be HDHR specific?
That is the only difference between my working HDHR config and your logs, unless it's the HDHR drivers (haven't updated in awhile).
Is there a way to force that error with my working config to check if it's the problem or not?
The significance of that message is that users that get it are running XP. Those that dont get that message are running Vista/Win7, so there is probably a lot of major differences between XP and Vista/Win7 that could account for this problem - different versions of all sorts of different components in the BDA subsystem etc.
Missed that it was XP, I setup Xp install same problems as the others records for a couple of minutes then file sizes stop growing but HDHR still streams even after the end time.
Both tuners work fine under Win 7 no problems there just under Win XP
Hmm. The more I think about it, sub, the more I think you must be right and that this had never worked. I just had never connected what I'm seeing now with what I saw when I was first playing with the first beta. Human memory is such a strange thing at times. Sorry about that.
So, now to ask a question that'll be impossible to answer: What's different in how it records from the HDHR between GB-PVR and NPVR? Since I know that it worked on GB-PVR.
Maybe I'll write some sort of utility to let me record with GB-PVR and put it into NPVR's database for playback. Although then I wouldn't get the timing.info that makes the skipping and comskip now finally work right. Or, maybe I'll finally replace my 6½-year-old computer that's hooked up to the TV with something a little more modern and with a newer OS.