Und wieder eine gute Nachricht:
Auf
http://www.virtualdub.org" ist beschrieben, wie man die Registry abändern kann, damit die TV-Karten mit den Philips SAA713x Chipsätzen mit dem VFWWDM-Wrapper in VirtualDub laufen. Der Text steht direkt auf der Eingangsseite unter den News mit dem Titel
"1/14/2003 News: Philips SAA713x (Antigua) capture fix, and random other stuff
I have been in contact with Philips regarding a problem with VirtualDub's capture module and the drivers for the Philips SAA713x (Antigua) chip -- essentially, you can get video capture to work one or two times, then the thing dies. Overlay works, but preview doesn't, and you get zero frames trying to capture.
For you coders out there, from the Video for Windows side this very simply means you get zero samples on both the video and preview callbacks. As it turns out, Philips' staff discovered that the problem is VFWWDM driver connecting to both the Preview and the Capture pins on the Antigua capture filter.
You can disable the Preview pin with the following Registry entry:
HKEY_LOCAL_MACHINESYSTEMControlSet001ControlClass{4D36E96C-E325-11CE-BFC1-08002BE10318}
nnnParametersCapPreviewEnabled = DWORD:00000001
nnnn is a four-digit number that varies by system -- the best way to figure it out is to search for a key that is fairly unique to the driver, perhaps ADC Phase Clock Delay or VideoTunerEnabled. There should already be a bunch of other Enabled type entries in the registry key. (Note that CurrentControlSet is an alias and usually points to ControlSet001.)
When you are done, reboot the system (I mean it) and then restart VirtualDub in capture mode. If the change took, the Overlay option should be grayed out.
After making this change on my Windows 2000 system, capture works reliably. Full credit goes to the Antigua team for figuring this out -- my role for the most part was trying a capture and responding back, "uh, yup, it doesn't work."
Please note, however, that the registry change disables functionality in the capture driver and may interfere with normal operation of DirectShow-based capture applications. It may also void your OEM technical support.
It is suggested that you keep note of the change for future reference, and perhaps bookmark the key if you are running the Windows 2000/XP Registry Editor, in order to delete it later if you experience problems in other applications.
As usual, if your system fails to boot, you must have screwed up somewhere."
Gruss
Stefan