GBPVR freezes while recording ATSC shows

[tjb]

I just installed a new HDHomeRun tuner and ever since I have been having the same problem as referenenced above. The Event log contains the following error:

Faulting application gbpvrrecordingservice.exe, version 1.0.2782.16257, stamp 00000025, faulting module psiparser.ax, version 0.1.0.0, stamp 46b3718b, debug? 0, fault address 0x0000b2d7

I also added the following statement in my config.xml:

<BDAUsePsiParser>false</BDAUsePsiParser>

but I still get the same errors. This has occurred 3 out of 4 evenings that I had something scheduled to record.

[tjb]

I probably should add that the failed recordings are all recurring scheduled events. I have done several tests where I simply record 2 or 3 current programs and so far they have always worked.

Also, I found a fix for an older version that Sub posted a few months ago (PsiParser.ax file dated 4/3/2007) in a file called PsiParser.zip. Any chance that this patch is still applicable to the current version?

[sub]

Also, I found a fix for an older version that Sub posted a few months ago (PsiParser.ax file dated 4/3/2007) in a file called PsiParser.zip. Any chance that this patch is still applicable to the current version?

Nope - dont do it.

[sub]

I just installed a new HDHomeRun tuner and ever since I have been having the same problem as referenenced above. The Event log contains the following error:

Faulting application gbpvrrecordingservice.exe, version 1.0.2782.16257, stamp 00000025, faulting module psiparser.ax, version 0.1.0.0, stamp 46b3718b, debug? 0, fault address 0x0000b2d7

I also added the following statement in my config.xml:

<BDAUsePsiParser>false</BDAUsePsiParser>

but I still get the same errors. This has occurred 3 out of 4 evenings that I had something scheduled to record.

If you're getting that error, then you havnt correctly set that <BDAUsePsiParser>true</BDAUsePsiParser> setting in config.xml. Did you [b]add[b] that line, or update the line that was already there? You should have updated the existing line.

[tjb]

If you're getting that error, then you havnt correctly set that <BDAUsePsiParser>true</BDAUsePsiParser> setting in config.xml. Did you [b]add[b] that line, or update the line that was already there? You should have updated the existing line.

As always, you are right. I added the lines to the end of the file instead of changing the original lines. I'll try again tonight to see if this resolves the issue.

[tjb]

I modified the existing line instead of adding it to the bottom. Now the recording service does not crash, but the failed recordings persist to some extent. Since the service does not crash, the recordings that work now continue on to completion (they used to die with the recording service), but others still show up as 4k files. I should note that whenever the recordings fail, there are two 4k files, not just one. Also, the final timestamp on the two files is the timestamp of the end of the show, not the beginning. I think this is because GbPvr notices that the recording is very small and tries to restart it as follows:

Recording is unusually small. Giving second chance: T:\Recordings ...
Stopping recording
Stopping recording oid:1
Restarting recording
BDARecordingSource about to start recording oid:1 channel:T:35,5,1~P:1~V:81~A:84~PMT:80~N:>5.1 WLWT-HD (000(AC3))
RenewLease 4
forcing refresh of next 2 hour events for all capture sources

Just in case they may help, I have included a zipped copy of the log files. The last failure was at 7:00 AM this morning (10/9/2007).

[sub]

When you get a 4k file, this indicates the device has failed to lock onto a signal and never delivered any data to GB-PVR.

[tjb]

When you get a 4k file, this indicates the device has failed to lock onto a signal and never delivered any data to GB-PVR.

I still think it may be tied to recurring schedules. Tonight I will delete all recurring schedules and schedule individual recordings and see if it still fails. Thanks for all your help, Sub.

[dmporch]

When you get a 4k file, this indicates the device has failed to lock onto a signal and never delivered any data to GB-PVR.

I'm getting a similar problem still and I was wondering how common this is and if there is anything we can do about it?

[tjb]

I'm getting a similar problem still and I was wondering how common this is and if there is anything we can do about it?

In your case did this problem just start with the latest version, or has it been intermittent for awhile? Mostly I'm just curious since I did not really start using GBPvr for recordings until version 1.0.16. As soon as I have it running without problems I plan to ditch my cable service.

The problem on my system occurs quite frequently. For example I had 5 shows scheduled to record last night, 3 of them were OK, the other two only had 4k files. It does NOT apparently have anything to do with recurring recordings. Last night I deleted all recurring scheules and selected Quick Record for the 5 shows in question, and like I said before, 2 of them failed.

I'd also be interested to know how many people are experiencing this problem, and in particular, which tuner cards they are using (in case the problem is tuner specific). I have a FusionDHTV in my DVR, and an HDHomeRun on my network for a total of 3 tuners (all trying to record ATSC OTA).