Actually current0.jpg is the still from Camera Nr. 0. If you have only one camera then current.jpg and current0.jpg are the same thing. If you have more than one cam then you use current0, current1, and so on to get a still from a particular cam. In multicam setups current.jpg should not be used if you want to be sure of which cam you'll get an image from (it's affected by cookies from web visitors).
As for the problem you are having... it's not a bug, it's a feature
. If nothing is consuming images (no web requests, no localsave, etc.) AbelCam throttles down after while to conserve CPU cycles. Instead of taking samples from the cam at the rate set by Framerate, it samples at some low rate like once every few minutes.
Some find this to be good, others find it to be annoying. I battled this feature when I was making a script that saved a "collage" of the stills from all my cams periodically. I finally worked around it my making my code do this:
- Get the image
- Throw the mage away
- Wait 2 seconds
- Get the image
- Use the image
I believe the caption is applied when the image is served, so a fresh caption on a stale image is not surprising.
Edit: Maybe SSE can clarify the "throttled down" mode for us. My "once every few minutes" may be wrong. I was just messinbg around with this using a cam pointed at a clock and got an image that was 20 minutes stale. So maybe sampling stops completely? If that's the case I don't think I like this feature...