Nvarguscamerasrc - conditions for aeregion property

adam.bucko · September 17, 2024, 12:48pm

Hello i am working with an IMX camera on Jetson Orin Nano 4gb, and i am trying to set aeregion property with my program. Using the ICameraProperties i read out the getMinAeRegionSize() value and got 256*256. Therefore i decided to use the aeregion size of 256x256.

My camera resolution is 1920*1080 and with testing i have found out that the aeregion setting only works at certain parts of the image, in other parts of the image it causes the pipeline to freeze and eventually timeout.

These are some examples of aeregion position that seemed to work:

GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 0 512 512 1.000000
AE Region: 0 0 512 512 1.000000
GST_ARGUS: Setting AeRegion on the fly: 0 0 512 512 1.000000 
GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 512 512 1024 1.000000
AE Region: 0 512 512 1024 1.000000
GST_ARGUS: Setting AeRegion on the fly: 0 512 512 1024 1.000000 
GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 1024 512 1536 1.000000
AE Region: 0 1024 512 1536 1.000000
GST_ARGUS: Setting AeRegion on the fly: 0 1024 512 1536 1.000000

And this is an example of values which did not work:

GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 412 832 768 1188 1.000000
GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 512 1024 1024 1536 1.000000

I am unable to determine why some values are accepted and some cause pipeline to freeze.

With the highest DEBUG level of 9 on the element nvarguscamerasrc i only get this output after the pipeline freezes and few seconds go by:

CONSUMER: ERROR OCCURRED
[ERROR] [AvDeepStream] argus-camera-source: TIMEOUT�)
GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 412 832 668 1088 1.0
AE Region: 0 1536 256 1792 1.000000
0:00:07.468006976  4105 0xaaaae7b21580 DEBUG       nvarguscamerasrc gstnvarguscamerasrc.cpp:1714:consumer_thread:<argus-camera-source> consumer_thread: stop_requested=1

[INFO] [AvDeepStream] Received EOS, stopping the stream
GST_ARGUS: Cleaning up

Afterwards i have to restart nvargus-daemon systemctl in order to run the test again.

My main question is, are there some additional conditions regarding setting the numbers in aeregion property ? Since i dont know why the pipeline is freezing with some values

ShaneCCC · September 18, 2024, 12:18am

Please check the daemon log for the detail.

https://elinux.org/Jetson/l4t/Camera_BringUp

Thanks

adam.bucko · September 18, 2024, 7:05am

Hi and thank you for your reply, i tried looking into daemon logs, the most intel i got from sudo journalctl -u nvargus-daemon -f

This is what i got:

Settting the aeregion values to these numbers

GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 510 256 766 1.000000
AE Region: 0 510 256 766 1.000000
GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 561 256 817 1.000000
AE Region: 0 561 256 817 1.000000
GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 612 256 868 1.000000
AE Region: 0 612 256 868 1.000000
GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 663 256 919 1.000000
AE Region: 0 663 256 919 1.000000
GST_ARGUS: NvArgusCameraSrc: Settin

Causes the following errors to arise

Sep 18 06:50:35 dcs nvargus-daemon[4371]: (Autocontrol) Error BadParameter: NvIspAeSetUpLac1Settings: effective image region [256x252] is too small (in src/algorithms/ae/ae_metering.cpp, function NvIspAeSetUpLac1Settings(), line 729)
Sep 18 06:50:35 dcs nvargus-daemon[4371]: (Autocontrol) Error BadParameter: AE failed to grab PCL metadata
Sep 18 06:50:35 dcs nvargus-daemon[4371]:  (in src/algorithms/ae/ae_main.cpp, function run(), line 858)
Sep 18 06:50:35 dcs nvargus-daemon[4371]: (Autocontrol) Error BadParameter: NvIspAeSetUpLac1Settings: effective image region [256x252] is too small (in src/algorithms/ae/ae_metering.cpp, function NvIspAeSetUpLac1Settings(), line 729)
Sep 18 06:50:35 dcs nvargus-daemon[4371]: (Autocontrol) Error BadParameter: AE failed to grab PCL metadata
Sep 18 06:50:35 dcs nvargus-daemon[4371]:  (in src/algorithms/ae/ae_main.cpp, function run(), line 858)
Sep 18 06:50:35 dcs nvargus-daemon[4371]: (Autocontrol) Error BadParameter: NvIspAeSetUpLac1Settings: effective image region [256x252] is too small (in src/algorithms/ae/ae_metering.cpp, function NvIspAeSetUpLac1Settings(), line 729)
Sep 18 06:50:35 dcs nvargus-daemon[4371]: (Autocontrol) Error BadParameter: AE failed to grab PCL metadata
Sep 18 06:50:35 dcs nvargus-daemon[4371]:  (in src/algorithms/ae/ae_main.cpp, function run(), line 858)
Sep 18 06:50:35 dcs nvargus-daemon[4371]: (Autocontrol) Error BadParameter: NvIspAeSetUpLac1Settings: effective image region [256x252] is too small (in src/algorithms/ae/ae_metering.cpp, function NvIspAeSetUpLac1Settings(), line 729)

