How to add new codecs to IGEP GST FRAMEWORK

From IGEP - ISEE Wiki

Jump to: navigation, search

 How to add a new codec in IGEP-GST-DSP-FRAMEWORK

We will demostrate how to add a new codec inside the IGEP-GST-DSP-FRAMEWORK.

Texas instruments DSP Codecs page it's here.

DM3730 or OMAP3530 accept the codecs Omtimized for OMAP3530 & DM3730 or C64+ DSP based devices.

We will integrate a acc audio encoder in the codec server.


Step 1 - Download the Codec Package.

Get a codec from TI website C64XPlus_Audio_Codecs Product Download Page.

As you will observe the package name has "c64xplus" embedded inside it i.e. it is a generic MP3 c64+ decoder. Hence you can use this link to download & integrate this codec on non-OMAP3 platforms such as DM644x, DM646x, OMAPL13x. To reiterate, it is the same codec package on both OMAP3 and Davinci DVSDK sites.

Step 2 - Install the Package.

Once you have downloaded the codec package c64xplus_codec_x_xx_xxx_production.bin use the following command to install the package:


This will give a tar file extract that tar file.

Step 3 - Copy your desired Codec inside the server.

After extracting a tar file you need to copy this package into the Codec Server package.

e.g. in my case




Step 4 - Modifications inside the Codec Server

Once the Codec Package is integrated inside the Codec Server, the server needs to be configured in order to be able to use the new codec.

Now open file igep-dsp-gst-framework-3_20_00/codecs-omap3530_4_02_00_00/packages/ti/sdo/server/cs/codec.cfg

/* Declaration of new codec module */

var AACHEENC = xdc.useModule('ti.sdo.codecs.aacheenc.ce.AACHEENC');

The XDC file in the codec directory (i.e.AACHEENC.xdc) contains the different sections that are defined in the algorithm
that require to be mapped to defined memory sections by the server. Usually
this memory definitions are contained in the TCF file (''server.tcf''). For example to fulfill the requirements for the AACHE
encoder algorithm, and continuing with the variable defined before, the
following entries are added to the configuration file:

/* in my case with aacheenc */

AACHEENC.useCache = false;

AACHEENC.alg.watermark = false;

AACHEENC.alg.codeSection = codeSection;

AACHEENC.alg.udataSection = udataSection;

AACHEENC.alg.dataSection = dataSection;

/* Add the Algorithm to the server by adding
a new set to the ''Server.algs'' array.
For example to add the AACHEENCODER algorithm, the following entry needs to be
added */

name: "aacheenc", mod: AACHEENC , threadAttrs: {
stackMemId: 0, priority: Server.MINPRI + 3},
groupId : 2,

Step 5 - Validation

To minimize any errors during the building of the Server, add the codec to the validation entries in package.xs file of the server, which is in same directory as codec.cfg

/* in my case with aacheenc */
validate_one_codec( "ti.sdo.codecs.aacheenc", "AACHEENC" );

Step 6 - Add codec in gstreamer

Open file gstticodecs_dm3730.c located in  igep-dsp-gst-framework-3_20_00/gstreamer-ti_svnr962/src

directory and add following lines.

/* in my case with aacheenc */
"AAC Audio Encoder", /* String name of codec used by plugin*/
"aacheenc", /* String name of codec used by CE */
codecServer /* Engine that contains this codec */

Step 7 - Compile

Compile dmai, codecs and gst_ti in IGEP-GST-DSP framework, copy newly generated files cs.x64P and on board and test with  gstreamer pipeline.

gst-launch-0.10 alsasrc ! TIAudenc1 codecName=aacheenc engineName=codecServer ! filesink location=test.aac



Many thanks to Pratik G Shinde for this contribution.