• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 413 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.

DM368 encoding rate is slower than DM365!!!

Haran Ashok
Expert 1175 points

Hi,

We have an application which basically does streaming and we ran the application on DM365 and DM368. Our application crashed for higher configurations in case of DM368 but on DM365 it was performing perfectly alright so we started profiling our application.When we profiled the encoding time alone for DM365 we found out that the encoder took 16ms to encode the data but in case of DM368 it took 24 ms to encode the same data.

When we profiled AAC encoding alone which was totally ARM intensive there was a 30 % improvement in the performance on DM368 compared to DM365. So this proved that ARM was actually working at the rate as expected but the hardware encoder was not proper.Currently we are using  DVSDK 2_10_01_18 for both DM365 and DM368. Is there any particular encoder libraries that needs to be changed for DM368 since now we are using the same libraries that we use for DM365. Can anyone please explain what is the expected behavior in case of encoding on DM368 as compared to DM365.  

Regards

Haran

  • 0
    TI__Expert 8465 points

    Hi Haran,

    Can you please tell version of the encoder?. And there is no need to change encoder to run on DM368. But you may be interested in following post for system optimization.

    http://e2e.ti.com/support/embedded/multimedia_software_codecs/f/356/t/99812.aspx

  • 0 in reply to Veeranna Hanchinal
    Expert 1175 points

    Hi Veeranna,

    Thanks for your reply.The version of the encoder we are using is 2.3.00.0.6. I have seen the link mentioned and have optimized my config file according to it and i am seeing a slight improvement in the performance of the encoder(1-2ms).

    Another observation is that when we run a standalone H264 Application,the H264 encoder performs better than DM365.

    But when we run H264 standalone application, simultaneously with an ARM intensive application we observe that there is a degradation in the performance of the encoder on DM368.Similar behavior is not observed on DM365.

    We needed a clarification.We are supplying 1.35V to DM368 operating at 432MHz.But the migration guide from DM365 to DM368 mentions that we should use a higher power supply for DM368 @432MHz(Table 2. Minimum Required Changes "Comments Section").Is our understanding correct?

    And could this affect the performance of the encoder when an ARM intensive application is running in parallel.

    Regards

    Haran

  • 0 in reply to Haran Ashok
    TI__Expert 8465 points

    Hello Haran,

    I don't have expertise in power related information, I have asked corresponding people to look into this post. 

    And with respect to software codec functionality, one difference will be running on DM365 and DM368 is; codec will run faster on DM368-HDVICP and it might be  waiting for ARM926 resource to get execute to frame post processing. So can you check on this, Make sure your other other ARM application  will not make H264 encoder to wait. 

  • 0 in reply to Veeranna Hanchinal
    Expert 1175 points

    Hi Veeranna,

    We are actually using the sample standalone application provided by the TI DVSDK and the ARM standalone application does not have anything to do with providing resource to the HDVICP.These are the observations on DM365 and DM368.

    1.Running standalone H264 encoder application only.

    Configuration                       DM365             DM368 

    960*540                               16ms                14ms

    2.Simultaneously running an ARM intensive application which does a file read/write operation or socket write application which is ARM intensive together with the H264 standalone application.

    Configuration                       DM365             DM368

    960*540                               16ms                18-22ms.

    Why is an ARM intensive application running on DM368 affecting the H264 standalone application and the same is not true with DM365 where it is not getting affected at all.

    Is this an observed behavior on DM368?

    Regards

    Haran

  • 0 in reply to Haran Ashok
    Expert 1175 points

    Hi Veeranna,

    Just to update you.Now i am able to get the expected performance from our DM368 custom board.The problem due to which we got a decreased performance was that i was configuring the UBL to provide a 1x DDR clock instead of a 2x clock which had a major impact on the H264 hardware encoder performance on DM368 due to some syncronization issue but now i am able to get the expected performance on the  DM368 custom board.Thanks for ur support.

    Regards

    Haran