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.

IPNC RDK5.1 DEI issue

Other Parts Discussed in Thread: TVP5151

Hi,

I am currently working on a Digital Video Encoder based on DM365. In the analog video capture side, we are using TVP5151 chip as the encoder. When we enable DEI module in SDK5.1, av_server process gets hang in the Encode thread. We suspect that this issue is caused by both Encode thread and DEI accessing the encode engine at same time. So we added a lock in DEI and encoder thread for mutual exclusive access. With this change, encoding was successfull, but capture frame rate reduced from 25 fps to 20fps. Following is the streaming details:

Module   | Avg Time/Frame | Frame-rate | Total time | Total Frames |
 CAPTURE  |          48.40 |      20.66 |      43609 |          901 |
 DEI      |          45.09 |      22.18 |      40624 |          901 |
 RESIZE   |          12.98 |      77.07 |      11691 |          901 |
 ENCODE0  |          42.67 |      23.44 |      38446 |          901 |
 STREAM   |           0.25 |    4058.56 |        222 |          901 |

We were able to achieve 25fps with DEI module enabled in IPNC RDK 3.0.(There also we had to implement the locking mechanism) The major difference we find between RDK5.1 and RDK 3.0 in the DEI module is that in RDK5.1, DEI 2.0 is used. Does this have any dependency on the reduction in frame rate?

Any help would be greatly appreciated

  • Hello,

    The deinterlacer used is of higher quality and in turn takes more cycles comapred to older one, but this can achieve 30fps for D1 resolution as in v5.1

    Can you please give more details on usecase? is this D1 ? what the flow path? 

    Also, can you check thread priority and comapre wioth IPCN RDK codebase?

    Regards,

    Raghu

  • Hi,

       Thank you for your reply.

       We are currently using D1 and flow path is:

               Capture->Dei->Resize->Encode

       DEI thread priority is same as IPNC RDK codebase - "OSA_THR_PRI_MAX-2"