Could I call VICP Signal Processing Library API functions when h.264 codec engine is running?

Hello Dennis,

Which chip it is ? If it is DM6467,  then you cannot use the VICP library because DM6467 doesn't have a VICP but a HD-VICP specialized at codec encode/decode. The VICP is more flexible and exists on DM64x/DM644x device but not on DM646x device.

Thanks for your answer, Victor.

We are now working on dm6446,  dm6467 is just on our roadmap.  So, for dm6446, could VICP Signal Processing Library API functions be called when h.264 codec engine is running?

That depends on whether the version of H.264 you have uses VICP. Not all H.264 codec from TI makes use of VICP.

May be you can try calling CPIS_init() after H.264 is initialized and see whether it still works ?

Thanks again.

We are now using the “DM644x Codec Server” and “DM644x/647/648 VICP Library” downloading from http://www.go-dsp.com/forms/TIDigitalMediaSWCM/index.htm?DCMP=DSP_DigitalMediaSW&HQS=Other+OT+requestfreesoftware.

We find that calling CPIS_init() after H.264 is initialized will cause H.264 failed while VICP Signal Processing Library seems still work。

So, the “C64x+ H.264 BP Encode” and “C64x+ H.264 BP Decode” maybe work well with VICP Signal Processing Library, right?  Is there any other H.264 Codec would you prefer? Thanks!

And, is that true we can not share the VICP with H.264 codec even if the VICP load is low（for example, doing CIF encoding or D1 decoding only） when H.264 Codec do makes use of VICP?  Is there any way out?

Thank you very much!