-
Notifications
You must be signed in to change notification settings - Fork 9
Open
Labels
bugSomething isn't workingSomething isn't working
Description
When trying to change these to something other than the default value the library appears to not work. For example, see the number of skipped frames, see the following pipelines:
ae-num-skip-frames=0
GST_DEBUG="*ti*:6" gst-launch-1.0 \
v4l2src device=/dev/video2 io-mode=5 ! "video/x-bayer, width=1920, height=1080, format=rggb, framerate=30/1" ! \
tiovxisp dcc-isp-file=/opt/imaging/imx219/dcc_viss.bin format-msb=7 \
sink_0::device=/dev/v4l-subdev2 sink_0::dcc-2a-file=/opt/imaging/imx219/dcc_2a.bin \
sink_0::ae-num-skip-frames=0 \
! kmssinkae-num-skip-frames=1
GST_DEBUG="*ti*:6" gst-launch-1.0 \
v4l2src device=/dev/video2 io-mode=5 ! "video/x-bayer, width=1920, height=1080, format=rggb, framerate=30/1" ! \
tiovxisp dcc-isp-file=/opt/imaging/imx219/dcc_viss.bin format-msb=7 \
sink_0::device=/dev/v4l-subdev2 sink_0::dcc-2a-file=/opt/imaging/imx219/dcc_2a.bin \
sink_0::ae-num-skip-frames=1 \
! kmssinkOn the second pipeline, the sensor_out_data that TI_2A_wrapper_process returns is always stuck to the same value. This also behaves the same for the awb-num-skip-frames
The feedback itself to the ISP node appears to work correctly since the image doesn't have a green tint like we had when the AE library wasn't integrated.
And when trying to use this with multiple cameras, if one has a num-skip-frames=0 and the other num-skip-frames=1, the one with a value of 1 has the incorrect behavior. This error is not only with 1, is with any value other than 0.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working