Revision history [back]

Ok, I checked the source code of opencv and found the issue. In warpperspective the function cv::remap gets called. link text

 if( interpolation == INTER_LINEAR )
        ifunc = linear_tab[depth];

the linear_tab[depth] will return 0 ( depth for cv_32s is 4). So obviously the assert( ifunc != 0) will fail. So in my eyes this means that integer as a source mat is simply not supported/supposed to work.

Ok, I checked the source code of opencv and found the issue. In warpperspective the function cv::remap gets called. link text

 if( interpolation == INTER_LINEAR )
        ifunc = linear_tab[depth];

the linear_tab[depth] will return 0 ( depth for cv_32s is 4). So obviously the assert( ifunc != 0) will fail. So in my eyes this means that integer as a source mat is simply not supported/supposed to work.work which is also kind of obvious. I mean, linear interpolation on integers does not make too much sense.

Ok, I checked the source code of opencv and found the issue. In warpperspective the function cv::remap gets called. link text

 if( interpolation == INTER_LINEAR )
        ifunc = linear_tab[depth];

the linear_tab[depth] will return 0 ( depth for cv_32s is 4). So obviously the assert( ifunc != 0) will fail. So in my eyes this means that integer as a source mat is simply not supported/supposed to work which is also kind of obvious. I mean, linear interpolation on integers does not make too much sense.supported/supposed.

Ok, I checked the source code of opencv and found the issue. In warpperspective the function cv::remap gets called. link text

 if( interpolation == INTER_LINEAR )
        ifunc = linear_tab[depth];

the linear_tab[depth] will return 0 ( depth for cv_32s is 4). So obviously the assert( ifunc != 0) will fail. So in my eyes this means that integer as a source mat is simply not supported/supposed.supported/supposed to work.