A bug of the function "NvBufferTransform" in gstnvarguscamerasrc.cpp

Environment:JetPack 4.4.1 JetsonNX max-clock 6core-15W
There is a time consuming bug in gstnvarguscamerasrc.cpp.
As shown in the following figure, I can get h264-data/yuv-data 25fps in the appsink/fakesink by using capture single sensor, no matter how many app-bin are followed by tee.

But after add a same pipeline to capture another sensor, I can get 25fps from the appsink/fakesink with 2 app-bins;I can get only 21fps from the appsink/fakesink with 3 app-bins;and get only 17fps with 4app-bin. As app-bin and queue increase, the number of captured frames decreases.

I found that the function NvBufferTransform will cost much time when capture by using two cameras.

The following figure was work by using single camera.

The following figure was work by using two cameras.

This is duplicate of
An important bug about nvargus and tee /queue when captured by using multiple sensors ?

Let’s continue discussion in the topic.

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