Alrighty... my head is basically buzzing after trying to interpret all the information out there, but here's the problem. Essentially the question is, 'how come a camera that's connected by a firewire connection can't be detected by netmeeting'?
From my research, the answer is that the program is written to interpret devices operating under the video for windows (VfW) specification, and digital camcorders connected by firewire operate under the Windows Driver Model (WDM) specification inherent in DirectShow/DirectX.
Microsoft apparently has support for a VfW-WDM mapping protocol, so that older devices which came with programs that are meant to be interpreted under the VfW spec are translated into a WDM spec and therefor compatible with DirectX.
But what I can't find is a WDM-VfW protocol. Surely this would be a very marketable commodity? I can see some immediate uses, the least of which would be to enable programs like AVI_IO and VirtualDub to capture Type 1 DV and recompress it with different codecs.
Anyone able to shed some light on this?
- A
From my research, the answer is that the program is written to interpret devices operating under the video for windows (VfW) specification, and digital camcorders connected by firewire operate under the Windows Driver Model (WDM) specification inherent in DirectShow/DirectX.
Microsoft apparently has support for a VfW-WDM mapping protocol, so that older devices which came with programs that are meant to be interpreted under the VfW spec are translated into a WDM spec and therefor compatible with DirectX.
But what I can't find is a WDM-VfW protocol. Surely this would be a very marketable commodity? I can see some immediate uses, the least of which would be to enable programs like AVI_IO and VirtualDub to capture Type 1 DV and recompress it with different codecs.
Anyone able to shed some light on this?
- A
Comment