Good points. I use 640 x 480 on both AMCap and AbelCam. As I mentioned AMCap shows no delay at all, I think the default frame rate is 10 fps. AMCap never shows more than 17% CPU in the task manager, and ranges between 3% - 17% with an average around ~8%.

Changing the fps on AbelCam config did not seem to affect the CPU and preview speed at all. Tried rates from 2 fps to 10 fps. Picture was nearly identical.

Thanks for your help in diagnosing. Here is a link to the PWC-010:

http://www.prolynkz.com/products/webcams/pwc010.php

I shall try the 2.3 beta and get back to you on the results.

ACNCA064-2008-09-24 isn't required, but you might find it useful. It is the "Network Camera Agent", which was part of the AbelCam MSI installer on earlier versions. As of 2.3.6 beta it was given its own EXE installer, which is also the reason the AbelCam installer got smaller.

I am not 100% sure that 2.3.x are completely 64-bit ready; 2.2.x are, but they do not offer the option to select different capture engines. Hopefully SSE can clarify this. From your post is does sound like you got 2.3.6 to run on your 64-bit O/S though... true?

Assuming you have 2.3.6 running now, try this:

- On the Cameras screen, Stop and Remove your camera.

- Now Add your camera back in, BUT when you see the little pop-up list of camera devices DON'T just hit OK. Instead, change the Interface selection to either VisioForge or TyCapture first.

- Once the camera has been added, go into Configure and check/set your Resolution and FrameRate as desired (changing the Capture Device will default some settings).

- Save your config and then start the camera as normal. Check CPU level. If it's still too high, repeat this procedure using a different Capture Interface.

The Capture Interfaces have various differences internally that will give different levels of features vs. efficiency with different cameras. The thing I forgot to tell you before is that you have to remove and add the camera in order to actually see the Interface selections.

I followed your link to the cam information and looked around the site. I didn't find anything there that helped, unfortunately. Hopefully the "trial and error" method above will result in your finding one capture interface that works nicely with the cam.