Argus needs at least 4 capures ist its internal capture queue?

[rbayr]

Hello,

I was experimenting wit single Argus captures (iCaptureSession->capture()).

I my test setup I queue a set amount of requests (using iCaptureSession->capture()) and than I wait for the first image to be delivered by the OutpuStream before queueing the next request. Afterwards every received Image will also Tigger the queuing of the next request.

If I start with 1 Request queued, than I receive an image on every 4th trigger send to the camera (after two initial setup triggers), so the 3rd, 7th, 11th, … trigger will generate an image.

If I start with 2 Requests queued, than I receive an image on every 4th and its following trigger send to the camera (after two initial setup triggers), so the 3rd, 4th, 7th, 8th, 11th, 12th, … trigger will generate an image.

If I start with 3 Requests queued, than I receive an image on every 4th and its 2 following trigger send to the camera (after two initial setup triggers), so the 3rd, 4th, 5th, 7th, 8th, 9zh, 11th, 12th, 13th, … trigger will generate an image.

If I start with 4 or more Requests queued I receive an image on every trigger after the two initial triggers.

Is there a reason for this behaviour?
Is there a way to get an image with every trigger, even though the internal request queue has less than 4 requests?

For my application it is curial that every trigger send to the camera also generates an image.

Platform:

L4T: 32.7.3
Jetson Xavier NX

[ShaneCCC]

It’s known behavior for current ARCH design don’t have a solution for it now.

Thanks

[rbayr]

Is there a plan to fix this in a future releases?

Or is there another possibility to get trigger accurate captures with the ISP?

[ShaneCCC]

Sorry to tell don’t have plan in nearly release.

Thanks