Industrial Cameras FAQ/BlockID of acquired images are...

BlockID of acquired images are not continuous number in USB3.0 cameras (BU / DU series) or GigE Vision cameras(BG series).  Does this means that frame-loss occurred?(No.1510)

When application is acquiring images using High-Level streaming API of SDK in the environment that CPU usage is high, TeliCamAPI may receive the next frame image (B) and save it in ring buffer inside TeliCamSDK during executing processing of current frame image (A) in ImageAcquired event handler.

In this case, ImageAcquired event for image (B) will be skipped and an image (C) next to image (B) will be handled as current frame at the next ImageAcquired event. If user checks BlockID of image (A) and image(C),user will misjudge that BlockID is not continuous.

If ring buffer index of current ImageAcquired event is not continuous number to that of previous ImageAcquired event, use Strm_LockBuffer() function to get images not processed yet.

if BlockID of images in ring buffer is not continuous, please set frame rate slower or set buffer count of ring buffer larger.
The default buffer count of ring buffer is 8. User application can specify buffer count by specifying buffer count as argument of Strm_OpenSimple() or CameraStream.Open(). User application can set buffer count up to 30.

back

Was this FAQ helpful?

Please let us know your opinion about the FAQ so that we will be able to improve our FAQ. (Within 800 characters)
Note: If you need a reply to your inquiry (e.g. inquiry about products), please use the inquiries form provided on Contact Us page. Please note that we cannot answer to your questions filled in below.

Please click below to change the cookie settings used on our website.