exposure overblown on hi3518ev100 + ov9712 about majestic HOT 4 OPEN

also this register seems to correspond to the prometheus metrics isp_exposure & isp_exptime
I'm not sure if it's ok that these are the same value - are they the same thing?

# HELP isp_exptime Sensor exposure time
# TYPE isp_exptime gauge
isp_exptime 687
# HELP isp_again Analog Gain
# TYPE isp_again gauge
isp_again 1024
# HELP isp_dgain Digital Gain
# TYPE isp_dgain gauge
isp_dgain 1024
# HELP isp_ispdgain ISP Gain
# TYPE isp_ispdgain gauge
isp_ispdgain 1024
# HELP isp_exposure Exposure
# TYPE isp_exposure gauge
isp_exposure 687
# HELP isp_avelum Average luminance
# TYPE isp_avelum gauge
isp_avelum 47
# HELP isp_exposureismax Exposure reached maximum
# TYPE isp_exposureismax gauge
isp_exposureismax 0

from majestic.

ok I was able to test using libsns_ov9712.so from oem firmware, and the issue still exists, so I suspect it's majestic doing something here with AEC

from majestic.

So an update - after some playing around with the camera positioning, if I angle the camera down just a bit, the image exposure balances out a bit better.
I think the main issue here may be that non of the isp exposure/gain settings (exposure, aGain, dGain, ispGain, etc) seem to have any effect on the ov9712 sensor, but it does look like this may be something controlled or influenced by majestic itself. So looking for advice on troubleshooting this. (none of the debug settings like system.logLevel=TRACE seem to induce majestic to output anything extra or meaningful for this investigation.)

from majestic.

You may use HiSilicon's PQTools to adjust low level ISP settings and play with different settings

from majestic.