• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 471 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.

OMX based components and CodecServer

Joern
Genius 3055 points

From several threads (from this one to that) I came to that entry, where John Bency proclaims: "Also, A8 based OMX components are not planned for EZSDK."

That brings up two basic questions for me:

  1. We use the H.264 encoder OMX component for encoding - and until now I assumed that the whole work (at least since the newest EZSDK 5.03.01.15) would have done by the HDVPIC (compression) and ARM (process control and RTP streaming). Now this assumption seems wrong for me, all that sounds for me like if the encoding must be controlled from DSP side, as no OMX components are made for A8?
  2. Almost completely separately from that encoding process we have to handle some data provided by a FPGA, and as we have to calculate a lot around this data we handle most of this by a codec written for the DSP, embeded into a codec server and controlled from ARM side via the codec engine. But the codec server - asaik - must be the only program running at DSP, several jobs have to be placed into several codecs within that codec server. So where gets the OMX component for H.264 encoding control running?

Hopefully,
best regards,
Joern.

  • 0
    Expert 2030 points

    Hope this helps.

    OMX actual components typically run on HDVICP and HDVPSS. They can be initialized and controlled from A8 based client application via distributed openmax based proxies.

    OMTB is once such application running on A8 that does video encode, even while the DSP is held in reset.

    This is in example-application folder. There are many other demos that can be launched from omx folder within the EZSDK

    As to second question, I would like to do the same. But the current EZSDK does not allow codec engine and OMX to be run from the same application.

    See my post here.

    May be a couple of questions like this help attract attention to this problem.

    RV

     

  • 0 in reply to RV
    Genius 3055 points

    Thank you very much for your information concerning running OMTB while DSP held in reset. That actually helps me still being hopefully, that somehow my codec engine based implementation will be able to run while the OMX based H.264 encoding is running as well.

    Further digging around unfortunately I can do not much before middle of next week - if I find anything, I'll post it here, of course. But maybe until then someone other will have some more concrete hints than Chris could spend for the moment...

    Regards,
    Joern.

  • 0 in reply to Joern
    Expert 2030 points

    see this post http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/149505.aspx. We fixed some of the issues to get c6accel running.

    Let me know if it works out for you.

    RV