Setting custom auto-exposure region with odd left value causes flickering

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Xavier
1

Hi there! We have found an odd problem while using the libargus API. When we set a custom auto exposure region with the setAeRegions function, we get flickering video. (see attachment)

flickering.zip (2.3 MB)

We have already found the following things:

  • This only happens for odd values of the left coordinate of the AcRegion. When we change the left to be even, these issues do not occur.
  • You also need to point the camera to a scene where the AcRegion encompasses a darker and a lighter area, so for example the sky with something before it will work fine.

I have tested on both JetPack 5.1 as well as JetPack 4.4.1, and on both cases we could reproduce this flickering problem.

Can you explain why this is happening? Thanks in advance!

1 Like
3

Good finding.
Suppose relative with Argus engine don’t support odd resolution also the AeRegion may have problem while set odd value.

Thanks

4

Are there any other requirements for the AcRegion that we should be aware of?
It would be great if this could be added to the documentation.

5

Do you any update on my question above?

7

really appreciate @pepijn.vanheiningen …

btw, what is the conclusion here? @ShaneCCC
if it is odd number in the resolution(width or height)?
or each value (left/top/right/bot)?

Kind Regards,

  • I just tested with these two cases, and both are giving flickering when I dynamically change the Exposure Compensation.

AcRegion fieldRegion(811, 496, 3265, 1713, 0.8); //odd
AcRegion sensorRegion(0, 0, 3856, 2180, 0.2);

AcRegion fieldRegion(810, 496, 3264, 1712, 0.8); //even
AcRegion sensorRegion(0, 0, 3856, 2180, 0.2);

8

Could you clarify don’t set the aeregion but only change the Exposure compensation?

10

Hi,
I tried it with the whole sensor region only (AcRegion sensorRegion(0, 0, 3856, 2180, 1.0);)
it is the default right?

yes it was still happening.
However I found out that my sensor gain range was 0.0 - 1.0 when the problem happens.
if I increase this to 0.0 - 3.0, interestingly it is not happening!

I’m really curious the reason behind this…
Thank you!

Kind Regards,

11

How about don’t call the AcRegion()?

13

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.