The following page for the documentation of the latest version of Intel IPP provides you with all the resize functions with prior initialization. You can check the documentation to see all the differences. You have a huge number of resize functions.
The documentation is really scarce. You can call ResizeFilterInit with option ippResizeFilterLanczos, which sounds really similar to calling ResizeLanczos. I'm a signal processing noob, so maybe the distinction is obvious to people of other backgrounds.
I've been a user for Intel Performance Primitives for a long time. I never had problems with the documentation. However, the documentation provides information about calling the different functions and doesn't explain the goal for each filter. This is domain specific. So, you won't become a signal processing expert by reading the documentation. You require other sources to become a signal processing expert, combined with the documentation on how to call the functions. You need to understand what you want to do and the documentation will allow you to use the appropriate function to achieve your goals.
The ResizeFilterInit function allows you to specify the desired filter to use. There are many ways to achieve the same result.
You can check additional documentation to understand the difference between the filters and they effect and when it is convenient to use each of them.
The following link might be helpful. It provides some details about ROI Processing in Geometric Transforms.
Just make sure you check other sources to have a better understanding of what you can do with these functions.
The main idea of ResizeFilter with Lanczos interpolation is the same as for ResizeLanczos. But ResizeFilter computes pixel values using fixed-point arithmetic, so it has lower accuracy than ResizeLanczos that uses floating point arithmetic to interpolate pixels.
> But ResizeFilter computes pixel values using fixed-point arithmetic, so it has lower accuracy than ResizeLanczos that uses floating point arithmetic to interpolate pixels.
It looks like ResizeFilter is available for 8u_C1R only, so ResizeFilter is of very limited use. You want to say that this function uses fixed-point arithmetic for 8u ? What is the size of this fixed-point arithmetic ? And how can this lead to "lower accuracy" for 8u ?
ResizeLanczos uses floating-point arithmetic for 8u, 16u, 16s, 32f and 64f ? What size of floating-point arithmetic ? And where is this documented (as the original question was related to (lack of) documentation) ?
And what type and size of arithmetic is used by ResizeLinear, ResizeCubic and ResizeSuper ?
Adriaan van Os
> The type of arithmetic for internal computations is always compromise between accuracy and performance.
That is like saying like that 2 is always greater than 1. Which is interesting but not informative. Nor addressing my question.
Adriaan van Os