The size [256x252] as reported by the error doesnt corespond with the points i set in aeregion. This is also the case when trying to set the window to a bigger size
This is the case with a size of window set to 356x356:

GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 994 356 1350 1.000000
AE Region: 0 994 356 1350 1.000000

Resulting error:

Sep 18 06:57:21 dcs nvargus-daemon[4505]: CAM: serial no file already exists, skips storing again(Autocontrol) Error BadParameter: NvIspAeSetUpLac1Settings: effective image region [356x228] is too small (in src/algorithms/ae/ae_metering.cpp, function NvIspAeSetUpLac1Settings(), line 729)

ShaneCCC · September 18, 2024, 8:13am

Maybe the size clamp by the output ratio.
Could you check by any output size that the ratio is 4:3 like 640x480/2592x1944?

adam.bucko · September 18, 2024, 9:02am

Is this what you meant ? This is the resolution of the video

GST_ARGUS: Running with following settings:
Camera index = 0
Camera mode = 2
Output Stream W = 1920 H = 1080
seconds to Run = 0
Frame Rate = 29.999999

ShaneCCC · September 19, 2024, 6:23am

Any other sensor mode that the ratio is 4:3?

adam.bucko · September 19, 2024, 8:35am

What do you mean ? Should i change the resolution ?

ShaneCCC · September 20, 2024, 5:25am

Looks like there are two sensor mode support by sensor driver.
Could you check another sensor mode?
BTW, have below command to check the sensor mode.

v4l2-ctl --list-formats-ext

adam.bucko · September 20, 2024, 1:07pm

This is the output of said command
$ v4l2-ctl --list-formats-ext

ioctl: VIDIOC_ENUM_FMT
	Type: Video Capture

	[0]: 'RG10' (10-bit Bayer RGRG/GBGB)
		Size: Discrete 3280x2464
			Interval: Discrete 0.048s (21.000 fps)
		Size: Discrete 3280x1848
			Interval: Discrete 0.036s (28.000 fps)
		Size: Discrete 1920x1080
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 1640x1232
			Interval: Discrete 0.033s (30.000 fps)
		Size: Discrete 1280x720
			Interval: Discrete 0.017s (60.000 fps)

ShaneCCC · September 23, 2024, 3:29am

Please select 3280x2464 sensor mode to verify.

Thanks

adam.bucko · September 23, 2024, 7:54am

Even with the resolution of 3280 x 2464 i am experiencing the same behaviour

GST_ARGUS: Setting AeRegion on the fly: 0 2056 257 2313 1.000000 
GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 2313 257 2570 1.000000
AE Region: 0 2313 257 2570 1.000000
GST_ARGUS: Setting AeRegion on the fly: 0 2313 257 2570 1.000000 
CONSUMER: ERROR OCCURRED
[ERROR] [AvDeepStream] argus-camera-source: CANCELLED�)

With the error quotes of the window being [256x148]

Sep 18 09:43:24 dcs nvargus-daemon[3401]: (Autocontrol) Error BadParameter: NvIspAeSetUpLac1Settings: effective image region [256x148] is too small (in src/algorithms/ae/ae_metering.cpp, function NvIspAeSetUpLac1Settings(), line 729)
Sep 18 09:43:24 dcs nvargus-daemon[3401]: (Autocontrol) Error BadParameter: NvIspAeSetUpLac1Settings: effective image region [256x148] is too small (in src/algorithms/ae/ae_metering.cpp, function NvIspAeSetUpLac1Settings(), line 729)

