I am running into annoying problem using capDriverConnect API in an ancient VFW library.
I have a simple two step code using capCreateCaptureWindow and capDriverConnect.
The "problem " is that capDriverConnect randomly copies the captured data into the CView derived class.
It appears that when the code is run in debug the data is blank ( black ) about 50 % of the time and when run (.exe - still in debug mode) it fills the data ( single frame from USB camera ) about 80% of the time.
<b>I cannot find anywhere ( I did Google for it) if capDriverConnect suppose to do that and / or how to stop it. </b>
I need to capture frames for further processing and that code is working correctly.
Please - no commentary about how obsolete or crappy VFW is. It is used in OpenCV and that library does ton of video processing which I need.
I am not trying to be a moron, but if you do not have a clue why capDriverConnect
behave this way save your and mine time and do not reply. OK?
Last Visit: 31-Dec-99 18:00 Last Update: 24-May-17 0:29