almost. In the ringbuffer lock mode auto, the buffer is locked when a new image is acquired and stays locked during getting the image via wait. The buffer is only unlocked when you don’t hold the image any more. In python that should be when either
- the image runs out of scope
- you call delete on the image
- the image variable is overwritten
You’ll find a ringbuffer example in your CVB installation under %CVB%\Tutorial\Image Manager\VC\VCRingBuffer\x64\Release
Image unlock would only allow the ringbuffer to re-use this specific buffer again which means it is subject to change and should not be used for computations any more as the result might be anything between two images (image A, image B or image A being overwritten by X percent with image B).
For normal usage (99 % of all cases), the default ringbuffer lock mode auto is fine and you won’t need to worry about it. Only lock mode on would require you to manually unlock each buffer/image after you are done with it in order to get new image. Lock mode off would require you to make sure you process the images fast enough before they are overwritten.