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.

H264 Video Encoder locks my audio capturing

Other Parts Discussed in Thread: OMAPL138

Hi,

I'm using an OMAPL138 EVM and Im using the dmai video_encode_io1_omapl138.x470MV from the dmai examples (Beta release from sdk 4.00 which is practically Brijesh branch). Before I ran this application in my evm board I execute arecord to capture some audio data. The problem is that when I'm doing this, the audio record process gets locked. I was wondering if this is could be a DMA conflict between the server device configuration (DSP) and the resources used by the audio capture. Im using the cs1omapl138_1_00_00-v2_setup_linux.bin codecs package.

What I'm doing is the following:

1) Boot the EVM, and when the kernel loads, I ran arecord. This throws me some garbage in the console letting me know that I'm recording.

2) Then in the linux console I go to dmai_examples folder and execute the encode app:

                    ./video_encode_io1_omapl138.x470MV -c h264enc -i  video.yuv -r 720x480 -o encode_file --benchmark

When I execute this the arecord process gets locked, and the output that I'm seeing in the console stops, letting me now that the process has been actually lock.

I need some help to debug this or how do I know if the codec has something in the configuration that is locking the audio, if this is the problem. This problem has been locking me to continue with a complex application need it for a customer.

Also what Im seeing with this test on video_encode_io1_omapl138.x470MV, is that the bechmark is giving me this output:

Frame 1: Read UYVY frame size 691200 (720x480) from file
Read time: 21681us
[2] Encode: 59581us
File write time: 1843us
Total: 83342us

 Frame 2: Read UYVY frame size 691200 (720x480) from file
Read time: 21521us
[3] Encode: 59708us
File write time: 1737us
Total: 83137us

 Frame 3: Read UYVY frame size 691200 (720x480) from file
Read time: 21146us
[4] Encode: 59676us
File write time: 1207us
Total: 82136us

The total time to encode a frame is practically 82 ms. I was wondering if this performance for the encoder is good. Because this means approximately 12 fps. Am I right?

Thanks in advance.  It will be helpful any suggestion

Jorge

RidgeRun Embbeded engineer