nvcamerasrc aeRegion

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Hi,

We are experiencing over exposed videos and I am trying to somewhat influence the auto-exposure logic of nvcamerasrc, with no luck so far.

I tried setting manual exposure (nvcamerasrc auto-exposure=1 exposure-time=0.001) with no visible effect on the images. What am I doing wrong here? is this not the correct way to set manual exposure?

I moved on to try setting the aeRegion parameter, but could not convince gstreamer (gst-launch or nvcamerasrc) to accept the settting:
WARNING: erroneous pipeline: could not set property “aeRegion” in element “nvcamerasrc0” to “(0,0,100,100,1.2)”

I tried many variation of this format, to no success.

Can someone share a gst-launch-1.0 command line with aeRegion specified in the correct format?

Best regards,
Adh

2

It’s know problem for gst-launch. Please use the nvgstcapture instead of gst-launch for the aeRegion.

3

@ShaneCCC, I think it could be a good idea to include those kind of limitations about nvcamerasrc in the Accelerated_GStreamer_User_Guide.

That would save your customers a lot of time and help choose the right path early on (nvgstcapture vs. nvcamerasrc).

4

Hello Adh,

Did nvgstcapture works for you on aeRegion? Thanks.

Michael