• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 102 subscribers
  • Views 2491 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 DM6467 H.264 encoders

Lynne Schaffer
Prodigy 185 points

I have a customer who is looking at the DM6467 for their new design. The want to use the device to do H.264 video encoding at 1080p30 resolution with a roadmap to 1080p60. They’ve been looking at the available codecs online (http://focus.ti.com/docs/toolsw/folders/print/dm6467codecs.html) and have some questions about the implementation:

 

n  Will we have 1080p60 main and high support in the codecs later in the year?  Also, they need level 4.1 and these are all level 4 – when will we have level 4.1 support?

n  Their data is transported in RGB and our codecs show only YUV.  Is there an RGB implementation?  Could they do color space conversion in the chip?  Or would they need to do it externally in the interface FPGA?

n  Finally, they really need to figure out latency.  It is not obvious how they can figure that out from the data on the website.  Could you help me to figure this out?

 

 

  • 0
    TI__Intellectual 1970 points

    Lynne,

    We have the 1080p30 encoder on DM 6467, but do not have a plan to do 1080p60 encoder on DM6467. You can look at DM 8168 for 1080p60 encode support. 

    Regarding Level 4.0/4.1, the major difference would be the max bit rate that can be supported. We can support bit-rates upto 24 Mbps on DM6467, and hence TI codec claims level 4.0 compatibility. Level 4.1 will require higher bit rates to be supported.

    We can do YUV to RGB conversion using the VDCE on the DM6467. So the colour conversion can be done on the chip.

    Latency : Are we looking at the encoder latency?Or the total end-to-end latency ? Each 1920x1080 frame of encode will take <33 ms. The encoder expects one full frame to data to be captured and then passed on to the encoder in YUV 420 format.

    Regards,

    kapil

     

  • 0 in reply to Kapil Ahuja
    Prodigy 60 points

    hi Kapil

    I see you said that you can convert YUV  to RGB by using VDCE of DM6467, but I can not find any other information or documents relating to this function. Will you plz give me some tips or just tell me where you found how to realize this when writing my own  xDAIS ALGs ?

    thanks.