Live TV Problem

[cetacean]

Hi everyone.

I'm having an odd problem watching live tv. My setup consists of GBPVR and a Hauppauge 250. Sometimes when I'm watching live tv, GBPVR just stops playing the live stream for no reason. It goes back to the main menu after about 30 seconds of video. When I start live tv again, I will get about 30 seconds of video then, bam, main menu. It will keep doing this until the next reboot, after which it works normally for a time and then this issue crops up again. I haven't been able to tie it to a conflict with any particular program though I'm pretty sure something like that is what's going on.

I'm looking for advice on what diagnostic steps I can take (e.g., what logs I can look in, etc) to start tracking down the source of this problem. Any advice or likely problem candidates would be appreciated. Thanks

[sub]

What version of GB-PVR are you running?

Are you using and MVP for viewing, or via your monitor?

What EPG do you use?

[cetacean]

What version of GB-PVR are you running?

Are you using and MVP for viewing, or via your monitor?

What EPG do you use?

I'm running the newest version minus one, 0.95.14

I have an MVP but this occurs when I'm watching on my monitor. (my gbpvr.exe.log is filled with 15 megs of :

12/7/2005 5:48:48 PM.139 VERBOSE [125] getValue cached value: /settings/DisableHauppaugeMVPScreenSaver : true
12/7/2005 5:48:48 PM.139 VERBOSE [125] MVP request processed
12/7/2005 5:48:53 PM.170 VERBOSE [125] MVP data read: 1 (8)
12/7/2005 5:48:53 PM.170 VERBOSE [125] Responding to ping

)

I use Zap2It for the program guide

[sub]

can you reproduce the problem, then zip and attach your GBPVRRecordingService.exe.log and GBPVRRecordingService.exe-native.log?

[cetacean]

Well, I think I found the problem in that log:

12/7/2005 8:41:29 PM.764 VERBOSE [21] Starting LiveTV for captureSource: 2 channel oid: 125 filename:
12/7/2005 8:42:02 PM.545 VERBOSE [21] RenewLease 2
12/7/2005 8:42:02 PM.545 VERBOSE [21] RecordingFactory.LoadNext24HourEvents()
12/7/2005 8:42:02 PM.545 VERBOSE [21] Found potential conflict with recording scheduled to start at: 12/5/2005 9:00:00 PM
12/7/2005 8:42:02 PM.545 VERBOSE [21] Looking for another available tuner (for moving scheduled recording)
12/7/2005 8:42:02 PM.545 VERBOSE [21] Checking PVR-250 (DIRECT:Hauppauge PVR250:1)
12/7/2005 8:42:02 PM.545 VERBOSE [21] DIRECT:Hauppauge PVR250:1 can not help...
12/7/2005 8:42:02 PM.545 VERBOSE [21] Checking VCR Plug In (DIRECT:Hauppauge PVR250:1)
12/7/2005 8:42:02 PM.545 VERBOSE [21] DIRECT:Hauppauge PVR250:1 can not help...
12/7/2005 8:42:02 PM.889 VERBOSE [21] StopPreviewLiveTV()

This is the entirety of the GBPVRRecordingService.exe.log for that session


I guess it thinks that there is an old recording scheduled that it thinks the current session is conflicting with? I checked my pending recordings (I use Xrecord) and didn't see anything from 12/5 and couldn't go back far enough in the EPG to see if anything was scheduled then.

Ive also attached the native log but didn't see anything that seemed relevant there.

[cetacean]

After I posted that, I restarted GBPVR, and had the same issue.

Then I tried to watch live tv again it gave me an error that said something like "error: ______ not set to valid instance of object" or something like that (clicked ok before I really read the error, sorry)

Then I started live tv again and it's working fine. *shrug*

Could that error have been the clearing out of the erroneous scheduled recording?


As I alluded to in the OP, this has happened previously (before 12/5 at 9 when that conflicting recording was scheduled.)

[sub]

Where is the other log I asked for?

[cetacean]

Where is the other log I asked for?

Sorry, thought the snippet above was sufficient. Here is the full log. The reproduced error is from 8:41 PM to 8:42 PM on 12/7. You can see it recurr several times after that and then disappear.

[sub]

Have you tried rebooting?

[cetacean]

Have you tried rebooting?

Now why didn't I think of that?

Thanks for tryiing to help with this, I will work on trying to figure out when the past due recordings decide to stick around and gum things up. Could this be an XRecord issue, or does that just frontend GBPVR's recording DB so there isn't a way it could be doing this?