Part Number: TMS320DM365
Hello,
It has been observed that upgrading the de-interlacing algorithm version to 2.0 in DM365/DM368 has dramatically reduced the mean frame-rate delivered by AV_Server from 25 Hz to 21 Hz. While it has been acknowledged that this version of the algorithm runs for longer (additional clock cycles) in each iteration, no mechanisms to address the impact of this seem to be available.
When using v1.9 of the de-interlacing algorithm, AV_Server is able to capture a new frame in 33.9 ms, which is within the 40 ms lapse available. However, when using v2.0 ceteris paribus, this figure increases to 47.7 ms (mean), indicating a loss in frame-rate corresponding to 4 fps (7.7 ms per frame). The location of this lag is restricted to the de-interlacing thread since no other modifications in the static code have been done.
That said, would there be any way to reduce the time lag, either through memory increase or otherwise, to counter the loss of frame-rate caused by the de-interlacer?
Thanks,
Anirudh