• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 206 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.

Audio Codec (encoding) integration

chrisw957
Intellectual 480 points
Other Parts Discussed in Thread: OMAP3530

 

I'm using an omap3530, and I need some sort of audio encoding support-- either MP3 or AAC.  I've done MP3 on the ARM side, but it uses too much CPU.

From the TI Digital Media Software Inventory, it looks like AAC is my only option.  I've downloaded c64xplus_aacldenc_1_00_00_000_production.bin and extracted it, but it seems difficult to get this integrated into my ti-codecs-omap3530_1.00.01.bb recipie (I'm using openembedded). 

Are these the only instructions available?  http://processors.wiki.ti.com/index.php/How_do_I_Integrate_new_codecs_into_DVSDK

If I manage to get it integrated, will all I have to do is replace my existing cs.x64P on the target with the new one?  Will the ti gstreamer plugin work with the aac encode codec, or does it need changes as well?

Also, I found references to a "mega server" in the DVSDK 3.01.00.10 notes.  It seems to have more codecs, including aac encoding, but I'm confused as to why it would be created instead of just integrating the new codecs into the existing "combo".  DVSDK 3.01.00.10 is not available yet?

 

  • 0
    Intellectual 480 points

     

    Following the integration instructions from the wiki, I was able to build a new cs.x64P with aacldenc added into it.  I put it on the target, but gstreamer doesn't seem to find the codec when I try to use it.  I get "Engine_getConstName> Unable to locate alg" error.  Not sure if I need to rebuild gstreamer now, or???

    -c