When I disconnect the webcam and connect the evaluation camera, I am able to verify that it is using it's own (non-windows) driver.
When the webcam is connected, it is using the microsoft provided driver files: ksthunk.sys and usbvideo.sys.
#Vimicro usb pc camera amcap drivers
Note I: I've been able to verify that different drivers are being used for each camera by: Start->Devices and Printers->USB 2.0 Camera->Hardware tabe->USB 2.0 camera->Driver->Driver Details. So I suggested that it should work with windows default driver similar to how a webcam would so as to avoid compatibility issues but I'm wondering if there is a better option that I might be missing. I've been able to use both cameras in my c++ based OpenCv applications, but I'm asking because a 3rd company is going to provide me with a usb board-based camera (for evaluation) and they are asking about driver specs. Could anyone comment on such assumption or explain how AMCAP.exe is able to do that. In which case, I assume that most camera vendors follow a common standard interface for camera drivers. My question is: Is it safe to assume that AMCAP.exe is only running as a video-stream display program?
#Vimicro usb pc camera amcap .exe
exe (provided from Vimicro) and it will display live streaming from the connected camera (any of the two) although each one uses a different driver. I've been experimenting with two cameras, one is a webcam and another is an evaluation-kit camera that comes with its own drivers, I can run AMCAP. General Publisher Publisher web site Release Date FebruDate Added FebruVersion 9.22 build 260.3 Category Category Subcategory Operating Systems Operating Systems Windows XP/2003/Vista/Server Additional Requirements None Download Information File Size 2.34MB File Name AMCapSetup.exe Popularity Total Downloads 327,659 Downloads Last Week 312 Pricing License Model Free to try Limitations Time-limit during video capture and watermark on still images Price $29. Full Specifications What's new in version 9.22 build 260.3 Version 9.22 build 260.3 may include unspecified updates, enhancements, or bug fixes.
0 kommentar(er)
