Feature Request: Add `maxSensitivityIso` to `setAutoExposureLimit()`

[maxsitt]

With setAutoExposureLimit() a limit for the maximum exposure time can be set. This is very helpful, e.g. to avoid overexposed frames/images.

With the current implementation, only the maximum exposure time can be set. Depending on the configuration (e.g. using setAutoExposureRegion()), the produced frames can still be too bright, as ISO is increased even with the auto exposure limit.

Would it be possible to add a second parameter for maxSensitivityIso as in setManualExposure() also for setAutoExposureLimit()? This would give us more control over the camera behaviour under challenging lighting conditions and could avoid frames getting too bright due to high ISO values.

Thanks!

[themarpe]

@alex-luxonis is this possible?

[Erol444]

ping @alex-luxonis

[alex-luxonis]

No internal API available for that, but maybe we could tweak the tuning to set an ISO range on pipeline startup.

[maxsitt]

@alex-luxonis Thanks for looking into this!

Could you explain what you mean with "tweak the tuning"? Sorry that I don't understand what exactly you mean by this.

The possibility to set a range or limit for not only auto exposure time, but also ISO would definitely benefit various scenarios. In our use case, we would like to avoid frames getting too bright when using setAutoExposureRegion() in combination with detections. In our tests, we could often observe very bright frames due to small, dark (sometimes false) detections, which in turn influences the detection model. Using setAutoExposureLimit() did not solve this problem, as ISO is still increased.

[themarpe]

@maxsitt apart form modifying the imager/sensor tuning files (which requires Intel tools), there is no means of achieving this on RVC2 platform.

We'll have to close as wontfix as its not easily doable