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.

Hardware De-Interlace for TI816X VS2 demo

Hello ALL,

 

I am working  with TI816X VS2 daughter card and able to run vs2 demo successfully.

But I want to use Hardware de-interlacer in my VS2 demo. I walk through code and find that IL_CLIENT_DEI_ALGBYPASS flag is true in VS2 demo code.

So it seems that hardware de-interlacer is bypassed in VS2 demo. So I make IL_CLIENT_DEI_ALGBYPASS flag as false and try to run demo and runs fine.

Now I have query as below.

1) Above configuration are true to use hardware de-interlacer?

2) How can I find that my VS2 demo is using hardware de-interlacer?

3) What are the configuration to use hardware de-interlacer?

4) Is there any documents  that explain to use hardware de-interlacer?

 

Thanks

Hitesh Patel

  • Hello,

    We are looking into this and will get back to you soon.

    Regards,
    Marc

  • Hi Marc,

    Thank for looking on query.

    Here I want to add my observation on above experiment.

    I configure IL_CLIENT_DEI_ALGBYPASS flag as false in VS demo and run demo for 1 hour.

    But after few minutes video is hang and my display is giving last frame of video. I could not find the issue here.

    I will appreciate your help and support.

    Thanks & Regards

    Hitesh Patel

     

     

     

  • Hi Hitesh

    Your modifications are correct to enable the DEI. As of now SDK doesn’t offer any other configurations other than DEI enable/disable options

    regards

    shiju

     

     

  • Hi Shiju,

    Thanks for the reply.

    So, does it mean that by enabling DEI as Hitesh suggested, the H/W DEI actually comes into effect ?

    If yes, then why does it stops giving video suddenly ? Is there any issue with using H/w deinterlacer with this particular SDK only ? Will it get resolved in next release of SDK?

    Or it is a major bug and blocking factor ?

    Please confirm where exactly the issue lies.

     

    Thanks again,
    Sweta

  • Sweta,

    please let me know the SDK version your working with?

  • Hi Shiju,

    I am using EZSDK_5_11.

    Thanks,
    Sweta

     

  • Hi Sweta,

    We have been verified the VS2 demo with DEI in enabled mode.  There was Ducati MHz issues while enabling the DEI and that result to a few frame drops, but no crash.  In SDK 5.0.0.11, we use the HW mosaic feature and we have observed the display hangs random due a silicon bug popes-up with HW mosaic feature.  This usually happen after an hour.  Are you seeing all the channels freezes in the display or a few freezes and others are working?  VS2 will be removed from all future SDK releases as it will be supported in RDK from VS BU.  VS RDK is specifically designed for Video surveillance applications and the first release is planned by August End.

    Regards Shiju

     

     

  • Hi Shiju,

    Thank you very much for the update.

    When we enable HW mosaic, demo stops giving video to TV after 1/2 hours and we see black frame only. No video data.

    We do use 2x2 (total 4 channels) and we don't see video in any of the 4 channels when this happens.

    Couple of more questions:

    1) Does this mean that there is no work around for the silicon bug of hw mosaic feature or it is planned to be fix in next silicon version ?

    2) Can you please provide me details about RDK ? Please provide me link from where I can download this SDK.

    3) Will RDK be super set of ezsdk ? What all features will be supported ? Will RDK also have Openmax and HDVPSS source code ?

    We are EA partner of TI.

    Reason behind asking these questions is, our product falls in video surveillance category.

    We will need to modify HDVPSS and Openmax to fulfill our end product requirements.

    Thanks again,

    Sweta

  • Hi Sweta

    It seems like you are hitting with HW mosaic related silicon bug.

    My answers are inline

    Couple of more questions:

    1) Does this mean that there is no work around for the silicon bug of hw mosaic feature or it is planned to be fix in next silicon version ?

    [Shiju] There is no workarounds available for this HW mosaic issue. Only option is we shouldn’t use this feature. In RDK we are using the SW mosaic feature to overcome these issues.

    2) Can you please provide me details about RDK ? Please provide me link from where I can download this SDK.

    [Shiju] RDK is in progress and the first release is planned for August end. I will update you once the release is out

    3) Will RDK be super set of ezsdk ? What all features will be supported ? Will RDK also have Openmax and HDVPSS source code ?

    [Shiju] RDK is a non-omx based framework specifically designed for video surveillance applications based on simple Bios & IPC. RDK integrates HDVPSS & IVA codec to support VPSS & video functionalities.  As your products product falls in video surveillance category, RDK would be a better option for your developments

    Regards Shiju

     

     

  • Hi Shiju,

    Thanks for update.

    If RDK is non-omx based framework, I need more information about data sharing and data flow path between ARM, DSP and HDVPSS.

    We will need to perform encode, decode, deinterlacing and analytics. Captured data needs to be available on ARM side (evenif captured by HDVPSS).

    Would it be possible with RDK release of August ?

    Please give me some more details about how open max will be replaced with any other component so that we can plan accordingly.


    Thanks,
    Sweta

     

  • Sweta,

    August end release of RDK will be capable of perform capture, encode, decode, deinterlacing, scale & display along with graphics.  The captured data will be available on A8 as well.  We have architectured the RDK in such a way that we do have various links (components) integrates HDVPSS drivers & IVA codec.   You can make your chain by connecting various links as per your app data paths.  Almost all & a few more features will be available in RDK release compared to the current OMX SDK

     

    Regards

    Shiju