dvb recording ending at incorrect times

[tieke]

I suspect the attached logs may not be too helpful, but basically a recording on my Twinhan dvb-s card stopped earlier tonight than it was supposed to, although the recording service seemed to indicate that it hadn't stopped at all.

To be specific, my wife had set "The Apprentice" up to record, which it duly started to do at around 7.29pm, but rather than record the entire two-hour season finale, it recorded only the first 41 1/2 minutes of it. When she went to watch it and spotted that she had reached the end of the recording half-way through, I saw that the gb-pvr icon was still green, and that on checking the recording status, gb-pvr stated that the dvb source was still recording the program (I have both a pvr-150 and a dvb source). Restarting the recording service resulted in the dvb card now being reported as sleeping, but did not of course produce an extra hour or so of the program .

I am running the latest 97.9 version, but have had sporadic occurances of something similar with previous versions - ie the dvb source's status still being in record mode even though the official record time should have ended. The logs didn't provide any useful info then, but maybe sub may find something in the current ones.

cheers,

tieke

[sub]

I cant see any obvious reason there. It all looks ok.

[tieke]

Bugger. I might see if there are any more recent drivers, and if it happens again, simply disable the card (better to choose to record a show than have the computer decide for me )

cheers,

tieke

[tieke]

Just restarted the gb-pvr computer, and had a microsoft pop-up offering to send error details to microsoft regarding an 8.13pm GBPVRRecordingService.exe error, so there is obviously some record of it somewhere - do you know if there is an easy way to figure out further info about this error?

cheers,

tieke

[sub]

Take a look in the Windows Event Viewer.

[tieke]

Thanks. It said:

Code:

Event Type:    Error
Event Source:    .NET Runtime 2.0 Error Reporting
Event Category:    None
Event ID:    1000
Date:        6/06/2006
Time:        8:10:01 p.m.
User:        N/A
Computer:    SHUTTLE
Description:
Faulting application gbpvrrecordingservice.exe, version 1.0.2344.23214, stamp 00000038, faulting module psiparser.ax, version 0.1.0.0, stamp 447bb717, debug? 0, fault address 0x0001002a.
Data:
0000: 41 00 70 00 70 00 6c 00   A.p.p.l.
0008: 69 00 63 00 61 00 74 00   i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00   i.o.n. .
0018: 46 00 61 00 69 00 6c 00   F.a.i.l.
0020: 75 00 72 00 65 00 20 00   u.r.e. .
0028: 20 00 67 00 62 00 70 00    .g.b.p.
0030: 76 00 72 00 72 00 65 00   v.r.r.e.
0038: 63 00 6f 00 72 00 64 00   c.o.r.d.
0040: 69 00 6e 00 67 00 73 00   i.n.g.s.
0048: 65 00 72 00 76 00 69 00   e.r.v.i.
0050: 63 00 65 00 2e 00 65 00   c.e...e.
0058: 78 00 65 00 20 00 31 00   x.e. .1.
0060: 2e 00 30 00 2e 00 32 00   ..0...2.
0068: 33 00 34 00 34 00 2e 00   3.4.4...
0070: 32 00 33 00 32 00 31 00   2.3.2.1.
0078: 34 00 20 00 30 00 30 00   4. .0.0.
0080: 30 00 30 00 30 00 30 00   0.0.0.0.
0088: 33 00 38 00 20 00 69 00   3.8. .i.
0090: 6e 00 20 00 70 00 73 00   n. .p.s.
0098: 69 00 70 00 61 00 72 00   i.p.a.r.
00a0: 73 00 65 00 72 00 2e 00   s.e.r...
00a8: 61 00 78 00 20 00 30 00   a.x. .0.
00b0: 2e 00 31 00 2e 00 30 00   ..1...0.
00b8: 2e 00 30 00 20 00 34 00   ..0. .4.
00c0: 34 00 37 00 62 00 62 00   4.7.b.b.
00c8: 37 00 31 00 37 00 20 00   7.1.7. .
00d0: 66 00 44 00 65 00 62 00   f.D.e.b.
00d8: 75 00 67 00 20 00 30 00   u.g. .0.
00e0: 20 00 61 00 74 00 20 00    .a.t. .
00e8: 6f 00 66 00 66 00 73 00   o.f.f.s.
00f0: 65 00 74 00 20 00 30 00   e.t. .0.
00f8: 30 00 30 00 31 00 30 00   0.0.1.0.
0100: 30 00 32 00 61 00 0d 00   0.2.a...
0108: 0a 00                     ..

But I also noticed that

"The following boot-start or system-start driver(s) failed to load:
nvport
THBDA "

So that might be a cause/additional problem for me to look at.
[EDIT] - the nvport reference is a known purevideo uninstall remnant. I will look further at the THBDA reference
cheers,

tieke

[sub]

You could try setting <BDAUsePsiParser>false</BDAUsePsiParser>, but you'll need to remember to set it back to 'true' if you need to scan for channels.