• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 184 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

dm6467T

Xavier Tisaire
Intellectual 310 points

Hi all,

 

I'd like to know the normal delays with the dm6467T encoding with h.264. With the demo we're getting 1.8 secs, and shortening some buffers 1,2 secs, but I assume that it can be optimized.

Could you please tell me if the latency could be lower, and how much?

 

Regards,

Xavi

  • 0
    TI__Expert 5130 points

    Xavi,

    Can you elaborate on how the delay is calculated? Is it the overall system latency or the codec latency due to CE/FC framework?

    If you measure the time taken for a process() on ARM, it will be slightly higher than the actual process() on the DSP. This latency is due to the message passing, address translation, cache maintenance operations.

    On DM6467, we observed a delay of ~0.4 ms per frame process() call. This translates to 12 ms framework latency per second.

    One of the major contributor to this delay is the cache invalidate / writeback operations that occur on the DSP. I think this is the reason why you see a lower delay by reducing the buffer sizes.

    If the codec doesn't touch the input / output buffers through CPU, you can optimize some of these operations. This can be done through the CE configuration variables.

    Regards,

    Anand Balagopalakrishnan