Webcam32 FAQs User's Guide Java Support Help Wizard
|
|
|
|
Webcam32 FAQs User's Guide Java Support Help Wizard |
|
|
|
|
When using Webcam32 in its FTP mode, new images are uploaded to the FTP Server/Webserver at configurable periodic intervals. The image previously on the server is replaced with the latest image just captured. If desired, the previous images can be saved in a rolling loop to provide viewers with a series of images from the last set of uploads.
Assuming that a save count of 3 had been specified with an upload interval of 60 seconds
| Upload | Description |
| 0 | image.jpg written |
| 1 | image.jpg renamed to image1.jpg image.jpg written |
| 2 | image1.jpg renamed to image2.jpg image.jpg renamed to image1.jpg image.jpg written |
| 3 | image2.jpg renamed to image3.jpg mage1.jpg renamed to image2.jpg image.jpg renamed to image1.jpg image.jpg written |
| 4 | image2.jpg renamed to image3.jpg (note: image3.jpg has been lost) mage1.jpg renamed to image2.jpg image.jpg renamed to image1.jpg image.jpg written |
| 5 onwards | The description for upload 4 repeats |
The previous images can be used on a "Last
In the Webcam32 FTP settings (basic), the Save Count value specifies the number of images to be saved. If 0 is used (default) then no images will be saved and each new image uploaded will simply overwrite the previous image.
The Save Count input area is illustrated in the following diagram:
Setting the save count too large can adversely affect performance. For each image, Webcam32 has to shuffle files around across the network. If the save count is too high (say > 20), there may not be time to shuffle previous files in a given upload interval and some intervals will be missed.