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