WDM, VfW, who gives a flying f... how it works, we only care that it works!
Bottom line, Hauppauge can capture video and play TV on w2k without crashing. Matrox can't.
Other than support for DV, I see nothing really worthwhile in WDM. I've captured >5GB with the Vegas Video capture tool using the Hauppauge VfW drivers so the 2/4 GB limits seem gone. I've got all the functionality I had under win9x without all the crashes and re-install voodoo to fix things, plus the benefits of no 2/4 GB limits with openDML aware apps.
Actually people need both driver models until MS fixes netmeeting/netshow to use WDM. I'd argue that working VfW drivers on w2k is a higher priority than WDM right now until MS gets off their duff and leads the way to show the benefits of WDM. As I said other than DV support, I see nothing of practical value in WDM at this time.
Last time this thread came around it was waaaa Zoren dosen't have a w2k SDK for their MJPEG chip.
--wally.
Bottom line, Hauppauge can capture video and play TV on w2k without crashing. Matrox can't.
Other than support for DV, I see nothing really worthwhile in WDM. I've captured >5GB with the Vegas Video capture tool using the Hauppauge VfW drivers so the 2/4 GB limits seem gone. I've got all the functionality I had under win9x without all the crashes and re-install voodoo to fix things, plus the benefits of no 2/4 GB limits with openDML aware apps.
Actually people need both driver models until MS fixes netmeeting/netshow to use WDM. I'd argue that working VfW drivers on w2k is a higher priority than WDM right now until MS gets off their duff and leads the way to show the benefits of WDM. As I said other than DV support, I see nothing of practical value in WDM at this time.
Last time this thread came around it was waaaa Zoren dosen't have a w2k SDK for their MJPEG chip.
--wally.
Comment