Codec modules inherits Icodec interface

Hi Benlu,

Sorry I am not sure I fully understood your question. Are you using a TI codec and TI server? If so there should not be any build issues out-of-box, unless you have made changes to the files. Can you give more details about what you did and show us the build log with the error message? Please also specify the versions of codec engine, codecs and DVSDK (if any) you are using.

For what it's worth, the codec interface inheritance is defined in the file ti/sdo/codecs/h264enc/ce/H264ENC.xdc file for the h264 encoder for example. For your own codec you should find it under a similar path. The 'inherited interface' specifies what category the actual codec library belongs to, whether its an IVIDENC1 (video encoder), IAUDDEC1 (audio decoder), IUNIVERSAL (generic algorithm) etc. So it needs to match the interface that has been implemented by the codec library.

Best regards,

Vincent

Vincent,

I'm using Ezsdk version 5_02_02 and TI lastest g729ab codec, I don't make any changes to g729ab codec files. The G729ABENC.xdc or G729ABDEC.xdc file defined the interface inherits from speech1 interface, which inherits from Icodec.

I have changed speech1 interface source codec in ti.sdo.ce.speech1, and want to port the speech1to example extensions path without effectting any other speeh1 using in codec engine. I have changed the file .xdc inheritance to extensions path, but it's still using ti.sdo.ce.speech1 interface.   

Hi benlu,

If you are interested in developing your own interface extension, make sure you have read the Codec Engine Application Developers' Guide: http://www.ti.com/lit/pdf/SPRUED6, as it contains valuable information on how to create one from scratch. Extending an interface is useful if you feel the need to change the SPHENC1 and SPHDEC1 interfaces defined by XDM, so that they match your new codecs (I presume you are trying to write your own speech codec, correct?). Most users are fine with the predefined interfaces, so they can simply write their codec libraries to conform to those interfaces without having to create an extension package. But maybe your codec/algorithm is different enough to justify doing so.

After creating your extension package, you should rebuild it using the xdc command, as described in the Guide. In addition, you need to rebuild your codec package against the extension package after modifying its inheritance in its .xdc file.

An alternative to creating an extension package that some people find simpler is to modify their codec to implement the IUNIVERSAL interface. This is a generic interface for algorithms that have significantly different semantics from the average codecs, and thus require exchanging different parameters between the application and the algorithm. If you are interested you can read up on it here: http://processors.wiki.ti.com/index.php/Getting_started_with_IUNIVERSAL

Best regards,

Vincent

Vincent,

I'm sorry, I don't state the problem clearly. I have changed the source code from ti.sdo.ce.speech1 interface, which inherits by g729. Certainly, I re-built the speech1 interface, and it's been called by app successfully.

I changed the g729 codec package path which defined in package.xdc and server's cfg file also been changed, it's also can be apply in applications. But when I modified the G729ENC.xdc or G729DEC.xdc file and re-built the g729 codec package to change the ti.sdo.ce speech1 interface to ti.sdo.ce.examples.extensions.speech1, app can't open codec G729enc and G729 dec... why?