• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 425 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.

DaVinci TMS320DM816x

Ignat Lozover
Prodigy 20 points


We have some questions based on the documentation on the website on DaVinci TMS320DM816x.
 
  1) The Product bulletin states "Industry’s highest performance video engine enables a near-zero latency". What is latency of 1080p60 encode/decode?
 
  2)  It also states "three simultaneous 1080p60 frames per second (fps) video streams". Does it support two bidirectional channels of HD 1080p?
 
  3)  Does the Hardware and/or SDK support (DVB/ASI) MPEG Transport streams?
 
  4) AES128 Encryption support?  Thanks.

  • 0
    TI__Mastermind 43875 points

    Ignat,

    For some latency information please see the following thread.

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/int-dm81x/f/518/t/94334.aspx#328276

    BR,

    Steve

  • 0 in reply to Steve Clynes
    Prodigy 20 points

    Thanks Steve, but there seems to be an issue with the link.  Please provide another thread link.

  • 0 in reply to Ignat Lozover
    TI__Mastermind 43875 points

    Sorry, I didn't realize that it was an internal TI link.

    Here is a synopsys of the thread...

    For question related to Latency - Video Encoders (H.264 and Mpeg4/H.263) provided by TI on DM816x/DM814x are designed for low latency applications. These can take uncompressed data with a minimum unit of 1 MB row (16 lines) and can provide compressed bit-stream out with a minumum unit of 1 slice (compressed unit used for packets).
    Now based upon what is the slice rate - one can compute the latency at which compressed data will be available at encoder output
    Example - assume each frame has 20 slices then each slice is available at the output of the encoder at (33 ms / 20 + 0.3 ms intial overhead) time interval =~ 2 ms
    So you should be able to compute the latency for you application based upon slice rate.

    BR,

    Steve