Unable to set capture device.

[RussellS]

Hi,

I have been using GBpvr 0.97.7 for quite a long time with no issues but decided it was time to upgrade to the newer version of 1.2.13

I've got it installed ok and I can run config.exe. I setup my capture device which is a Hauppauge PVR150MCE and checked the other settings etc. However, when I try to run PVRX2.exe nothing happens. Taskmanager confirms that PVRX2 is running but no UI comes up and the PC is unresponsive. The only way out is to end task in taskmanager. When I then go back into config again I find that the capture source is empty.

I now find that if I setup the capture source, then click OK to close config and then go back into config, I find the capture source is empty. I just can't get it to retain the capture source settings.

The PC is running WinXP Professional SP2 with .net 2.0 and I installed vcredist_x86.exe as advised in the release notes.


If anyone can offer any guidance I'd be very gratefull.


Regards

Russell

[sub]

Symptoms like this usually mean the videocard isnt up to the task. What video card do you have in your machine?

[RussellS]

Hi, thanks for the reply.

The video card is a ATI Radeon 7000 which, I have to admit, is getting on a bit

I didn't even consider that the video card would be the problem but it does make sense. I'm only using the capture & record facility of GBPVR as my main HTPC app is Meedio.

Should I go back to a version that used the old GBVR.exe gui and if so what was the last version that used it.


Many thanks for your time,

Regards

Russell

[sub]

I dont know if that card works or not. Post the pvrx2.exe-native.log and I'll see if there are any more clues.

[msantana]

I have the exact same issue. I have been using version 99.xx and finally decised to bite the bullet and install the latest version.
I also have a PVR150MCE in my system with: WinXP SP2, Athlon FX59, 1G RAM and a GFource 6200.

I also noticed the capture device dissappearing in the config. I ran PVRX2 in window mode to diagnose and it comes up with a black window. I can arrow up and down and hear the clicks as if I'm moving throught the menu. If I hit enter after moving up once I get a white screen with a large red "X" (diagonal lines from corner to corner). Upgrading my video driver did not help.

[sub]

I have the exact same issue. I have been using version 99.xx and finally decised to bite the bullet and install the latest version.
I also have a PVR150MCE in my system with: WinXP SP2, Athlon FX59, 1G RAM and a GFource 6200.

I also noticed the capture device dissappearing in the config. I ran PVRX2 in window mode to diagnose and it comes up with a black window. I can arrow up and down and hear the clicks as if I'm moving throught the menu. If I hit enter after moving up once I get a white screen with a large red "X" (diagonal lines from corner to corner). Upgrading my video driver did not help.

The 6200 definitely works. Reproduce the problem, then zip and attach the logs and I'll take a look.

[msantana]

Thanks for the quick response...

I wan't sure which log files you need. So, I zip'd the entire log directory. Even if the capture device is not setup in the config, shouldn't the UI still display correctly and allow one to navigate and use items that do not use the capture device? Are these two seperate problems?

Once again, Thanks for the help!

[sub]

2008-07-20 16:09:13.390 ERROR [1] Shutting down due to error (probably no VMR9 support): System.ComponentModel.Win32Exception: Error creating window handle.
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Form.CreateHandle()
at System.Windows.Forms.Control.get_Handle()
at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.Show()
at GBPVRX2.xb979ad394703258e.xfb409e85bd292293(String[] xf18a926310372520)

Sorry, I dont know what cause that. Its a new one on me. If you're accessing via remote desktop software, try it locally.