Hi,
I refer to this link to verify the lantency of the imx219 camera.
after trying ,I use following command:
v4l2-ctl --list-formats-ext --device=0
[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)
gst-launch-1.0 nvarguscamerasrc sensor-id =0 ! ‘video/x-raw(memory:NVMM),width=1280,height=720,framerate=30/1,format=NV12’ ! nv3dsink
gst-launch-1.0 nvarguscamerasrc sensor-id =0 ! ‘video/x-raw(memory:NVMM),width=1280,height=720,framerate=60/1,format=NV12’ ! nv3dsink
I find change framerate seems not work, the lantency cost about: 180ms-220ms
And I change the plugin from nv3dsink to xvimagesink by using following command:
gst-launch-1.0 nvarguscamerasrc sensor-id =1 ! ‘video/x-raw(memory:NVMM),width=1280,height=720,framerate=30/1,format=NV12’ ! nvvidconv ! xvimagesink
In this command, the lantency cost about: 120ms-160ms
How I test the delay is shoot with the csi camera at the screen time and observe the time difference.
I wonder if this delay can be reduced, or this is already basically the best.