| June 22, 2009 10:00 AM PDT | |
Some IPP APIs are deprecated since IPP 6.0. Please check the list below
1. All ippiResize*/ippiResizeCenter*/ippiResizeShift*/
and ippiGetResizeFract/ippiResizeSqrPixelGetBufSize functions
All ippiResize* functions in ippiman.pdf and .h formats have been marked for deprecated. Please use ippiResizeSqrPixel* intead.
For exmaple, you have the below code using ippiResize_8u_C3R
status=ippiResize_8u_C3R((Ipp8u*)pSrc->DataPtr(), pSrc->Size(), pSrc->Step(), roiRect, (Ipp8u*)pDst->DataPtr(), pDst->Step(), pDst->Size(), xFactor, yFactor, Interpolation);
Please use ippiResizeSqrPixel_8u_C3R function instead. The code is like,
IppiRect roiRect={0,0, pSrc->Width(),pSrc->Height()};
IppiRect dstRect={0,0, pDst->Width(),pDst->Height()};
status=ippiResizeGetBufSize(roiRect, dstRect, 3, Interpolation, &BufferSize);
Ipp8u* pBuffer=ippsMalloc_8u(BufferSize);
status=ippiResizeSqrPixel_8u_C3R((Ipp8u*)pSrc->DataPtr(), pSrc->Size(), pSrc->Step(), roiRect, (Ipp8u*)pDst->DataPtr(), pDst->Step(), dstRect, xFactor, yFactor, 0, 0, Interpolation, pBuffer);
We focus on the ippiResizeSqrPixel because it supports more interpolation methods and has close result as wide-used square-based interpolation.
The ippiResize* functions are obsolete. We kept them in current version just for back-compatible.
2. ippsSynthesisFilter_G729_16s/ippsShortTermPostFilter_G729A_16s
Please use ippsSynthesisFilter_NR_16s_Sfs as replacement
The function computes the speech signal by filtering the input speech through the synthesis filter. It performs the same operation as ippsSynthesisFilter_G729_16s/ippsShortTermPostFilter_G729A_16s for the same parameters, but explicit memory, scale factor and length.
For example the call
ippsShortTermPostFilter_G729A_16s(pSrcLpc, pSrcResidual, pSrcDstSpch)
and
ippsSynthesisFilter_G729_16s(pSrcResidual, pSrcLpc, pSrcDstSpch)
each is equvalentl to the call
ippsSynthesisFilter_NR_16s_Sfs(pSrcLpc, pSrcResidual, pSrcDstSpch, 40, 12, pSrcDstSpch-10).
3. ippsRijndael128EncryptCCM/ippsRijndael128EncryptCCM_u8; ippsRijndael128DecryptCCM/ippsRijndael128DecryptCCM_u8
Please Use ippsRijndael128CCMEncryptMessage/ippsRijndael128CCMDecryptMessage as replacement. Just for simple the interface.
Please see more details from User guide, ippiman.pdf, ippsman.pdf, ippcpman.pdf under doc directory, or online reference.
In future releases, we will also make more improvement to add warning messages during compilation time for awareness.
1. All ippiResize*/ippiResizeCenter*/ippiResizeShift*/
and ippiGetResizeFract/ippiResizeSqrPixelGetBufSize functions
All ippiResize* functions in ippiman.pdf and .h formats have been marked for deprecated. Please use ippiResizeSqrPixel* intead.
For exmaple, you have the below code using ippiResize_8u_C3R
status=ippiResize_8u_C3R((Ipp8u*)pSrc->DataPtr(), pSrc->Size(), pSrc->Step(), roiRect, (Ipp8u*)pDst->DataPtr(), pDst->Step(), pDst->Size(), xFactor, yFactor, Interpolation);
Please use ippiResizeSqrPixel_8u_C3R function instead. The code is like,
IppiRect roiRect={0,0, pSrc->Width(),pSrc->Height()};
IppiRect dstRect={0,0, pDst->Width(),pDst->Height()};
status=ippiResizeGetBufSize(roiRect, dstRect, 3, Interpolation, &BufferSize);
Ipp8u* pBuffer=ippsMalloc_8u(BufferSize);
status=ippiResizeSqrPixel_8u_C3R((Ipp8u*)pSrc->DataPtr(), pSrc->Size(), pSrc->Step(), roiRect, (Ipp8u*)pDst->DataPtr(), pDst->Step(), dstRect, xFactor, yFactor, 0, 0, Interpolation, pBuffer);
We focus on the ippiResizeSqrPixel because it supports more interpolation methods and has close result as wide-used square-based interpolation.
The ippiResize* functions are obsolete. We kept them in current version just for back-compatible.
2. ippsSynthesisFilter_G729_16s/ippsShortTermPostFilter_G729A_16s
Please use ippsSynthesisFilter_NR_16s_Sfs as replacement
The function computes the speech signal by filtering the input speech through the synthesis filter. It performs the same operation as ippsSynthesisFilter_G729_16s/ippsShortTermPostFilter_G729A_16s for the same parameters, but explicit memory, scale factor and length.
For example the call
ippsShortTermPostFilter_G729A_16s(pSrcLpc, pSrcResidual, pSrcDstSpch)
and
ippsSynthesisFilter_G729_16s(pSrcResidual, pSrcLpc, pSrcDstSpch)
each is equvalentl to the call
ippsSynthesisFilter_NR_16s_Sfs(pSrcLpc, pSrcResidual, pSrcDstSpch, 40, 12, pSrcDstSpch-10).
3. ippsRijndael128EncryptCCM/ippsRijndael128EncryptCCM_u8; ippsRijndael128DecryptCCM/ippsRijndael128DecryptCCM_u8
Please Use ippsRijndael128CCMEncryptMessage/ippsRijndael128CCMDecryptMessage as replacement. Just for simple the interface.
Please see more details from User guide, ippiman.pdf, ippsman.pdf, ippcpman.pdf under doc directory, or online reference.
In future releases, we will also make more improvement to add warning messages during compilation time for awareness.
Do you need more help?
This article applies to: Intel® Integrated Performance Primitives Knowledge Base
For more complete information about compiler optimizations, see our Optimization Notice.
Comments (4) 
| September 17, 2009 10:29 PM PDT
Ying Song (Intel)
|
Have you tried the latest version 6.1? If not , please go to http://software.intel.com/en-us/intel-ipp to get the latest update. If you still experience the problem, it is recommended to submit this issue into Intel IPP forum at http://software.intel.com/en-us/forums/intel-integrated-performan ce-primitives/ ? or Private Premier at https://premier.intel.com . In issue submission, please provide your image files with different sizes, target test platform with configuration, so we can take a look to see if we can reproduce the problem. Thanks, Ying |
| January 25, 2010 7:28 AM PST
mdl61
| We have noticed a similar problem and traced it to the internal threading mechanism. We have implemented our own threading external to ippResizeSqrPixel and this conflicts with the internal threading causing an increase of 40% CPU utilization, mostly in the kernel. We avoid this problem by calling ippSetNumThreads(1) before using ippResizeSqrPixel. |
| October 19, 2010 1:34 AM PDT
Ying H (Intel)
|
Regarding the cpu usage issue, some discussion in http://software.intel.com/en-us/articles/high-cpu-usage-and-..... -function/ may helpful |
Trackbacks (0)
Leave a comment 
To obtain technical support, please go to Software Support.


I2R D&T Team
175
I have noticed that when calling the function ippResize or ippResizeCenter recursively and sequentially with small delay (< 100 ms) in between, uses less CPU usage as compared to ippResizeSqrPixel. The comparison is based on resizing 1280x1024 image to 877x602 image. I have tried using the single algorithm or parallel algorithm introduced in the documentation but it still uses alot of CPU usage in both algorithms. I cannot figure out what's wrong with ippResizeSqrPixel function.
Does anyone faced the same problem?