• State
  • Locked Locked
  • Replies 0 replies
  • Subscribers 97 subscribers
  • Views 216 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.

Execution of H.264 encoder and DM36X resizer

Rohan Babtiwale
Prodigy 160 points

Hi,

I am using H.264 encoder in one thread and H.264 decoder and dm365resizer in another thread. Currently the scratch group Id is same for encoder,decoder and resizer. In this case,  according to http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/t/7796.aspx#31125  the codec engine sequentialize these operations by taking care of the scheduling and locking.

I want to use the encoder and the dm365 resizer (on decoder side) concurrently. So I compiled the encoder and resizer with different group Ids. It works fine if 'alg_imcop_lock' is put for process() call. But the maximum performance achieved is 15 FPS for 720P resolution. If the 'alg_imcop_lock' is removed then the resizer hangs in process() call after first frame. Is there any way to use h.264 encoder and dm365resizer concurrently without using any mutex lock??