ShaneCCC · September 23, 2024, 9:08am

The error tell size is less than 256x256.

adam.bucko · September 23, 2024, 10:35am

Yes thats the point, the issue with all the resolutions is that it crashes due to small window size even tho the parameters by which the window was set dont result to the values outputed in the Error.

setting aeregion to 0 2056 257 2313 1.0 is 2313-2056=257 and 257-0=257 resulting in 257x257 window by my understanding

ShaneCCC · September 23, 2024, 2:10pm

Please try even numbers like 256x256.
And from the log looks like set the AE ranges to 0 2313 257 2570 that greater than the output size 2464

adam.bucko · September 24, 2024, 5:40am

Even numbers caused the same Error to arise

To your second point with it being higher than 2464. I dont think it is, since the 2313-2570 is in image width, which is max 3280, due to the order being [top, left, bottom, right]. This can be seen in the documentation for aeregion

Source: https://developer.download.nvidia.com/embedded/L4T/r28_Release_v3.0/Docs/Jetson_TX1_and_TX2_Accelerated_GStreamer_User_Guide.pdf?t=eyJscyI6ImdzZW8iLCJsc2QiOiJodHRwczovL3d3dy5nb29nbGUuY29tLyJ9

ShaneCCC · September 24, 2024, 6:20am

OK, that’s my mistake.
What’s your version. I check below command on JP5.1.2 without problem.

xvimagesink sync=false
GST_ARGUS: NvArgusCameraSrc: Setting AE REGION : 0 2313 257 2570 1
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
GST_ARGUS: Creating output stream
CONSUMER: Waiting until producer is connected...
GST_ARGUS: Available Sensor modes :
GST_ARGUS: 2592 x 1944 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 16.000000; Exposure Range min 34000, max 550385000;

GST_ARGUS: 2592 x 1458 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 16.000000; Exposure Range min 34000, max 550385000;

GST_ARGUS: 1280 x 720 FR = 120.000005 fps Duration = 8333333 ; Analog Gain range min 1.000000, max 16.000000; Exposure Range min 22000, max 358733000;

GST_ARGUS: Running with following settings:
   Camera index = 0
   Camera mode  = 0
   Output Stream W = 2592 H = 1944
   seconds to Run    = 0
   Frame Rate = 29.999999
GST_ARGUS: Setting AeRegion: 0 2313 257 2570 1.000000
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.

adam.bucko · September 24, 2024, 6:43am

My JetPack is also 5.1.2, however i am changing the aeregion on the fly, when the camera pipleine is already running, there might be a difference since it has a custom print into the console for changing it during the run. What do you think ?

ShaneCCC · September 24, 2024, 6:54am

Could you verify the gst-launch-1.0 command in my previous comment to confirm.

Thanks

system · October 23, 2024, 3:18am

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

Topic		Replies	Views
Nvargus-daemon aeregion limitations Jetson Xavier NX camera	5	165	October 22, 2024
How do I display a camera image on the screen Jetson Orin Nano camera	20	926	May 13, 2024
Nvarguscamerasrc error Jetson AGX Orin camera	2	567	April 26, 2023
Error connecting CSI Camera Jetpack 6.0 - nvbuf_utils: dmabuf_fd mapped entry NOT found and a lot more errors Jetson Orin Nano camera	6	577	March 23, 2024
Nvarguscamerasrc dmabuf_fd -1 mapped entry NOT found Jetson Orin NX camera , gstreamer	12	1776	March 15, 2023
Nvarguscamerasrc not working (URGENT) Jetson Orin Nano camera	12	127	February 20, 2025
Nvarguscamerasrc issues, related to OpenCV Jetson Nano camera	36	7084	October 12, 2022
Gst-nvarguscamera fails on Jetpack 6.0 Jetson Orin NX camera	2	37	January 24, 2025
Argus Autoexposure Region of Interest Jetson AGX Xavier nvbugs	20	4277	October 18, 2021
Bayer Video Feed on OV2740 Jetson Xavier NX camera	9	1946	October 18, 2021

Nvarguscamerasrc - conditions for aeregion property

Related topics