problem with video capture; msi 8833 and Wincoder

schavera

Member
Nov 28, 2001
25
0
0
I recently purchased the mx400 pro vt32s -- aka msi8833 -- and I cannot get Wincoder video capture to work. I select the nvidia wdm video capture device in the configuration button and the app then freezes up. I restarted my computer and tried to run wincoder again and I can't get past the welcome screen. I also tried VirtualDub and it doesn't recognize the device as valid.

I have since updated both the latest nvidia video driver and capture driver as found on the msi support site. I still have the same problem. has anyone else run into this problem on this or any other nvidia card?

The only thing i can think of that may contribute to this is that i have an hipix hdtv card installed and it is also listed as a capture device but i have disabled it and it no longer shows up as a device and i still have this problem. Could there be some sort of conflict or is this a bad driver?

I am running on Win98SE and the installed capture driver is 1.04g, in think.

 
Oct 16, 1999
10,490
4
0
I can't get virtualdub working with my MSI card either. It says it can't detect a capture device. But wincoder seems to be detecting it and working ok for me. Have you tried upgrading wincoder? The version that came with my card was pretty old. Just install the trial version off intervideo's website over your original install and viola.
 

schavera

Member
Nov 28, 2001
25
0
0
Thanks for the info. i installed the trial version of wincoder and that didn't work. i will try your other suggestion next. i am just about ready to send this card back. This is way too frustrating. maybe an ATI card is a better / easier solution...
 

schavera

Member
Nov 28, 2001
25
0
0
Well, I have had little luck with this. I downloaded the driver wrapper and was able to get it recognized within VirtualDub but I don't see anything while recording. It is just a black box. I have just about given up on this product as I am still having problems with WinCoder.

Gonad, what OS and what version of the WDM are you running? I think this might be part of the problem but most likely it is one of those things that is specific to my setup.