UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Observer hakyemez
Observer
667 Views
Registered: ‎11-07-2018

Latency of Encoders

Could you help me to compare the latency of HEVC and AVC for encoding in Zynq Ultrascale+ VCU IP. In PG252 16.6ms is mentioned for encoder latency. In which options that latency is measured? How much latency does 'Using encoder buffer' option add to the system?

Kind Regards,

Tags (2)
0 Kudos
3 Replies
Xilinx Employee
Xilinx Employee
622 Views
Registered: ‎08-01-2007

Re: Latency of Encoders

The number in the Product Guide PG252 are independent of the encoder mode.

If you want to do additional testing you can use gst-shark as noted in Debugging Performance Issues sub-section of section Debugging a VCU based System.  You can find example of how to use gst-shark to measure latency on Google.

Chris
Video Design Hub | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
0 Kudos
Moderator
Moderator
592 Views
Registered: ‎11-09-2015

Re: Latency of Encoders

Hi @hakyemez,

Do you have any updates on this? Was @chrisar's reply enough for you?

If your question is answered or your issue is solved, please kindly mark the response which helped as solution (click on "Accept as solution" button below the reply)

If this is not solved/answered, please reply in the topic giving more information on your current status.

Thanks and Regards,


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
Observer hakyemez
Observer
566 Views
Registered: ‎11-07-2018

Re: Latency of Encoders

Hi Chris,

I've downloaded Zynq UltraScale+ MPSoC VCU TRD design application on ZCU106 from that source :

https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18842306/Zynq+UltraScale+MPSoC+VCU+TRD+2018.2+ +Design+Module+1#ZynqUltraScale%EF%BC%8BMPSoCVCUTRD2018.2-DesignModule1-1.3.6VCUGSTAPP
 

There are prebuild design sources and I've tried to find the latency of encoder with using gst-shark tool as you've suggested.

GST_DEBUG="GST_TRACER:7" GST_TRACERS="interlatency" vcu_gst_app /media/card/config/1080p60/Record/1080p60_HEVC_LOW.cfg

I got that results for interlatency :

0:06:56.034102613 2514 0x3793ea80 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)capsfilter1_src, time=(string)0:00:01.681336445;
0:06:56.034149828 2514 0x7fa8004cf0 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)omxh265enc-omxh265enc0_src, time=(string)0:00:00.674996550;
0:06:56.034258508 2514 0x7fa8004cf0 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)omxh265enc-omxh265enc0_src, time=(string)0:00:00.674997150;
0:06:56.034315054 2514 0x3793ea80 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)h265parse0_src, time=(string)0:00:01.681547666;
0:06:56.034382431 2514 0x3793ea80 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)qtmux0_src, time=(string)0:00:01.681615653;
0:06:56.034423835 2514 0x3793ea80 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)filesink0_sink, time=(string)0:00:01.681615653;
0:06:56.036735266 2514 0x3793ea80 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)queue1_src, time=(string)0:00:01.683847346;
0:06:56.036791182 2514 0x3793e9e0 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)capsfilter0_src, time=(string)0:00:00.325885619;
0:06:56.036814964 2514 0x3793ea80 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)capsfilter1_src, time=(string)0:00:01.683936885;
0:06:56.036990232 2514 0x3793e9e0 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)capsfilter0_src, time=(string)0:00:00.000038984;
0:06:56.037078340 2514 0x3793ea80 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)h265parse0_src, time=(string)0:00:01.684199021;
0:06:56.037101853 2514 0x3793e9e0 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)capsfilter0_src, time=(string)0:00:00.000025733;
0:06:56.037150958 2514 0x3793ea80 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)qtmux0_src, time=(string)0:00:01.684272259;
0:06:56.037192392 2514 0x3793ea80 TRACE GST_TRACER :0:: interlatency, from_pad=(string)v4l2src0_src, to_pad=(string)filesink0_sink, time=(string)0:00:01.684272259;

 

Is the latency of H265 encoder calculated this way ?

interlatency of  [v4l2src0_src to qtmux0_src] -  interlatency of [v4l2src0_src to h265parse0_src]

1.681615653 - 1.681547666 = 67 us

Kind Regards,

Serkan Ender Hakyemez

 

 

 

 

0 Kudos