AAC/MP3 Ittiam integration

Hi Andrea,

I'll work on a quick tutorial on how to integrate these codecs today and how to use them. I'll post it hopefully today or tomorrow.

Regards,

Cristina

Did you record from microphone in your test?

thank you.

Andrea

Hi Andrea,

Yes, I record from a microphone and then encode the audio to either mp3 or aac.

Regards,

Cristina

How can I record from micophone?

I'm trying with:

gst-launch alsasrc ! audio/x-raw-int, width=16, depth=16,  endianness=1234,

channels=2, rate=44100, signed=true ! filesink location=/audio.pcm

but audio.pcm is alway empty.

I'm using 2.6.29 kernel with DM355 audio support enable, I can listen mp3 file, but I can't record anything :-(

thank you

Andrea

Hi Andrea,

This is the pipeline to record from the microphone, yours should be fine too,

gst-launch alsasrc ! audioconvert ! audio/x-raw-int, width=16, depth=16,  endianness=1234, channels=2, rate=44100, signed=true ! filesink location = audio.pcm

I'm guessing the problem could be that you have not enabled the microphone, or set the volume properly.

To activate the microphone:

amixer sset 'Left PGA Mixer Mic3L' on
amixer sset 'Right PGA Mixer Mic3R' on

To set the volume type:

alsamixer

You can configure PCM and line DAC to higher levels. If you press F4, you can increase the level of the microphone's volume.

To hear the pcm file you recorded on your leopard, you can use the following pipeline:

gst-launch -e filesrc location= /audio.pcm ! audio/x-raw-int, width=16, depth=16, endianness=1234, channels=2, rate=44100, signed=true ! alsasink

Hope this helps.

Regards,

Cristina

Hi Cristina,

I'm new on this forum and i'm working with the LeopardBoard from a few days.

I tried your pipeline for the registration, but the audio signal  is distorted. Trying the same pipe without the "audioconvert" plugin works better. Is a my error  or the evidence you too?

Regards,

Lorenzo

Hi Lorenzo,

I haven't notice that. Audioconvert is an element that converts audio to different formats, however we are setting the caps after it on that pipeline, so it shouldn't be necessary.

Regards,

Cristina

Andrea,

FYI,

There's a way to save the alsamixer settings, so you don't have to do it all over again every time you start your board. Once you turned on the microphone and set the volume, you can run:

alsactl store

And the next time you boot your board,

alsactl restore

And it will use the configuration you stored previously.

Regards,

Cristina

Hi Cristina,

i tried to encode the audio to mp3 or aac following these instructions:

www.ridgerun.com/blog

But the Leopard gives :

WARNING: erroneous pipeline: no element "dmaienc_mp3"

I'm working with the latest  SDK version...

Thank you.

Regards

Lorenzo

Hi Lorenzo,

There are a couple of steps that need to be followed in order to use these codecs, hopefully they will be post here soon. In the mean time, you should download the codecs package from TI web site.

Hi Cristina,

are these steps in SDK configuration?

I see that in "Proprietary Software"  there are some Gstreamer DMAI Plugins (Build DM355s Codec configuration instead of standard DM355 codecs)...

Have i to select them?

Thanks

Regards

Lorenzo

Hi Cristina,

My interest is to record from microphone and to stream audio using Dm355 and gstreamer.

I have succeeded in recording a pcm file and playing it but how can i stream via UDP between two Dm355.

Can u help me ?

Regards

Idriss

Hi Chistina,

I'm following steps from

elinux.org/RidgeRun_LeopardBoard_SDK_Hints

It says

"Apply the patch for the codecs to include the parameters definitions"

What are the patches to include parameter definitions?

If I pass that step, I get error

----------------

js: "/home/tunca/DM355SDK789311/proprietary/xdctools_3_10_05/xdctools_3_10_05_61/packages/xdc/xdc.tci", line 299: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: can't locate the package 'ittiam.codecs.mp3_dec.ce' along the path:

...

Ensure that the package path is set correctly.

----------------

Can you help me with this?

Thanks

Hi,

I updated the page with the patches, you can now go back to that step. Now, regarding the error that you got, did you place the codecs in the directory DM355SDK789311/proprietary$ as suggested on the wiki? It seems that the package can't be found because it is not in the correct place.

Since this still needs more work done, any suggestions or comments are appreciated.