This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: The time consumed by the H264 algorithm compression is unstable?

Part Number: TDA4VM


Hi. Expert

SDK version:0804

linux + freeRTOS

Periodically feed the H264 (in Gstreamer,element:v4l2h264enc, bitrate=15Mbps) algorithm with the same image (CPU load rate is 30%, cycle is 45ms), the compression time used by H264 is unstable, jumping between 21~36ms, and there is no obvious regularity.A scatter plot of the time consumed by H264 compression is shown below:

Feed the image interface:gst_app_src_push_buffer().

Take the H264 compressed video stream interface:gst_app_sink_try_pull_sample().

In order to solve the above problem, we did a singleton test: remove the influence of other DDR footprints, change the h264 compressed frame to only output I frames, and change the compressed bitrate to 50Mbps. It is concluded that the time consumed by H264 compression also jumps between 21~36ms, and there is no obvious improvement.A scatter plot of the time consumed by H264 compression is shown below:

Excuse me, is there any way to solve the problem of unstable compression time?

Best regards.