• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 262 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.

capture process EVM demo vs IPNC .

TIG
Intellectual 270 points

Hi.

 

I want to know whether to have the same software layer (Application? API ? ) with IPNC and EVM.

I want only to compare the capture processing.

 

◆ EVM demo and IPNC use video for linux 2 for capture. EVM demo and IPNC use dvsdk

◆ EVM demo (encode) and IPNC (AV_server) are different the structure of the application. The kind of the input camera is also different.

 

  • 0
    TI__Mastermind 19985 points

    Hi,

    DM36x IPNC Reference Design does not use V4L2 layer for capture. We have developed some capture drivers which meet IP camera needs much better. So IPNC capture processing flow is similar to EVM but the actual implementation is different.

    IPNC Ref Design use DVSDK for codecs, framework components, codec engine, linux support package (for everything except capture drivers).

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.

  • 0 in reply to Anshuman Saxena
    Intellectual 270 points

    Hi Anshuman, thanks for your replay.

    I saw the document Application_DesignGuide_IPNC_DM365.  (page23)

    The algorithm flow using video for linux two has been described there.

    So, I think IPNC use v4l2.

  • 0 in reply to TIG
    TI__Mastermind 19985 points

    Hi,

    We use V4L2 IOCTLs only for display driver. As far as the figure 11 in the design guide is concerned, i think it is a mistake and need to be corrected. We will fix it in next release.

    For capture processing, we do not use V4L2 in IPNC Ref Design.

    Regards,

    Anshuman