How to add new codecs to IGEP GST FRAMEWORK

From IGEP - ISEE Wiki

Revision as of 11:14, 3 February 2012 by Manel Caro (talk | contribs) (Created page with '=  How to add a new codec in IGEP-GST-DSP-FRAMEWORK = <span lang="EN-US" />We will demostrate how to add a new codec inside the IGEP-GST-DSP-FRAMEWORK. Texas instruments D…')

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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

<span lang="EN-US" />We will demostrate how to add a new codec inside the IGEP-GST-DSP-FRAMEWORK.

Texas instruments DSP Codecs page it's here.

<span lang="EN-US" />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.

Procedure

Step 1 - Download the Codec Package.

Get a codec from TI website [http://software-dl.ti.com/dsps/dsps_public_sw/codecs/C64XPlus_Audio/index_FDS.html 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.

<o:p> </o:p>

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:

./c64xplus_codec_x_xx_xxx_production.bin

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

<span lang="EN-US" />c64xplus_aacheenc_1_20_005_production/dm6446_aacheenc_1_20_005_production/packages/ti/sdo/codecs/aacheenc 

to 

igep-dsp-gst-framework-3_20_00/codecs-omap3530_4_02_00_00/packages/ti/sdo/codecs

=== Step 4 - Modifications inside the Codec Server ===

<o:p> </o:p>

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

<span lang="EN-US" /><span lang="EN-US">/* Declaration of new codec module */</span> <span lang="EN-US">var AACHEENC = xdc.useModule('ti.sdo.codecs.aacheenc.ce.AACHEENC');</span> <span lang="EN-US">/*</span> <span lang="EN-US">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: */</span> <span lang="EN-US"><o:p> </o:p></span> <span lang="EN-US">/* in my case with aacheenc */</span> <span lang="EN-US">        AACHEENC.serverFxns = "AUDENC1_SKEL";</span> <span lang="EN-US">        AACHEENC.stubFxns = "AUDENC1_STUBS";</span> <span lang="EN-US">        AACHEENC.useCache = false;</span> <span lang="EN-US">        AACHEENC.alg.watermark = false;</span> <span lang="EN-US">        AACHEENC.alg.codeSection = codeSection;</span> <span lang="EN-US">        AACHEENC.alg.udataSection = udataSection;</span> <span lang="EN-US">        AACHEENC.alg.dataSection = dataSection;</span> <span lang="EN-US">/* 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 */</span> <span lang="EN-US"><o:p> </o:p></span> <span lang="EN-US">{name: "aacheenc", mod: AACHEENC , threadAttrs: {</span> <span lang="EN-US">        stackMemId: 0, priority: Server.MINPRI + 3},</span> <span lang="EN-US">        groupId : 2,</span> <span lang="EN-US">    },</span>

<span lang="EN-US" />

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

<span lang="EN-US">/* in my case with aacheenc */</span> <span lang="EN-US">validate_one_codec( "ti.sdo.codecs.aacheenc", "AACHEENC" );</span><br>

<span lang="EN-US" />

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.

<span lang="EN-US"><o:p> </o:p></span><span lang="EN-US">/* in my case with aacheenc */</span> <span lang="EN-US">{
"AAC Audio Encoder", /* String name of codec used by plugin*/
"aacheenc", /* String name of codec used by CE */
codecServer /* Engine that contains this codec */
},
 <!--[if !supportLineBreakNewLine]-->
<!--[endif]--></span>

<span lang="EN-US" />

Step 7 - Compile

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

<o:p> </o:p>

<o:p>References</o:p>

<span style="color:windowtext;text-decoration:none;text-underline:none" />

Thanks

Many thanks to Pratik G Shinde for this contribution.