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.

iMX library or VICP signal processing library



Hi All,

I am new to VICP. i have started exploring the VICP documents and sample applications.

In this i have found there are two libraries available one is iMX lib and another is VICP signal processing library.

I came to knew that VICP signal processing library uses iMX library.

As per the VICP signal processing library's document it is more optimized way to use than the iMX library.

But VICP signal processing library does not have API's for some functions available  with iMX library like motion estimation.

So my question is that if i really want to improve the performance of my DSP algorithm which library i should have to use, VICP signal processing library or iMx library.

From the sample application, lab1, lab2... ,i came to knew that sequencer can be used with iMx library, i want to know whether i can use VICP signal processing library with sequencer just like iMx library or not?

 

Any pointer will help me to move further.

 

Thanks,

Zuber Saiyed

 

  • Zuben,

     

    The VICP signal processing library is designed to maximize ease of use for the H/W accelerator. If you are new to using VICP, I would recommend starting with the VICP Lib APIs as described in the user’s guide. We are currently working on extending the list of supported APIs and you will see additional APIs being supported in future releases. The VICP Lib abstracts the lower level H/W details and the associated SW. Note, the H/W details and lower level SW API details are only made available with special licensing. Thus, if you see need for supporting a particular API with the VICP Lib, please let me know and we can try and prioritize its support. If you need the support in short term, we may be able to provide an interim release to support you.

     

    Regards,

    Gagan

     

     

  • Thanks Gagan,

    I appreciate your help. 

    I am eager to know about my second question, that whether i can use VICP signal processing library just like iMX library with sequencer or not?

    I think VICP signal processing library only uses iMX, does it use sequencer also, internally?

    If not can i use this API's with sequencer to reduce the load of DSP?

    i found VICP signal processing library's APIs are like wrapper APIs on iMX library, so does it add more overhead or it is light weight?

    is there any performance comparison available between iMX APIs and VICP signal processing library's APIs?

     

    I appreciate if i can get answers in Yes or No with explanations, as these questions are key questions in decision making for me.

     

    Thanks,

    Zuber Saiyed

  • Zuber,

    • I am eager to know about my second question, that whether i can use VICP signal processing library just like iMX library with sequencer or not?

    The VICP Library abstracts the lower level libs from the user.  Thus, if you use the VICP Lib, you don't have to call the iMX Lib and the sequencer lib APIs.

    • I think VICP signal processing library only uses iMX, does it use sequencer also, internally?

    Yes it does. Please refer to the UG and the provided examples for each kernel to see how the APIs work.

    • i found VICP signal processing library's APIs are like wrapper APIs on iMX library, so does it add more overhead or it is light weight?

    It is light weight. We are working on making the APIs even more flexible by allowing user to pipe multiple APIs and reduce the overhead of the abstraction layer further.

    • is there any performance comparison available between iMX APIs and VICP signal processing library's APIs?

    Other than the startup overhead, the APIs performance is the same.

    Regards,

    Gagan