GOOD uses the BOX.BOX filter, with a filter size of 1 for all scales larger
than .75, which is identical to BILINEAR. At very small scales it clamps the
filter size to 16. Uses the BILINEAR code if both directions are bilinear
or are exactly .5 scale with integer translations.
BEST uses the IMPULS
Oops, these debugging printfs should be removed before use:
On 09/26/2014 07:06 PM, Bill Spitzak wrote:
+ if (bilinear_ok) {
+ printf("Using bilinear\n");
+ flags |= (FAST_PATH_BILINEAR_FILTER |
+ FAST_PATH_NO_CONVOLUTION_FILTER);
+
GOOD uses the BOX.BOX filter, with a filter size of 1 for all scales larger
than .75, which is identical to BILINEAR. At very small scales it clamps the
filter size to 16. Uses the BILINEAR code if both directions are bilinear
or are exactly .5 scale with integer translations.
BEST uses the IMPULS
GOOD uses the BOX.BOX filter, with a filter size of 1 for all scales larger
than .75, which is identical to BILINEAR. At very small scales it clamps the
filter size to 16.
BEST uses the IMPULSE.LANCZOS2 filter up to a scale of 2 with the filter size
clamped to 1. At higher scales it switches to BO
GOOD uses the BOX filter, and uses BILINEAR for all scales > 1/1.35.
BEST uses the LANCZOS2 filter. The size is chosen to produce normal
filtering up to a scale of 2, and square pixels with only slight
blurry borders beyond that. I think it looks really nice.
Uses NEAREST instead of BILINEAR, GOO
