I created a graph with encoder node like this.
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.
I created a graph with encoder node like this.
Hello,
Which SDK version are you using?
Regards,
Lucas
Hello,
There was an optimization done in the 7.3 SDK which should take care of this. Can you migrate to the 7.3 SDK?
Regards,
Lucas
Hello,
We have not decided to migrate to 7.3 SDK .Can you help me to figure out how much it's improved in SDK 7.3.
I encode a bitstream in size of 1920 * 1080.
Regards,
Wang
Hello Wang,
Very sorry for the delay. After discussing with our internal team, I realized that I was mistaken on the optimizations made in 7.3. These optimizations only applied to decoder and not encoder. The performance will be the same in 7.3 as with 7.2 SDK.
Regards,
Lucas
Did you can vxVerifyGraph(graph) before calling vxProcessGraph(graph)? If not, can you try calling that first, and reprofiling the vxProcessGraph? The reason I ask is because if you don't call vxVerifyGraph(graph), then the vxProcessGraph(graph) internally calls that to set everything up. I want to see if this 1.3 seconds is mainly from vxVerifyGraph(graph) or vxProcessGraph(graph) for the first frame.
Hello Jesse,
I called vxVerifyGraph(graph) before calling vxProcessGraph(graph).I think it is mainly from vxProcessGraph(graph) for the first frame.
Regrads,
Wang
Hello Wang,
This is TI's last SDK release supporting RTOS-based encoder, as next release this will no longer be supported.
Since the full SDK is open source, you are welcome to view the source for this at tiovx/kernels_j7/hwa/venc/vx_video_encoder_target.c and make any modifications to improve the initial latency.
Regards,
Lucas
Hello Lucas,
Sorry, I haven't responded to this question for so long.
I have read tiovx/kernels_j7/hwa/venc/vx_video_encoder_target.c. And I don't think the latency can be simply reduced by modify this file since it mainly depends on mm_enc to call the encoder.
Regards
Hi Wang,
There seems to be issue in driver. We are investigating the same. Will provide the update as soon as we have something important.
Hi Wang,
Please find the attached driver patch. This patch fixes the current issue in encoder driver.