> Dear all,
> I tried to use a "USB Logitech Quick Cam Express" to run the AR-Toolkit.
> Unfortunately, when the camera settings window appears (Property Sheet
> Properties), the default frame rate is 15,000 and the checkbox "flip
> horizontal" is disabled.
> As a result the video is not correctly displayed.
> I tried with another Logitech WebCam and this problem does not occur.
> Is it just due to the web Cam ?
> Does anybody else experienced this problem with the QC Express ?
> What are the minimum requirements for a webCam to be able to run the
> ARtoolkit ?
> Thanks in advance.
Sorry, no solution, but a comment (and my own problem below ;-)).
I have a Logitech "Quick Cam Express for Notebooks". Is it the same? Mine used to work 100% fine togehter with ArToolkit2.xx. But the image was always mirrored in ArToolkit and I had to use some tool like VIDCAP32.EXE under windows to force the image to be flipped - then ARToolkit would have re-flipped it to the correct version... Only a workaround though. The machine then was using Windows 98SE with a horrible frame rate due to 266Mhz, but it was working.
But as stated above "it used to work"... Well, now I'm working on another machine (Thinkpad R40, WindowsXP, SP1, DirectX9.0c (4.09.0000.09.04), ArToolkit 2.52, 2.65, 2.70) and it always hangs up during the first call of arVideoGetImage(). Going inside this, it stops during the call of
"wait_result = vid->graphManager->WaitForNextSample(frame_timeout_ms);" in videoWin32DirectShow.cpp.
If I change the frame_timeout_ms from infinite to sth. else it continues, but does not show any pixels... Any other Windows application shows the video image properly. And ArToolkit complains about missing WDM-capture device if no camera is plugged in - so it somehow notices it. But every format (RGB, YUV, ...) and framerate leads to the same outcome.
Anybody experienced this before? Any help would be appreciated. I'm not that much into DirectX-issues... Unfortunately I don't have a different camera at hand at the moment.