JDCT_FASTEST is supposed to be configured during build of libjpeg and
will be set to the fastest DCT/IDCT algorithm for a given platform.
JDCT_IFAST on the other hand just selects a (fast, less accurate) integer
algorithm, which for a given platform might not be faster than any
of the other JDCT_ algorithms.
---
.../idirectfbimageprovider_jpeg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/interfaces/IDirectFBImageProvider/idirectfbimageprovider_jpeg.c
b/interfaces/IDirectFBImageProvider/idirectfbimageprovider_jpeg.c
index a7430f7..d1e9aa7 100644
--- a/interfaces/IDirectFBImageProvider/idirectfbimageprovider_jpeg.c
+++ b/interfaces/IDirectFBImageProvider/idirectfbimageprovider_jpeg.c
@@ -578,7 +578,7 @@ IDirectFBImageProvider_JPEG_RenderTo(
IDirectFBImageProvider *thiz,
}
if (data->flags & DIRENDER_FAST)
- cinfo.dct_method = JDCT_IFAST;
+ cinfo.dct_method = JDCT_FASTEST;
jpeg_start_decompress( &cinfo );
--
1.7.9.5
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
