Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I am hoping someone can point me in the right direction. At the moment my application (source code available for Windows) sends the following string to prepare the camera for image grabbing.
Then afterwards, to grab an image I send the following command http://192.168.0.9/admin-bin/ccam.cgi?opt=vhxcsym
In my image retrieval testing the device used for testing is a standard analogue clock with a second hand. The test is that the moment I send the image grab command (http://192.168.0.9/admin-bin/ccam.cgi?opt=vhxcsym) and the clocks seconds hand is on say 20 seconds, when I get the image displayed in my browser the seconds hand will sit at 22 seconds, basically 2 seconds difference from request to actual image information. What can I do so that when I request the image on 20, the image displayed is still sitting at 20. Any input or suggestions would be most appreciated.
Shaun, when you acquire a new image camera skips a couple frames - usually it is much shorter than 2 seconds, maybe you have long exposure. To reduce the dead time, you may start a streamer and than acquire images (w/o changing image format) - there will be no extra delay. You may try this with the camera default web interface. Other option - just acquire the whole stream and cut the required images from it.
Thanks for the advice, I read on the forum that the ccam.cgi is an older methodology and it is recomended to use the Video API. I am not able to work with incoming streaming video as the application is for a CE device, so processing power and memory is limited. I will try the suggestions and post my results.
ccam.cgi is older for our cameras (I started it for the first model 303 in 2001) and later was adding some more functionality for new sensors and cameras. Video API was designed later for compatibility with Axis cameras, but now we do not have anybody to support this branch now. So ccam.cgi is the most current and we support it.