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.

Integrating OMX component with new codec



Hello,

We have very urgent requirement for a Centaurus EZSDK based demo preparation, in which we need to integrate our IVAHD codec with OMX component.  Our IVAHD codec isn't XDM compliant yet.  So I understand following steps are involved in the development process:

1) Adding XDM interface to the codec

2) Creating RTSC codec package for the codec

3) Calling Codec CE APIs from OMX component.

Is this standard approach?  This will require some modifications/alterations of the code which we are trying to reduce/minimise given short timeline target.

Alternately can we remove CE calls from OMX component and instead directly call the codec APIs?  So this way we may be able to skip overheads of creating RTSC package or creating RTSC package and adding XDM interface both.  Does this approach have any major caveats?    Basically can we replace CE function calls from OMX component directly with actual codec APIs?

Please advise.  Thanks in advance,

Regards,

Purushottam

  • Hi,

    Yes, the steps outlined 1-3 is the standard and best supported approach.

    However, you can certainly have your OMX component  directly interface with your code. Bypassing XDM/CE layers will then require your OMX component to take care of your codec's creation, initialization, activation, deactivation and processing stages. You may then want to directly use Framework Components as a utility layer for creation, initialization, activation, deactivation  and all related resource management. You can examine existing CE implementation layer as reference.

    You can check the following link for some common info and Q&As about Framework Components:
    http://processors.wiki.ti.com/index.php/Framework_Components_FAQ

    Best regards,

    Murat