[Lunar-commits] r16790 - moonbase/trunk/graphics

Dennis Veatch stumbles at lunar-linux.org
Tue Oct 4 13:13:03 UTC 2005

Author: stumbles
Date: 2005-10-04 13:12:54 +0000 (Tue, 04 Oct 2005)
New Revision: 16790


If you got bad pixels on your CCD, this might help

Compiled with gcc-3.4.4 and glibc-2.3.5

Copied: moonbase/trunk/graphics/jpegpixi (from rev 16757, moonbase/branches/submissions/new/kover/DETAILS)
--- moonbase/branches/submissions/new/kover/DETAILS	2005-10-01 19:54:08 UTC (rev 16757)
+++ moonbase/trunk/graphics/jpegpixi	2005-10-04 13:12:54 UTC (rev 16790)
@@ -0,0 +1,24 @@
+          MODULE=jpegpixi
+         VERSION=1.1.0
+          SOURCE=$MODULE-$VERSION.tar.gz
+   SOURCE_URL[0]=http://www.zero-based.org/software/$MODULE/
+      SOURCE_VFY=sha1:c8b41629228892ab4913914f75bffc0fe92e0839
+        WEB_SITE=http://www.zero-based.org/software/jpegpixi/
+         ENTERED=20051004
+         UPDATED=20051004
+           SHORT="correct images from a digital camera with CCD defects"
+cat << EOF
+Correct images from a digital camera with CCD defects.
+Jpegpixi is unique in that it tries to preserve the quality of the JPEG image
+as much as possible. Usual graphics programs decode JPEG images when they are
+loaded, and re-encode them when they are saved, which results in an overall
+loss of quality. Jpegpixi, on the other hand, only decodes the DCT blocks
+(typically 8×8, 16×8, or 16×16 pixel areas) which contain pixels to be
+interpolated, and when it re-encodes them, it uses exactly the same parameters
+with which the image has originally been encoded. These blocks are therefore
+only minimally disturbed, and other blocks remain pixel-by-pixel identical to
+the original image.

More information about the Lunar-commits mailing list