Problems after upgrading

[triple-e]

Newbie forum poster.

I just upgraded to 97.13 after installing the .NET 2.0 Framework. The install seemed to go well, but now I can't record any new shows or watch live tv. I can watch the recordings made before the upgrade. When scheduling a recording, all appears to work, and I have a 0 byte file at the end of the show. Another point is that my Hauppauge 150 doesn't show up when I check the "only show devices detected in this machine" checkbox in the source configuration dialog box. The setup worked great with 94.13 and 96.12 (which is where I upgraded from). I can zip up all of the log files if it helps. I get a dialog with "Object reference not set to an instance of an object" and an ok button.

Below is the hopefully relavant portion of the gbpvr.exe.log file:

8/23/2006 9:42:19 PM.086 VERBOSE [1] PreviewLiveTV(38)
8/23/2006 9:42:19 PM.086 VERBOSE [1] PreviewLiveTV() done
8/23/2006 9:42:19 PM.368 VERBOSE [1] DirectRecordingSource::getPreviewGraph(2)
8/23/2006 9:42:19 PM.368 VERBOSE [1] Stopping recording oid:1
8/23/2006 9:42:19 PM.586 ERROR [1] Error: msg=0x202 (WM_LBUTTONUP) hwnd=0x150382 wparam=0x0 lparam=0x1d2009a result=0x0 : System.NullReferenceException: Object reference not set to an instance of an object.
at ConnectFilters(IBaseFilter* pFilterUpstream, IBaseFilter* pFilterDownstream)
at NativeUtilities.ConexantRecorder.StartRecording(String cardType, ConexantRecordSource recordingSource, Int32 qualitySetting, Int32 board, String filename, Int32 channel, Int32 countryCode, Int32 tuningType, Boolean useStreamingEngineIfAvailable, Boolean previewMode, Boolean fmRadioMode, Boolean fmRadioPreviewMode)
at NativeUtilities.ConexantRecorder.getPreviewGraph(String cardType, ConexantRecordSource recordingSource, Int32 board, Int32 channel, Int32 countryCode, Int32 tuningType)
at GBPVR.Backend.Common.DirectRecordingSource.getPreviewGraph(ChannelTuning channelTuning)
at GBPVR.xb3e61f7448c39547.x4276385f71addb51(Channel xee500015fb4a65b6)
at GBPVR.x4a212861656a24dd.x3852f96f8dab4cab(Channel xee500015fb4a65b6)
at GBPVR.x05e13382b8294c7a.xb4057d727283fc14(x8b4f0834394c048a x12ea9462ae6eb890)
at GBPVR.xa556fe3f7d8d6ce3.OnClick(Point location)
at GBPVR.x05e13382b8294c7a.OnClick(Point location)
at GBPVR.x86396f56243de9fb.OnClick(Point location)
at GBPVR.xbb1566157f5f8b1f.xf1b04f0b61b2ba29(Object xdf2e3583f942db7b, EventArgs xc4f45905cb1fc7ba)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at GBPVR.xbb1566157f5f8b1f.WndProc(Message& m)
8/23/2006 9:42:20 PM.618 VERBOSE [1] controller.OnMouseDown()
8/23/2006 9:42:20 PM.696 VERBOSE [1] controller.OnClick()
8/23/2006 9:42:27 PM.180 VERBOSE [1] HideMouse ref=-1
8/23/2006 9:43:18 PM.727 VERBOSE [1] ShowMouse ref=0
8/23/2006 9:43:22 PM.055 VERBOSE [1] controller.OnMouseDown()
8/23/2006 9:43:22 PM.133 VERBOSE [1] controller.OnClick()

[elite]

Do you have your drivers installed correctly for the 150? (is all working in wintv?) - I know the drivers for the 350 can be a bit stroppy about how they are installed, just wondering if it is the same for the 150

[triple-e]

Everything is working in wintv. Everything was working in gbpvr 96.12 the instant before I upgraded to 97.13. Which is why this is all so very confusing. Are there some quick things to check besides wintv to see if I don't need to reinstall the hauppauge drivers?

[sub]

Can you reproduce the problem, then zip and attach the gbpvr.exe-native.log file?

[HtV]

Everything is working in wintv. Everything was working in gbpvr 96.12 the instant before I upgraded to 97.13. Which is why this is all so very confusing. Are there some quick things to check besides wintv to see if I don't need to reinstall the hauppauge drivers?

Any old plugins getting in the way. Check your plugin dir.

[triple-e]

There shouldn't be any. I have basically gone to starting over with a completely empty gbpvr folder in program files that I install into.

That's not to say that they would be gone from the registry if they were to register themselves, etc. Nor are they gone from the machine, just from the current gbpvr directory


And I imported recordings that I had made previously to the upgrade problems. They play just fine. But of course, they don't use the hauppauge card, but my cheap display card.

The software that came with the hauppauge plays live tv just fine. I haven't tried to record anything, because I basically don't want to use that software, I want to use gbpvr.

[triple-e]

Can you reproduce the problem, then zip and attach the gbpvr.exe-native.log file?

Missed this one earlier, I will do so as soon as I can tonight. Thanks!

[triple-e]

[ATTACHMENT NOT FOUND] This is my log file. I think I have attached it correctly.

[sub]

17:11:29.908 ERROR Failed to get capture filter output pin. This will cause encoder auto-detection to fail

This error is usually caused by a PVR250/PVR350 owner selecting the card type as a PVR150. I'd double check that you've selected the correct card type.

[triple-e]

Alright, I now feel completely insane. I would have bet real money that I have a Hauppauge 150.

The app told me that I didn't :o (it wasn't part of the selection process after checking the box indicating to only show me cards that were installed). I didn't believe it.:o I still don't, but after selecting the 250, everything was back to working order just as before.

Are there any 150's that behave like 250's, or am I just losing my mind after less than a year, and remembering wrong. I put the PVR together with only 2 things in mind. Cost and storage, so I can't believe I sprung for the 250 :confused: .

And if everything wasn't working now and the case was lying open on the floor I might look, but as it is working (THANK YOU!!!!) I will just settle back and enjoy the shows! I love this program and all the support that comes from the forums! Sorry for ignoring what the app said and making work for everyone to help me out!