Home | History | Annotate | only in /external/libjpeg-turbo
Up to higher level directory
NameDateSize
acinclude.m421-Aug-20186.7K
Android.bp21-Aug-20185.9K
appveyor.yml21-Aug-20181.8K
bmp.c21-Aug-20189.7K
bmp.h21-Aug-20181.8K
BUILDING.md21-Aug-201834.3K
cderror.h21-Aug-20185.3K
cdjpeg.c21-Aug-20183.9K
cdjpeg.h21-Aug-20185.5K
change.log21-Aug-201812.1K
ChangeLog.md21-Aug-201855.1K
ci/21-Aug-2018
cjpeg.121-Aug-201813.2K
cjpeg.c21-Aug-201821.3K
CMakeLists.txt21-Aug-201837.2K
cmakescripts/21-Aug-2018
coderules.txt21-Aug-20183.4K
configure.ac21-Aug-201819.4K
djpeg.121-Aug-20189.6K
djpeg.c21-Aug-201825.8K
doc/21-Aug-2018
doxygen-extra.css21-Aug-201826
doxygen.config21-Aug-2018401
example.c21-Aug-201816.8K
jaricom.c21-Aug-20185K
java/21-Aug-2018
jcapimin.c21-Aug-20189.5K
jcapistd.c21-Aug-20185.8K
jcarith.c21-Aug-201828.9K
jccoefct.c21-Aug-201816.8K
jccolext.c21-Aug-20184.5K
jccolor.c21-Aug-201823.4K
jcdctmgr.c21-Aug-201822K
jchuff.c21-Aug-201833.6K
jchuff.h21-Aug-20181.4K
jcinit.c21-Aug-20182.4K
jcmainct.c21-Aug-20185K
jcmarker.c21-Aug-201817.2K
jcmaster.c21-Aug-201821.4K
jcomapi.c21-Aug-20183.2K
jconfig.h21-Aug-20182.2K
jconfig.h.in21-Aug-20182.1K
jconfig.txt21-Aug-20184.8K
jconfigint.h21-Aug-20181K
jconfigint.h.in21-Aug-2018336
jcparam.c21-Aug-201817.7K
jcphuff.c21-Aug-201825.3K
jcprepct.c21-Aug-201812.9K
jcsample.c21-Aug-201819.8K
jcstest.c21-Aug-20183.8K
jctrans.c21-Aug-201814.6K
jdapimin.c21-Aug-201812.9K
jdapistd.c21-Aug-201823.2K
jdarith.c21-Aug-201824.4K
jdatadst-tj.c21-Aug-20186.6K
jdatadst.c21-Aug-20189.5K
jdatasrc-tj.c21-Aug-20186.7K
jdatasrc.c21-Aug-201810.1K
jdcoefct.c21-Aug-201824.7K
jdcoefct.h21-Aug-20182.6K
jdcol565.c21-Aug-201812K
jdcolext.c21-Aug-20184.4K
jdcolor.c21-Aug-201828.5K
jdct.h21-Aug-20188.8K
jddctmgr.c21-Aug-201811.2K
jdhuff.c21-Aug-201825.4K
jdhuff.h21-Aug-20189.2K
jdinput.c21-Aug-201814.2K
jdmainct.c21-Aug-201818.9K
jdmainct.h21-Aug-20182.4K
jdmarker.c21-Aug-201841.9K
jdmaster.c21-Aug-201827.3K
jdmaster.h21-Aug-2018788
jdmerge.c21-Aug-201820.9K
jdmrg565.c21-Aug-201811.2K
jdmrgext.c21-Aug-20185.9K
jdphuff.c21-Aug-201821.4K
jdpostct.c21-Aug-201810.1K
jdsample.c21-Aug-201817.7K
jdsample.h21-Aug-20181.7K
jdtrans.c21-Aug-20185.3K
jerror.c21-Aug-20187.7K
jerror.h21-Aug-201814.7K
jfdctflt.c21-Aug-20185.4K
jfdctfst.c21-Aug-20187.6K
jfdctint.c21-Aug-201811.2K
jidctflt.c21-Aug-20188.5K
jidctfst.c21-Aug-201813.4K
jidctint.c21-Aug-2018102.7K
jidctred.c21-Aug-201813.9K
jinclude.h21-Aug-20182.9K
jmemmgr.c21-Aug-201843.8K
jmemnobs.c21-Aug-20182.8K
jmemsys.h21-Aug-20187.6K
jmorecfg.h21-Aug-201814.7K
jpeg_nbits_table.h21-Aug-2018264.1K
jpegcomp.h21-Aug-20181K
jpegint.h21-Aug-201815.2K
jpeglib.h21-Aug-201848.7K
jpegtran.121-Aug-20189.4K
jpegtran.c21-Aug-201818.3K
jquant1.c21-Aug-201831.7K
jquant2.c21-Aug-201847.7K
jsimd.h21-Aug-20183.6K
jsimd_none.c21-Aug-20187.4K
jsimddct.h21-Aug-20183.2K
jstdhuff.c21-Aug-20185.2K
jutils.c21-Aug-20183.7K
jversion.h21-Aug-20181.8K
libjpeg.map.in21-Aug-2018164
libjpeg.txt21-Aug-2018163.9K
LICENSE.md21-Aug-20185.2K
Makefile.am21-Aug-201833.5K
md5/21-Aug-2018
MODULE_LICENSE_BSD21-Aug-20180
NOTICE21-Aug-20182.9K
OWNERS21-Aug-201819
rdbmp.c21-Aug-201815.1K
rdcolmap.c21-Aug-20186.9K
rdgif.c21-Aug-20181.3K
rdjpgcom.121-Aug-20181.7K
rdjpgcom.c21-Aug-201814.7K
rdppm.c21-Aug-201814.3K
rdrle.c21-Aug-201811.5K
rdswitch.c21-Aug-201812.7K
rdtarga.c21-Aug-201815K
README21-Aug-201813.5K
README-turbo.txt21-Aug-201816.4K
README.android21-Aug-20181.2K
README.ijg21-Aug-201813.3K
README.md21-Aug-201815.8K
README.version21-Aug-2018151
release/21-Aug-2018
sharedlib/21-Aug-2018
simd/21-Aug-2018
structure.txt21-Aug-201848.6K
testimages/21-Aug-2018
tjbench.c21-Aug-201831.1K
tjbenchtest.in21-Aug-201811.4K
tjbenchtest.java.in21-Aug-20189.6K
tjexampletest.in21-Aug-20188K
tjunittest.c21-Aug-201818.6K
tjutil.c21-Aug-20182.1K
tjutil.h21-Aug-20181.9K
transupp.c21-Aug-201861K
transupp.h21-Aug-20189.4K
turbojpeg-jni.c21-Aug-201841.6K
turbojpeg-mapfile21-Aug-2018794
turbojpeg-mapfile.jni21-Aug-20182.9K
turbojpeg.c21-Aug-201861.9K
turbojpeg.h21-Aug-201863.6K
usage.txt21-Aug-201834.2K
win/21-Aug-2018
wizard.txt21-Aug-201810.1K
wrbmp.c21-Aug-201815.3K
wrgif.c21-Aug-201813.2K
wrjpgcom.121-Aug-20182.6K
wrjpgcom.c21-Aug-201817.5K
wrppm.c21-Aug-20188.3K
wrppm.h21-Aug-2018721
wrrle.c21-Aug-20189.2K
wrtarga.c21-Aug-20187.5K

README

      1 libjpeg-turbo note:  This file has been modified by The libjpeg-turbo Project
      2 to include only information relevant to libjpeg-turbo, to wordsmith certain
      3 sections, and to remove impolitic language that existed in the libjpeg v8
      4 README.  It is included only for reference.  Please see README-turbo.txt for
      5 information specific to libjpeg-turbo.
      6 
      7 
      8 The Independent JPEG Group's JPEG software
      9 ==========================================
     10 
     11 This distribution contains a release of the Independent JPEG Group's free JPEG
     12 software.  You are welcome to redistribute this software and to use it for any
     13 purpose, subject to the conditions under LEGAL ISSUES, below.
     14 
     15 This software is the work of Tom Lane, Guido Vollbeding, Philip Gladstone,
     16 Bill Allombert, Jim Boucher, Lee Crocker, Bob Friesenhahn, Ben Jackson,
     17 Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi, Ge' Weijers,
     18 and other members of the Independent JPEG Group.
     19 
     20 IJG is not affiliated with the ISO/IEC JTC1/SC29/WG1 standards committee
     21 (also known as JPEG, together with ITU-T SG16).
     22 
     23 
     24 DOCUMENTATION ROADMAP
     25 =====================
     26 
     27 This file contains the following sections:
     28 
     29 OVERVIEW            General description of JPEG and the IJG software.
     30 LEGAL ISSUES        Copyright, lack of warranty, terms of distribution.
     31 REFERENCES          Where to learn more about JPEG.
     32 ARCHIVE LOCATIONS   Where to find newer versions of this software.
     33 FILE FORMAT WARS    Software *not* to get.
     34 TO DO               Plans for future IJG releases.
     35 
     36 Other documentation files in the distribution are:
     37 
     38 User documentation:
     39   usage.txt         Usage instructions for cjpeg, djpeg, jpegtran,
     40                     rdjpgcom, and wrjpgcom.
     41   *.1               Unix-style man pages for programs (same info as usage.txt).
     42   wizard.txt        Advanced usage instructions for JPEG wizards only.
     43   change.log        Version-to-version change highlights.
     44 Programmer and internal documentation:
     45   libjpeg.txt       How to use the JPEG library in your own programs.
     46   example.c         Sample code for calling the JPEG library.
     47   structure.txt     Overview of the JPEG library's internal structure.
     48   coderules.txt     Coding style rules --- please read if you contribute code.
     49 
     50 Please read at least usage.txt.  Some information can also be found in the JPEG
     51 FAQ (Frequently Asked Questions) article.  See ARCHIVE LOCATIONS below to find
     52 out where to obtain the FAQ article.
     53 
     54 If you want to understand how the JPEG code works, we suggest reading one or
     55 more of the REFERENCES, then looking at the documentation files (in roughly
     56 the order listed) before diving into the code.
     57 
     58 
     59 OVERVIEW
     60 ========
     61 
     62 This package contains C software to implement JPEG image encoding, decoding,
     63 and transcoding.  JPEG (pronounced "jay-peg") is a standardized compression
     64 method for full-color and grayscale images.  JPEG's strong suit is compressing
     65 photographic images or other types of images that have smooth color and
     66 brightness transitions between neighboring pixels.  Images with sharp lines or
     67 other abrupt features may not compress well with JPEG, and a higher JPEG
     68 quality may have to be used to avoid visible compression artifacts with such
     69 images.
     70 
     71 JPEG is lossy, meaning that the output pixels are not necessarily identical to
     72 the input pixels.  However, on photographic content and other "smooth" images,
     73 very good compression ratios can be obtained with no visible compression
     74 artifacts, and extremely high compression ratios are possible if you are
     75 willing to sacrifice image quality (by reducing the "quality" setting in the
     76 compressor.)
     77 
     78 This software implements JPEG baseline, extended-sequential, and progressive
     79 compression processes.  Provision is made for supporting all variants of these
     80 processes, although some uncommon parameter settings aren't implemented yet.
     81 We have made no provision for supporting the hierarchical or lossless
     82 processes defined in the standard.
     83 
     84 We provide a set of library routines for reading and writing JPEG image files,
     85 plus two sample applications "cjpeg" and "djpeg", which use the library to
     86 perform conversion between JPEG and some other popular image file formats.
     87 The library is intended to be reused in other applications.
     88 
     89 In order to support file conversion and viewing software, we have included
     90 considerable functionality beyond the bare JPEG coding/decoding capability;
     91 for example, the color quantization modules are not strictly part of JPEG
     92 decoding, but they are essential for output to colormapped file formats or
     93 colormapped displays.  These extra functions can be compiled out of the
     94 library if not required for a particular application.
     95 
     96 We have also included "jpegtran", a utility for lossless transcoding between
     97 different JPEG processes, and "rdjpgcom" and "wrjpgcom", two simple
     98 applications for inserting and extracting textual comments in JFIF files.
     99 
    100 The emphasis in designing this software has been on achieving portability and
    101 flexibility, while also making it fast enough to be useful.  In particular,
    102 the software is not intended to be read as a tutorial on JPEG.  (See the
    103 REFERENCES section for introductory material.)  Rather, it is intended to
    104 be reliable, portable, industrial-strength code.  We do not claim to have
    105 achieved that goal in every aspect of the software, but we strive for it.
    106 
    107 We welcome the use of this software as a component of commercial products.
    108 No royalty is required, but we do ask for an acknowledgement in product
    109 documentation, as described under LEGAL ISSUES.
    110 
    111 
    112 LEGAL ISSUES
    113 ============
    114 
    115 In plain English:
    116 
    117 1. We don't promise that this software works.  (But if you find any bugs,
    118    please let us know!)
    119 2. You can use this software for whatever you want.  You don't have to pay us.
    120 3. You may not pretend that you wrote this software.  If you use it in a
    121    program, you must acknowledge somewhere in your documentation that
    122    you've used the IJG code.
    123 
    124 In legalese:
    125 
    126 The authors make NO WARRANTY or representation, either express or implied,
    127 with respect to this software, its quality, accuracy, merchantability, or
    128 fitness for a particular purpose.  This software is provided "AS IS", and you,
    129 its user, assume the entire risk as to its quality and accuracy.
    130 
    131 This software is copyright (C) 1991-2012, Thomas G. Lane, Guido Vollbeding.
    132 All Rights Reserved except as specified below.
    133 
    134 Permission is hereby granted to use, copy, modify, and distribute this
    135 software (or portions thereof) for any purpose, without fee, subject to these
    136 conditions:
    137 (1) If any part of the source code for this software is distributed, then this
    138 README file must be included, with this copyright and no-warranty notice
    139 unaltered; and any additions, deletions, or changes to the original files
    140 must be clearly indicated in accompanying documentation.
    141 (2) If only executable code is distributed, then the accompanying
    142 documentation must state that "this software is based in part on the work of
    143 the Independent JPEG Group".
    144 (3) Permission for use of this software is granted only if the user accepts
    145 full responsibility for any undesirable consequences; the authors accept
    146 NO LIABILITY for damages of any kind.
    147 
    148 These conditions apply to any software derived from or based on the IJG code,
    149 not just to the unmodified library.  If you use our work, you ought to
    150 acknowledge us.
    151 
    152 Permission is NOT granted for the use of any IJG author's name or company name
    153 in advertising or publicity relating to this software or products derived from
    154 it.  This software may be referred to only as "the Independent JPEG Group's
    155 software".
    156 
    157 We specifically permit and encourage the use of this software as the basis of
    158 commercial products, provided that all warranty or liability claims are
    159 assumed by the product vendor.
    160 
    161 
    162 The Unix configuration script "configure" was produced with GNU Autoconf.
    163 It is copyright by the Free Software Foundation but is freely distributable.
    164 The same holds for its supporting scripts (config.guess, config.sub,
    165 ltmain.sh).  Another support script, install-sh, is copyright by X Consortium
    166 but is also freely distributable.
    167 
    168 The IJG distribution formerly included code to read and write GIF files.
    169 To avoid entanglement with the Unisys LZW patent, GIF reading support has
    170 been removed altogether, and the GIF writer has been simplified to produce
    171 "uncompressed GIFs".  This technique does not use the LZW algorithm; the
    172 resulting GIF files are larger than usual, but are readable by all standard
    173 GIF decoders.
    174 
    175 We are required to state that
    176     "The Graphics Interchange Format(c) is the Copyright property of
    177     CompuServe Incorporated.  GIF(sm) is a Service Mark property of
    178     CompuServe Incorporated."
    179 
    180 
    181 REFERENCES
    182 ==========
    183 
    184 We recommend reading one or more of these references before trying to
    185 understand the innards of the JPEG software.
    186 
    187 The best short technical introduction to the JPEG compression algorithm is
    188 	Wallace, Gregory K.  "The JPEG Still Picture Compression Standard",
    189 	Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44.
    190 (Adjacent articles in that issue discuss MPEG motion picture compression,
    191 applications of JPEG, and related topics.)  If you don't have the CACM issue
    192 handy, a PostScript file containing a revised version of Wallace's article is
    193 available at http://www.ijg.org/files/wallace.ps.gz.  The file (actually
    194 a preprint for an article that appeared in IEEE Trans. Consumer Electronics)
    195 omits the sample images that appeared in CACM, but it includes corrections
    196 and some added material.  Note: the Wallace article is copyright ACM and IEEE,
    197 and it may not be used for commercial purposes.
    198 
    199 A somewhat less technical, more leisurely introduction to JPEG can be found in
    200 "The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published by
    201 M&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1.  This book provides
    202 good explanations and example C code for a multitude of compression methods
    203 including JPEG.  It is an excellent source if you are comfortable reading C
    204 code but don't know much about data compression in general.  The book's JPEG
    205 sample code is far from industrial-strength, but when you are ready to look
    206 at a full implementation, you've got one here...
    207 
    208 The best currently available description of JPEG is the textbook "JPEG Still
    209 Image Data Compression Standard" by William B. Pennebaker and Joan L.
    210 Mitchell, published by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1.
    211 Price US$59.95, 638 pp.  The book includes the complete text of the ISO JPEG
    212 standards (DIS 10918-1 and draft DIS 10918-2).
    213 
    214 The original JPEG standard is divided into two parts, Part 1 being the actual
    215 specification, while Part 2 covers compliance testing methods.  Part 1 is
    216 titled "Digital Compression and Coding of Continuous-tone Still Images,
    217 Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS
    218 10918-1, ITU-T T.81.  Part 2 is titled "Digital Compression and Coding of
    219 Continuous-tone Still Images, Part 2: Compliance testing" and has document
    220 numbers ISO/IEC IS 10918-2, ITU-T T.83.
    221 
    222 The JPEG standard does not specify all details of an interchangeable file
    223 format.  For the omitted details we follow the "JFIF" conventions, revision
    224 1.02.  JFIF 1.02 has been adopted as an Ecma International Technical Report
    225 and thus received a formal publication status.  It is available as a free
    226 download in PDF format from
    227 http://www.ecma-international.org/publications/techreports/E-TR-098.htm.
    228 A PostScript version of the JFIF document is available at
    229 http://www.ijg.org/files/jfif.ps.gz.  There is also a plain text version at
    230 http://www.ijg.org/files/jfif.txt.gz, but it is missing the figures.
    231 
    232 The TIFF 6.0 file format specification can be obtained by FTP from
    233 ftp://ftp.sgi.com/graphics/tiff/TIFF6.ps.gz.  The JPEG incorporation scheme
    234 found in the TIFF 6.0 spec of 3-June-92 has a number of serious problems.
    235 IJG does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6).
    236 Instead, we recommend the JPEG design proposed by TIFF Technical Note #2
    237 (Compression tag 7).  Copies of this Note can be obtained from
    238 http://www.ijg.org/files/.  It is expected that the next revision
    239 of the TIFF spec will replace the 6.0 JPEG design with the Note's design.
    240 Although IJG's own code does not support TIFF/JPEG, the free libtiff library
    241 uses our library to implement TIFF/JPEG per the Note.
    242 
    243 
    244 ARCHIVE LOCATIONS
    245 =================
    246 
    247 The "official" archive site for this software is www.ijg.org.
    248 The most recent released version can always be found there in
    249 directory "files".  This particular version will be archived as
    250 http://www.ijg.org/files/jpegsrc.v8d.tar.gz, and in Windows-compatible
    251 "zip" archive format as http://www.ijg.org/files/jpegsr8d.zip.
    252 
    253 The JPEG FAQ (Frequently Asked Questions) article is a source of some
    254 general information about JPEG.
    255 It is available on the World Wide Web at http://www.faqs.org/faqs/jpeg-faq/
    256 and other news.answers archive sites, including the official news.answers
    257 archive at rtfm.mit.edu: ftp://rtfm.mit.edu/pub/usenet/news.answers/jpeg-faq/.
    258 If you don't have Web or FTP access, send e-mail to mail-server (a] rtfm.mit.edu
    259 with body
    260 	send usenet/news.answers/jpeg-faq/part1
    261 	send usenet/news.answers/jpeg-faq/part2
    262 
    263 
    264 FILE FORMAT WARS
    265 ================
    266 
    267 The ISO/IEC JTC1/SC29/WG1 standards committee (also known as JPEG, together
    268 with ITU-T SG16) currently promotes different formats containing the name
    269 "JPEG" which are incompatible with original DCT-based JPEG.  IJG therefore does
    270 not support these formats (see REFERENCES).  Indeed, one of the original
    271 reasons for developing this free software was to help force convergence on
    272 common, interoperable format standards for JPEG files.
    273 Don't use an incompatible file format!
    274 (In any case, our decoder will remain capable of reading existing JPEG
    275 image files indefinitely.)
    276 
    277 
    278 TO DO
    279 =====
    280 
    281 Please send bug reports, offers of help, etc. to jpeg-info (a] jpegclub.org.
    282 

README-turbo.txt

      1 *******************************************************************************
      2 **     Background
      3 *******************************************************************************
      4 
      5 libjpeg-turbo is a JPEG image codec that uses SIMD instructions (MMX, SSE2,
      6 NEON) to accelerate baseline JPEG compression and decompression on x86, x86-64,
      7 and ARM systems.  On such systems, libjpeg-turbo is generally 2-4x as fast as
      8 libjpeg, all else being equal.  On other types of systems, libjpeg-turbo can
      9 still outperform libjpeg by a significant amount, by virtue of its
     10 highly-optimized Huffman coding routines.  In many cases, the performance of
     11 libjpeg-turbo rivals that of proprietary high-speed JPEG codecs.
     12 
     13 libjpeg-turbo implements both the traditional libjpeg API as well as the less
     14 powerful but more straightforward TurboJPEG API.  libjpeg-turbo also features
     15 colorspace extensions that allow it to compress from/decompress to 32-bit and
     16 big-endian pixel buffers (RGBX, XBGR, etc.), as well as a full-featured Java
     17 interface.
     18 
     19 libjpeg-turbo was originally based on libjpeg/SIMD, an MMX-accelerated
     20 derivative of libjpeg v6b developed by Miyasaka Masaru.  The TigerVNC and
     21 VirtualGL projects made numerous enhancements to the codec in 2009, and in
     22 early 2010, libjpeg-turbo spun off into an independent project, with the goal
     23 of making high-speed JPEG compression/decompression technology available to a
     24 broader range of users and developers.
     25 
     26 
     27 *******************************************************************************
     28 **     License
     29 *******************************************************************************
     30 
     31 libjpeg-turbo is covered by three compatible BSD-style open source licenses.
     32 Refer to LICENSE.txt for a roll-up of license terms.
     33 
     34 
     35 *******************************************************************************
     36 **     Using libjpeg-turbo
     37 *******************************************************************************
     38 
     39 libjpeg-turbo includes two APIs that can be used to compress and decompress
     40 JPEG images:
     41 
     42   TurboJPEG API:  This API provides an easy-to-use interface for compressing
     43   and decompressing JPEG images in memory.  It also provides some functionality
     44   that would not be straightforward to achieve using the underlying libjpeg
     45   API, such as generating planar YUV images and performing multiple
     46   simultaneous lossless transforms on an image.  The Java interface for
     47   libjpeg-turbo is written on top of the TurboJPEG API.
     48 
     49   libjpeg API:  This is the de facto industry-standard API for compressing and
     50   decompressing JPEG images.  It is more difficult to use than the TurboJPEG
     51   API but also more powerful.  The libjpeg API implementation in libjpeg-turbo
     52   is both API/ABI-compatible and mathematically compatible with libjpeg v6b.
     53   It can also optionally be configured to be API/ABI-compatible with libjpeg v7
     54   and v8 (see below.)
     55 
     56 There is no significant performance advantage to either API when both are used
     57 to perform similar operations.
     58 
     59 =====================
     60 Colorspace Extensions
     61 =====================
     62 
     63 libjpeg-turbo includes extensions that allow JPEG images to be compressed
     64 directly from (and decompressed directly to) buffers that use BGR, BGRX,
     65 RGBX, XBGR, and XRGB pixel ordering.  This is implemented with ten new
     66 colorspace constants:
     67 
     68   JCS_EXT_RGB   /* red/green/blue */
     69   JCS_EXT_RGBX  /* red/green/blue/x */
     70   JCS_EXT_BGR   /* blue/green/red */
     71   JCS_EXT_BGRX  /* blue/green/red/x */
     72   JCS_EXT_XBGR  /* x/blue/green/red */
     73   JCS_EXT_XRGB  /* x/red/green/blue */
     74   JCS_EXT_RGBA  /* red/green/blue/alpha */
     75   JCS_EXT_BGRA  /* blue/green/red/alpha */
     76   JCS_EXT_ABGR  /* alpha/blue/green/red */
     77   JCS_EXT_ARGB  /* alpha/red/green/blue */
     78 
     79 Setting cinfo.in_color_space (compression) or cinfo.out_color_space
     80 (decompression) to one of these values will cause libjpeg-turbo to read the
     81 red, green, and blue values from (or write them to) the appropriate position in
     82 the pixel when compressing from/decompressing to an RGB buffer.
     83 
     84 Your application can check for the existence of these extensions at compile
     85 time with:
     86 
     87   #ifdef JCS_EXTENSIONS
     88 
     89 At run time, attempting to use these extensions with a libjpeg implementation
     90 that does not support them will result in a "Bogus input colorspace" error.
     91 Applications can trap this error in order to test whether run-time support is
     92 available for the colorspace extensions.
     93 
     94 When using the RGBX, BGRX, XBGR, and XRGB colorspaces during decompression, the
     95 X byte is undefined, and in order to ensure the best performance, libjpeg-turbo
     96 can set that byte to whatever value it wishes.  If an application expects the X
     97 byte to be used as an alpha channel, then it should specify JCS_EXT_RGBA,
     98 JCS_EXT_BGRA, JCS_EXT_ABGR, or JCS_EXT_ARGB.  When these colorspace constants
     99 are used, the X byte is guaranteed to be 0xFF, which is interpreted as opaque.
    100 
    101 Your application can check for the existence of the alpha channel colorspace
    102 extensions at compile time with:
    103 
    104   #ifdef JCS_ALPHA_EXTENSIONS
    105 
    106 jcstest.c, located in the libjpeg-turbo source tree, demonstrates how to check
    107 for the existence of the colorspace extensions at compile time and run time.
    108 
    109 ===================================
    110 libjpeg v7 and v8 API/ABI Emulation
    111 ===================================
    112 
    113 With libjpeg v7 and v8, new features were added that necessitated extending the
    114 compression and decompression structures.  Unfortunately, due to the exposed
    115 nature of those structures, extending them also necessitated breaking backward
    116 ABI compatibility with previous libjpeg releases.  Thus, programs that were
    117 built to use libjpeg v7 or v8 did not work with libjpeg-turbo, since it is
    118 based on the libjpeg v6b code base.  Although libjpeg v7 and v8 are not
    119 as widely used as v6b, enough programs (including a few Linux distros) made
    120 the switch that there was a demand to emulate the libjpeg v7 and v8 ABIs
    121 in libjpeg-turbo.  It should be noted, however, that this feature was added
    122 primarily so that applications that had already been compiled to use libjpeg
    123 v7+ could take advantage of accelerated baseline JPEG encoding/decoding
    124 without recompiling.  libjpeg-turbo does not claim to support all of the
    125 libjpeg v7+ features, nor to produce identical output to libjpeg v7+ in all
    126 cases (see below.)
    127 
    128 By passing an argument of --with-jpeg7 or --with-jpeg8 to configure, or an
    129 argument of -DWITH_JPEG7=1 or -DWITH_JPEG8=1 to cmake, you can build a version
    130 of libjpeg-turbo that emulates the libjpeg v7 or v8 ABI, so that programs
    131 that are built against libjpeg v7 or v8 can be run with libjpeg-turbo.  The
    132 following section describes which libjpeg v7+ features are supported and which
    133 aren't.
    134 
    135 Support for libjpeg v7 and v8 Features:
    136 ---------------------------------------
    137 
    138 Fully supported:
    139 
    140 -- libjpeg: IDCT scaling extensions in decompressor
    141    libjpeg-turbo supports IDCT scaling with scaling factors of 1/8, 1/4, 3/8,
    142    1/2, 5/8, 3/4, 7/8, 9/8, 5/4, 11/8, 3/2, 13/8, 7/4, 15/8, and 2/1 (only 1/4
    143    and 1/2 are SIMD-accelerated.)
    144 
    145 -- libjpeg: arithmetic coding
    146 
    147 -- libjpeg: In-memory source and destination managers
    148    See notes below.
    149 
    150 -- cjpeg: Separate quality settings for luminance and chrominance
    151    Note that the libpjeg v7+ API was extended to accommodate this feature only
    152    for convenience purposes.  It has always been possible to implement this
    153    feature with libjpeg v6b (see rdswitch.c for an example.)
    154 
    155 -- cjpeg: 32-bit BMP support
    156 
    157 -- cjpeg: -rgb option
    158 
    159 -- jpegtran: lossless cropping
    160 
    161 -- jpegtran: -perfect option
    162 
    163 -- jpegtran: forcing width/height when performing lossless crop
    164 
    165 -- rdjpgcom: -raw option
    166 
    167 -- rdjpgcom: locale awareness
    168 
    169 
    170 Not supported:
    171 
    172 NOTE:  As of this writing, extensive research has been conducted into the
    173 usefulness of DCT scaling as a means of data reduction and SmartScale as a
    174 means of quality improvement.  The reader is invited to peruse the research at
    175 http://www.libjpeg-turbo.org/About/SmartScale and draw his/her own conclusions,
    176 but it is the general belief of our project that these features have not
    177 demonstrated sufficient usefulness to justify inclusion in libjpeg-turbo.
    178 
    179 -- libjpeg: DCT scaling in compressor
    180    cinfo.scale_num and cinfo.scale_denom are silently ignored.
    181    There is no technical reason why DCT scaling could not be supported when
    182    emulating the libjpeg v7+ API/ABI, but without the SmartScale extension (see
    183    below), only scaling factors of 1/2, 8/15, 4/7, 8/13, 2/3, 8/11, 4/5, and
    184    8/9 would be available, which is of limited usefulness.
    185 
    186 -- libjpeg: SmartScale
    187    cinfo.block_size is silently ignored.
    188    SmartScale is an extension to the JPEG format that allows for DCT block
    189    sizes other than 8x8.  Providing support for this new format would be
    190    feasible (particularly without full acceleration.)  However, until/unless
    191    the format becomes either an official industry standard or, at minimum, an
    192    accepted solution in the community, we are hesitant to implement it, as
    193    there is no sense of whether or how it might change in the future.  It is
    194    our belief that SmartScale has not demonstrated sufficient usefulness as a
    195    lossless format nor as a means of quality enhancement, and thus, our primary
    196    interest in providing this feature would be as a means of supporting
    197    additional DCT scaling factors.
    198 
    199 -- libjpeg: Fancy downsampling in compressor
    200    cinfo.do_fancy_downsampling is silently ignored.
    201    This requires the DCT scaling feature, which is not supported.
    202 
    203 -- jpegtran: Scaling
    204    This requires both the DCT scaling and SmartScale features, which are not
    205    supported.
    206 
    207 -- Lossless RGB JPEG files
    208    This requires the SmartScale feature, which is not supported.
    209 
    210 What About libjpeg v9?
    211 ----------------------
    212 
    213 libjpeg v9 introduced yet another field to the JPEG compression structure
    214 (color_transform), thus making the ABI backward incompatible with that of
    215 libjpeg v8.  This new field was introduced solely for the purpose of supporting
    216 lossless SmartScale encoding.  Further, there was actually no reason to extend
    217 the API in this manner, as the color transform could have just as easily been
    218 activated by way of a new JPEG colorspace constant, thus preserving backward
    219 ABI compatibility.
    220 
    221 Our research (see link above) has shown that lossless SmartScale does not
    222 generally accomplish anything that can't already be accomplished better with
    223 existing, standard lossless formats.  Thus, at this time, it is our belief that
    224 there is not sufficient technical justification for software to upgrade from
    225 libjpeg v8 to libjpeg v9, and therefore, not sufficient technical justification
    226 for us to emulate the libjpeg v9 ABI.
    227 
    228 =====================================
    229 In-Memory Source/Destination Managers
    230 =====================================
    231 
    232 By default, libjpeg-turbo 1.3 and later includes the jpeg_mem_src() and
    233 jpeg_mem_dest() functions, even when not emulating the libjpeg v8 API/ABI.
    234 Previously, it was necessary to build libjpeg-turbo from source with libjpeg v8
    235 API/ABI emulation in order to use the in-memory source/destination managers,
    236 but several projects requested that those functions be included when emulating
    237 the libjpeg v6b API/ABI as well.  This allows the use of those functions by
    238 programs that need them without breaking ABI compatibility for programs that
    239 don't, and it allows those functions to be provided in the "official"
    240 libjpeg-turbo binaries.
    241 
    242 Those who are concerned about maintaining strict conformance with the libjpeg
    243 v6b or v7 API can pass an argument of --without-mem-srcdst to configure or
    244 an argument of -DWITH_MEM_SRCDST=0 to CMake prior to building libjpeg-turbo.
    245 This will restore the pre-1.3 behavior, in which jpeg_mem_src() and
    246 jpeg_mem_dest() are only included when emulating the libjpeg v8 API/ABI.
    247 
    248 On Un*x systems, including the in-memory source/destination managers changes
    249 the dynamic library version from 62.0.0 to 62.1.0 if using libjpeg v6b API/ABI
    250 emulation and from 7.0.0 to 7.1.0 if using libjpeg v7 API/ABI emulation.
    251 
    252 Note that, on most Un*x systems, the dynamic linker will not look for a
    253 function in a library until that function is actually used.  Thus, if a program
    254 is built against libjpeg-turbo 1.3+ and uses jpeg_mem_src() or jpeg_mem_dest(),
    255 that program will not fail if run against an older version of libjpeg-turbo or
    256 against libjpeg v7- until the program actually tries to call jpeg_mem_src() or
    257 jpeg_mem_dest().  Such is not the case on Windows.  If a program is built
    258 against the libjpeg-turbo 1.3+ DLL and uses jpeg_mem_src() or jpeg_mem_dest(),
    259 then it must use the libjpeg-turbo 1.3+ DLL at run time.
    260 
    261 Both cjpeg and djpeg have been extended to allow testing the in-memory
    262 source/destination manager functions.  See their respective man pages for more
    263 details.
    264 
    265 
    266 *******************************************************************************
    267 **     Mathematical Compatibility
    268 *******************************************************************************
    269 
    270 For the most part, libjpeg-turbo should produce identical output to libjpeg
    271 v6b.  The one exception to this is when using the floating point DCT/IDCT, in
    272 which case the outputs of libjpeg v6b and libjpeg-turbo can differ for the
    273 following reasons:
    274 
    275 -- The SSE/SSE2 floating point DCT implementation in libjpeg-turbo is ever so
    276    slightly more accurate than the implementation in libjpeg v6b, but not by
    277    any amount perceptible to human vision (generally in the range of 0.01 to
    278    0.08 dB gain in PNSR.)
    279 -- When not using the SIMD extensions, libjpeg-turbo uses the more accurate
    280    (and slightly faster) floating point IDCT algorithm introduced in libjpeg
    281    v8a as opposed to the algorithm used in libjpeg v6b.  It should be noted,
    282    however, that this algorithm basically brings the accuracy of the floating
    283    point IDCT in line with the accuracy of the slow integer IDCT.  The floating
    284    point DCT/IDCT algorithms are mainly a legacy feature, and they do not
    285    produce significantly more accuracy than the slow integer algorithms (to put
    286    numbers on this, the typical difference in PNSR between the two algorithms
    287    is less than 0.10 dB, whereas changing the quality level by 1 in the upper
    288    range of the quality scale is typically more like a 1.0 dB difference.)
    289 -- If the floating point algorithms in libjpeg-turbo are not implemented using
    290    SIMD instructions on a particular platform, then the accuracy of the
    291    floating point DCT/IDCT can depend on the compiler settings.
    292 
    293 While libjpeg-turbo does emulate the libjpeg v8 API/ABI, under the hood, it is
    294 still using the same algorithms as libjpeg v6b, so there are several specific
    295 cases in which libjpeg-turbo cannot be expected to produce the same output as
    296 libjpeg v8:
    297 
    298 -- When decompressing using scaling factors of 1/2 and 1/4, because libjpeg v8
    299    implements those scaling algorithms differently than libjpeg v6b does, and
    300    libjpeg-turbo's SIMD extensions are based on the libjpeg v6b behavior.
    301 
    302 -- When using chrominance subsampling, because libjpeg v8 implements this
    303    with its DCT/IDCT scaling algorithms rather than with a separate
    304    downsampling/upsampling algorithm.  In our testing, the subsampled/upsampled
    305    output of libjpeg v8 is less accurate than that of libjpeg v6b for this
    306    reason.
    307 
    308 -- When decompressing using a scaling factor > 1 and merged (AKA "non-fancy" or
    309    "non-smooth") chrominance upsampling, because libjpeg v8 does not support
    310    merged upsampling with scaling factors > 1.
    311 
    312 
    313 *******************************************************************************
    314 **     Performance Pitfalls
    315 *******************************************************************************
    316 
    317 ===============
    318 Restart Markers
    319 ===============
    320 
    321 The optimized Huffman decoder in libjpeg-turbo does not handle restart markers
    322 in a way that makes the rest of the libjpeg infrastructure happy, so it is
    323 necessary to use the slow Huffman decoder when decompressing a JPEG image that
    324 has restart markers.  This can cause the decompression performance to drop by
    325 as much as 20%, but the performance will still be much greater than that of
    326 libjpeg.  Many consumer packages, such as PhotoShop, use restart markers when
    327 generating JPEG images, so images generated by those programs will experience
    328 this issue.
    329 
    330 ===============================================
    331 Fast Integer Forward DCT at High Quality Levels
    332 ===============================================
    333 
    334 The algorithm used by the SIMD-accelerated quantization function cannot produce
    335 correct results whenever the fast integer forward DCT is used along with a JPEG
    336 quality of 98-100.  Thus, libjpeg-turbo must use the non-SIMD quantization
    337 function in those cases.  This causes performance to drop by as much as 40%.
    338 It is therefore strongly advised that you use the slow integer forward DCT
    339 whenever encoding images with a JPEG quality of 98 or higher.
    340 

README.android

      1 Any Android specific modifications to upstream libjpeg-turbo (1.5.1) should
      2 be listed here:
      3 
      4 (1) jconfig.h and jconfigint.h
      5 
      6 These are included upstream as jconfig.h.in and jconfigint.h.in.
      7 We have the option autogenerate these platform/version specific files (using
      8 the libjpeg-turbo build system) or to manually create them.
      9 
     10 Autogenerating these files on linux gets us most of the way, but we've needed
     11 to add some multi-platform flexibility to the INLINE and SIZEOF_SIZE_T macros.
     12 
     13 (2) simd/jsimdext.inc
     14 
     15 The modification enables us to compile x86 SIMD.
     16 
     17 The original code was:
     18 %define EXTN(name)   _ %+ name
     19 The new code is:
     20 %define EXTN(name)   name
     21 
     22 It is unclear why the unmodified code from upstream appends an underscore
     23 to name.  Before removing the underscore, the code failed to link because
     24 the function names in the SIMD code did not match the callers (because of
     25 the extra underscore).
     26 
     27 (3) jmemmgr.c
     28 
     29 Fix broken build with NDK platforms < android-21
     30 Cherry picked from upstream:
     31 https://github.com/libjpeg-turbo/libjpeg-turbo/commit/dfefba77520ded5c5fd4864e76352a5f3eb23e74
     32 
     33 (4) rdppm.c
     34 Fix sign mismatch comparison warnings
     35 Cherry picked from upstream:
     36 https://github.com/libjpeg-turbo/libjpeg-turbo/commit/d22fd541bf9dd87889c25909e19a640a580bcad7
     37 

README.ijg

      1 libjpeg-turbo note:  This file has been modified by The libjpeg-turbo Project
      2 to include only information relevant to libjpeg-turbo, to wordsmith certain
      3 sections, and to remove impolitic language that existed in the libjpeg v8
      4 README.  It is included only for reference.  Please see README.md for
      5 information specific to libjpeg-turbo.
      6 
      7 
      8 The Independent JPEG Group's JPEG software
      9 ==========================================
     10 
     11 This distribution contains a release of the Independent JPEG Group's free JPEG
     12 software.  You are welcome to redistribute this software and to use it for any
     13 purpose, subject to the conditions under LEGAL ISSUES, below.
     14 
     15 This software is the work of Tom Lane, Guido Vollbeding, Philip Gladstone,
     16 Bill Allombert, Jim Boucher, Lee Crocker, Bob Friesenhahn, Ben Jackson,
     17 Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi, Ge' Weijers,
     18 and other members of the Independent JPEG Group.
     19 
     20 IJG is not affiliated with the ISO/IEC JTC1/SC29/WG1 standards committee
     21 (also known as JPEG, together with ITU-T SG16).
     22 
     23 
     24 DOCUMENTATION ROADMAP
     25 =====================
     26 
     27 This file contains the following sections:
     28 
     29 OVERVIEW            General description of JPEG and the IJG software.
     30 LEGAL ISSUES        Copyright, lack of warranty, terms of distribution.
     31 REFERENCES          Where to learn more about JPEG.
     32 ARCHIVE LOCATIONS   Where to find newer versions of this software.
     33 FILE FORMAT WARS    Software *not* to get.
     34 TO DO               Plans for future IJG releases.
     35 
     36 Other documentation files in the distribution are:
     37 
     38 User documentation:
     39   usage.txt         Usage instructions for cjpeg, djpeg, jpegtran,
     40                     rdjpgcom, and wrjpgcom.
     41   *.1               Unix-style man pages for programs (same info as usage.txt).
     42   wizard.txt        Advanced usage instructions for JPEG wizards only.
     43   change.log        Version-to-version change highlights.
     44 Programmer and internal documentation:
     45   libjpeg.txt       How to use the JPEG library in your own programs.
     46   example.c         Sample code for calling the JPEG library.
     47   structure.txt     Overview of the JPEG library's internal structure.
     48   coderules.txt     Coding style rules --- please read if you contribute code.
     49 
     50 Please read at least usage.txt.  Some information can also be found in the JPEG
     51 FAQ (Frequently Asked Questions) article.  See ARCHIVE LOCATIONS below to find
     52 out where to obtain the FAQ article.
     53 
     54 If you want to understand how the JPEG code works, we suggest reading one or
     55 more of the REFERENCES, then looking at the documentation files (in roughly
     56 the order listed) before diving into the code.
     57 
     58 
     59 OVERVIEW
     60 ========
     61 
     62 This package contains C software to implement JPEG image encoding, decoding,
     63 and transcoding.  JPEG (pronounced "jay-peg") is a standardized compression
     64 method for full-color and grayscale images.  JPEG's strong suit is compressing
     65 photographic images or other types of images that have smooth color and
     66 brightness transitions between neighboring pixels.  Images with sharp lines or
     67 other abrupt features may not compress well with JPEG, and a higher JPEG
     68 quality may have to be used to avoid visible compression artifacts with such
     69 images.
     70 
     71 JPEG is lossy, meaning that the output pixels are not necessarily identical to
     72 the input pixels.  However, on photographic content and other "smooth" images,
     73 very good compression ratios can be obtained with no visible compression
     74 artifacts, and extremely high compression ratios are possible if you are
     75 willing to sacrifice image quality (by reducing the "quality" setting in the
     76 compressor.)
     77 
     78 This software implements JPEG baseline, extended-sequential, and progressive
     79 compression processes.  Provision is made for supporting all variants of these
     80 processes, although some uncommon parameter settings aren't implemented yet.
     81 We have made no provision for supporting the hierarchical or lossless
     82 processes defined in the standard.
     83 
     84 We provide a set of library routines for reading and writing JPEG image files,
     85 plus two sample applications "cjpeg" and "djpeg", which use the library to
     86 perform conversion between JPEG and some other popular image file formats.
     87 The library is intended to be reused in other applications.
     88 
     89 In order to support file conversion and viewing software, we have included
     90 considerable functionality beyond the bare JPEG coding/decoding capability;
     91 for example, the color quantization modules are not strictly part of JPEG
     92 decoding, but they are essential for output to colormapped file formats or
     93 colormapped displays.  These extra functions can be compiled out of the
     94 library if not required for a particular application.
     95 
     96 We have also included "jpegtran", a utility for lossless transcoding between
     97 different JPEG processes, and "rdjpgcom" and "wrjpgcom", two simple
     98 applications for inserting and extracting textual comments in JFIF files.
     99 
    100 The emphasis in designing this software has been on achieving portability and
    101 flexibility, while also making it fast enough to be useful.  In particular,
    102 the software is not intended to be read as a tutorial on JPEG.  (See the
    103 REFERENCES section for introductory material.)  Rather, it is intended to
    104 be reliable, portable, industrial-strength code.  We do not claim to have
    105 achieved that goal in every aspect of the software, but we strive for it.
    106 
    107 We welcome the use of this software as a component of commercial products.
    108 No royalty is required, but we do ask for an acknowledgement in product
    109 documentation, as described under LEGAL ISSUES.
    110 
    111 
    112 LEGAL ISSUES
    113 ============
    114 
    115 In plain English:
    116 
    117 1. We don't promise that this software works.  (But if you find any bugs,
    118    please let us know!)
    119 2. You can use this software for whatever you want.  You don't have to pay us.
    120 3. You may not pretend that you wrote this software.  If you use it in a
    121    program, you must acknowledge somewhere in your documentation that
    122    you've used the IJG code.
    123 
    124 In legalese:
    125 
    126 The authors make NO WARRANTY or representation, either express or implied,
    127 with respect to this software, its quality, accuracy, merchantability, or
    128 fitness for a particular purpose.  This software is provided "AS IS", and you,
    129 its user, assume the entire risk as to its quality and accuracy.
    130 
    131 This software is copyright (C) 1991-2016, Thomas G. Lane, Guido Vollbeding.
    132 All Rights Reserved except as specified below.
    133 
    134 Permission is hereby granted to use, copy, modify, and distribute this
    135 software (or portions thereof) for any purpose, without fee, subject to these
    136 conditions:
    137 (1) If any part of the source code for this software is distributed, then this
    138 README file must be included, with this copyright and no-warranty notice
    139 unaltered; and any additions, deletions, or changes to the original files
    140 must be clearly indicated in accompanying documentation.
    141 (2) If only executable code is distributed, then the accompanying
    142 documentation must state that "this software is based in part on the work of
    143 the Independent JPEG Group".
    144 (3) Permission for use of this software is granted only if the user accepts
    145 full responsibility for any undesirable consequences; the authors accept
    146 NO LIABILITY for damages of any kind.
    147 
    148 These conditions apply to any software derived from or based on the IJG code,
    149 not just to the unmodified library.  If you use our work, you ought to
    150 acknowledge us.
    151 
    152 Permission is NOT granted for the use of any IJG author's name or company name
    153 in advertising or publicity relating to this software or products derived from
    154 it.  This software may be referred to only as "the Independent JPEG Group's
    155 software".
    156 
    157 We specifically permit and encourage the use of this software as the basis of
    158 commercial products, provided that all warranty or liability claims are
    159 assumed by the product vendor.
    160 
    161 
    162 The Unix configuration script "configure" was produced with GNU Autoconf.
    163 It is copyright by the Free Software Foundation but is freely distributable.
    164 The same holds for its supporting scripts (config.guess, config.sub,
    165 ltmain.sh).  Another support script, install-sh, is copyright by X Consortium
    166 but is also freely distributable.
    167 
    168 The IJG distribution formerly included code to read and write GIF files.
    169 To avoid entanglement with the Unisys LZW patent (now expired), GIF reading
    170 support has been removed altogether, and the GIF writer has been simplified
    171 to produce "uncompressed GIFs".  This technique does not use the LZW
    172 algorithm; the resulting GIF files are larger than usual, but are readable
    173 by all standard GIF decoders.
    174 
    175 We are required to state that
    176     "The Graphics Interchange Format(c) is the Copyright property of
    177     CompuServe Incorporated.  GIF(sm) is a Service Mark property of
    178     CompuServe Incorporated."
    179 
    180 
    181 REFERENCES
    182 ==========
    183 
    184 We recommend reading one or more of these references before trying to
    185 understand the innards of the JPEG software.
    186 
    187 The best short technical introduction to the JPEG compression algorithm is
    188 	Wallace, Gregory K.  "The JPEG Still Picture Compression Standard",
    189 	Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44.
    190 (Adjacent articles in that issue discuss MPEG motion picture compression,
    191 applications of JPEG, and related topics.)  If you don't have the CACM issue
    192 handy, a PDF file containing a revised version of Wallace's article is
    193 available at http://www.ijg.org/files/Wallace.JPEG.pdf.  The file (actually
    194 a preprint for an article that appeared in IEEE Trans. Consumer Electronics)
    195 omits the sample images that appeared in CACM, but it includes corrections
    196 and some added material.  Note: the Wallace article is copyright ACM and IEEE,
    197 and it may not be used for commercial purposes.
    198 
    199 A somewhat less technical, more leisurely introduction to JPEG can be found in
    200 "The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published by
    201 M&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1.  This book provides
    202 good explanations and example C code for a multitude of compression methods
    203 including JPEG.  It is an excellent source if you are comfortable reading C
    204 code but don't know much about data compression in general.  The book's JPEG
    205 sample code is far from industrial-strength, but when you are ready to look
    206 at a full implementation, you've got one here...
    207 
    208 The best currently available description of JPEG is the textbook "JPEG Still
    209 Image Data Compression Standard" by William B. Pennebaker and Joan L.
    210 Mitchell, published by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1.
    211 Price US$59.95, 638 pp.  The book includes the complete text of the ISO JPEG
    212 standards (DIS 10918-1 and draft DIS 10918-2).
    213 
    214 The original JPEG standard is divided into two parts, Part 1 being the actual
    215 specification, while Part 2 covers compliance testing methods.  Part 1 is
    216 titled "Digital Compression and Coding of Continuous-tone Still Images,
    217 Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS
    218 10918-1, ITU-T T.81.  Part 2 is titled "Digital Compression and Coding of
    219 Continuous-tone Still Images, Part 2: Compliance testing" and has document
    220 numbers ISO/IEC IS 10918-2, ITU-T T.83.
    221 
    222 The JPEG standard does not specify all details of an interchangeable file
    223 format.  For the omitted details we follow the "JFIF" conventions, revision
    224 1.02.  JFIF 1.02 has been adopted as an Ecma International Technical Report
    225 and thus received a formal publication status.  It is available as a free
    226 download in PDF format from
    227 http://www.ecma-international.org/publications/techreports/E-TR-098.htm.
    228 A PostScript version of the JFIF document is available at
    229 http://www.ijg.org/files/jfif.ps.gz.  There is also a plain text version at
    230 http://www.ijg.org/files/jfif.txt.gz, but it is missing the figures.
    231 
    232 The TIFF 6.0 file format specification can be obtained by FTP from
    233 ftp://ftp.sgi.com/graphics/tiff/TIFF6.ps.gz.  The JPEG incorporation scheme
    234 found in the TIFF 6.0 spec of 3-June-92 has a number of serious problems.
    235 IJG does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6).
    236 Instead, we recommend the JPEG design proposed by TIFF Technical Note #2
    237 (Compression tag 7).  Copies of this Note can be obtained from
    238 http://www.ijg.org/files/.  It is expected that the next revision
    239 of the TIFF spec will replace the 6.0 JPEG design with the Note's design.
    240 Although IJG's own code does not support TIFF/JPEG, the free libtiff library
    241 uses our library to implement TIFF/JPEG per the Note.
    242 
    243 
    244 ARCHIVE LOCATIONS
    245 =================
    246 
    247 The "official" archive site for this software is www.ijg.org.
    248 The most recent released version can always be found there in
    249 directory "files".
    250 
    251 The JPEG FAQ (Frequently Asked Questions) article is a source of some
    252 general information about JPEG.
    253 It is available on the World Wide Web at http://www.faqs.org/faqs/jpeg-faq/
    254 and other news.answers archive sites, including the official news.answers
    255 archive at rtfm.mit.edu: ftp://rtfm.mit.edu/pub/usenet/news.answers/jpeg-faq/.
    256 If you don't have Web or FTP access, send e-mail to mail-server (a] rtfm.mit.edu
    257 with body
    258 	send usenet/news.answers/jpeg-faq/part1
    259 	send usenet/news.answers/jpeg-faq/part2
    260 
    261 
    262 FILE FORMAT WARS
    263 ================
    264 
    265 The ISO/IEC JTC1/SC29/WG1 standards committee (also known as JPEG, together
    266 with ITU-T SG16) currently promotes different formats containing the name
    267 "JPEG" which are incompatible with original DCT-based JPEG.  IJG therefore does
    268 not support these formats (see REFERENCES).  Indeed, one of the original
    269 reasons for developing this free software was to help force convergence on
    270 common, interoperable format standards for JPEG files.
    271 Don't use an incompatible file format!
    272 (In any case, our decoder will remain capable of reading existing JPEG
    273 image files indefinitely.)
    274 
    275 
    276 TO DO
    277 =====
    278 
    279 Please send bug reports, offers of help, etc. to jpeg-info (a] jpegclub.org.
    280 

README.md

      1 Background
      2 ==========
      3 
      4 libjpeg-turbo is a JPEG image codec that uses SIMD instructions (MMX, SSE2,
      5 NEON, AltiVec) to accelerate baseline JPEG compression and decompression on
      6 x86, x86-64, ARM, and PowerPC systems.  On such systems, libjpeg-turbo is
      7 generally 2-6x as fast as libjpeg, all else being equal.  On other types of
      8 systems, libjpeg-turbo can still outperform libjpeg by a significant amount, by
      9 virtue of its highly-optimized Huffman coding routines.  In many cases, the
     10 performance of libjpeg-turbo rivals that of proprietary high-speed JPEG codecs.
     11 
     12 libjpeg-turbo implements both the traditional libjpeg API as well as the less
     13 powerful but more straightforward TurboJPEG API.  libjpeg-turbo also features
     14 colorspace extensions that allow it to compress from/decompress to 32-bit and
     15 big-endian pixel buffers (RGBX, XBGR, etc.), as well as a full-featured Java
     16 interface.
     17 
     18 libjpeg-turbo was originally based on libjpeg/SIMD, an MMX-accelerated
     19 derivative of libjpeg v6b developed by Miyasaka Masaru.  The TigerVNC and
     20 VirtualGL projects made numerous enhancements to the codec in 2009, and in
     21 early 2010, libjpeg-turbo spun off into an independent project, with the goal
     22 of making high-speed JPEG compression/decompression technology available to a
     23 broader range of users and developers.
     24 
     25 
     26 License
     27 =======
     28 
     29 libjpeg-turbo is covered by three compatible BSD-style open source licenses.
     30 Refer to [LICENSE.md](LICENSE.md) for a roll-up of license terms.
     31 
     32 
     33 Building libjpeg-turbo
     34 ======================
     35 
     36 Refer to [BUILDING.md](BUILDING.md) for complete instructions.
     37 
     38 
     39 Using libjpeg-turbo
     40 ===================
     41 
     42 libjpeg-turbo includes two APIs that can be used to compress and decompress
     43 JPEG images:
     44 
     45 - **TurboJPEG API**<br>
     46   This API provides an easy-to-use interface for compressing and decompressing
     47   JPEG images in memory.  It also provides some functionality that would not be
     48   straightforward to achieve using the underlying libjpeg API, such as
     49   generating planar YUV images and performing multiple simultaneous lossless
     50   transforms on an image.  The Java interface for libjpeg-turbo is written on
     51   top of the TurboJPEG API.
     52 
     53 - **libjpeg API**<br>
     54   This is the de facto industry-standard API for compressing and decompressing
     55   JPEG images.  It is more difficult to use than the TurboJPEG API but also
     56   more powerful.  The libjpeg API implementation in libjpeg-turbo is both
     57   API/ABI-compatible and mathematically compatible with libjpeg v6b.  It can
     58   also optionally be configured to be API/ABI-compatible with libjpeg v7 and v8
     59   (see below.)
     60 
     61 There is no significant performance advantage to either API when both are used
     62 to perform similar operations.
     63 
     64 Colorspace Extensions
     65 ---------------------
     66 
     67 libjpeg-turbo includes extensions that allow JPEG images to be compressed
     68 directly from (and decompressed directly to) buffers that use BGR, BGRX,
     69 RGBX, XBGR, and XRGB pixel ordering.  This is implemented with ten new
     70 colorspace constants:
     71 
     72     JCS_EXT_RGB   /* red/green/blue */
     73     JCS_EXT_RGBX  /* red/green/blue/x */
     74     JCS_EXT_BGR   /* blue/green/red */
     75     JCS_EXT_BGRX  /* blue/green/red/x */
     76     JCS_EXT_XBGR  /* x/blue/green/red */
     77     JCS_EXT_XRGB  /* x/red/green/blue */
     78     JCS_EXT_RGBA  /* red/green/blue/alpha */
     79     JCS_EXT_BGRA  /* blue/green/red/alpha */
     80     JCS_EXT_ABGR  /* alpha/blue/green/red */
     81     JCS_EXT_ARGB  /* alpha/red/green/blue */
     82 
     83 Setting `cinfo.in_color_space` (compression) or `cinfo.out_color_space`
     84 (decompression) to one of these values will cause libjpeg-turbo to read the
     85 red, green, and blue values from (or write them to) the appropriate position in
     86 the pixel when compressing from/decompressing to an RGB buffer.
     87 
     88 Your application can check for the existence of these extensions at compile
     89 time with:
     90 
     91     #ifdef JCS_EXTENSIONS
     92 
     93 At run time, attempting to use these extensions with a libjpeg implementation
     94 that does not support them will result in a "Bogus input colorspace" error.
     95 Applications can trap this error in order to test whether run-time support is
     96 available for the colorspace extensions.
     97 
     98 When using the RGBX, BGRX, XBGR, and XRGB colorspaces during decompression, the
     99 X byte is undefined, and in order to ensure the best performance, libjpeg-turbo
    100 can set that byte to whatever value it wishes.  If an application expects the X
    101 byte to be used as an alpha channel, then it should specify `JCS_EXT_RGBA`,
    102 `JCS_EXT_BGRA`, `JCS_EXT_ABGR`, or `JCS_EXT_ARGB`.  When these colorspace
    103 constants are used, the X byte is guaranteed to be 0xFF, which is interpreted
    104 as opaque.
    105 
    106 Your application can check for the existence of the alpha channel colorspace
    107 extensions at compile time with:
    108 
    109     #ifdef JCS_ALPHA_EXTENSIONS
    110 
    111 [jcstest.c](jcstest.c), located in the libjpeg-turbo source tree, demonstrates
    112 how to check for the existence of the colorspace extensions at compile time and
    113 run time.
    114 
    115 libjpeg v7 and v8 API/ABI Emulation
    116 -----------------------------------
    117 
    118 With libjpeg v7 and v8, new features were added that necessitated extending the
    119 compression and decompression structures.  Unfortunately, due to the exposed
    120 nature of those structures, extending them also necessitated breaking backward
    121 ABI compatibility with previous libjpeg releases.  Thus, programs that were
    122 built to use libjpeg v7 or v8 did not work with libjpeg-turbo, since it is
    123 based on the libjpeg v6b code base.  Although libjpeg v7 and v8 are not
    124 as widely used as v6b, enough programs (including a few Linux distros) made
    125 the switch that there was a demand to emulate the libjpeg v7 and v8 ABIs
    126 in libjpeg-turbo.  It should be noted, however, that this feature was added
    127 primarily so that applications that had already been compiled to use libjpeg
    128 v7+ could take advantage of accelerated baseline JPEG encoding/decoding
    129 without recompiling.  libjpeg-turbo does not claim to support all of the
    130 libjpeg v7+ features, nor to produce identical output to libjpeg v7+ in all
    131 cases (see below.)
    132 
    133 By passing an argument of `--with-jpeg7` or `--with-jpeg8` to `configure`, or
    134 an argument of `-DWITH_JPEG7=1` or `-DWITH_JPEG8=1` to `cmake`, you can build a
    135 version of libjpeg-turbo that emulates the libjpeg v7 or v8 ABI, so that
    136 programs that are built against libjpeg v7 or v8 can be run with libjpeg-turbo.
    137 The following section describes which libjpeg v7+ features are supported and
    138 which aren't.
    139 
    140 ### Support for libjpeg v7 and v8 Features
    141 
    142 #### Fully supported
    143 
    144 - **libjpeg: IDCT scaling extensions in decompressor**<br>
    145   libjpeg-turbo supports IDCT scaling with scaling factors of 1/8, 1/4, 3/8,
    146   1/2, 5/8, 3/4, 7/8, 9/8, 5/4, 11/8, 3/2, 13/8, 7/4, 15/8, and 2/1 (only 1/4
    147   and 1/2 are SIMD-accelerated.)
    148 
    149 - **libjpeg: Arithmetic coding**
    150 
    151 - **libjpeg: In-memory source and destination managers**<br>
    152   See notes below.
    153 
    154 - **cjpeg: Separate quality settings for luminance and chrominance**<br>
    155   Note that the libpjeg v7+ API was extended to accommodate this feature only
    156   for convenience purposes.  It has always been possible to implement this
    157   feature with libjpeg v6b (see rdswitch.c for an example.)
    158 
    159 - **cjpeg: 32-bit BMP support**
    160 
    161 - **cjpeg: `-rgb` option**
    162 
    163 - **jpegtran: Lossless cropping**
    164 
    165 - **jpegtran: `-perfect` option**
    166 
    167 - **jpegtran: Forcing width/height when performing lossless crop**
    168 
    169 - **rdjpgcom: `-raw` option**
    170 
    171 - **rdjpgcom: Locale awareness**
    172 
    173 
    174 #### Not supported
    175 
    176 NOTE:  As of this writing, extensive research has been conducted into the
    177 usefulness of DCT scaling as a means of data reduction and SmartScale as a
    178 means of quality improvement.  The reader is invited to peruse the research at
    179 <http://www.libjpeg-turbo.org/About/SmartScale> and draw his/her own conclusions,
    180 but it is the general belief of our project that these features have not
    181 demonstrated sufficient usefulness to justify inclusion in libjpeg-turbo.
    182 
    183 - **libjpeg: DCT scaling in compressor**<br>
    184   `cinfo.scale_num` and `cinfo.scale_denom` are silently ignored.
    185   There is no technical reason why DCT scaling could not be supported when
    186   emulating the libjpeg v7+ API/ABI, but without the SmartScale extension (see
    187   below), only scaling factors of 1/2, 8/15, 4/7, 8/13, 2/3, 8/11, 4/5, and
    188   8/9 would be available, which is of limited usefulness.
    189 
    190 - **libjpeg: SmartScale**<br>
    191   `cinfo.block_size` is silently ignored.
    192   SmartScale is an extension to the JPEG format that allows for DCT block
    193   sizes other than 8x8.  Providing support for this new format would be
    194   feasible (particularly without full acceleration.)  However, until/unless
    195   the format becomes either an official industry standard or, at minimum, an
    196   accepted solution in the community, we are hesitant to implement it, as
    197   there is no sense of whether or how it might change in the future.  It is
    198   our belief that SmartScale has not demonstrated sufficient usefulness as a
    199   lossless format nor as a means of quality enhancement, and thus our primary
    200   interest in providing this feature would be as a means of supporting
    201   additional DCT scaling factors.
    202 
    203 - **libjpeg: Fancy downsampling in compressor**<br>
    204   `cinfo.do_fancy_downsampling` is silently ignored.
    205   This requires the DCT scaling feature, which is not supported.
    206 
    207 - **jpegtran: Scaling**<br>
    208   This requires both the DCT scaling and SmartScale features, which are not
    209   supported.
    210 
    211 - **Lossless RGB JPEG files**<br>
    212   This requires the SmartScale feature, which is not supported.
    213 
    214 ### What About libjpeg v9?
    215 
    216 libjpeg v9 introduced yet another field to the JPEG compression structure
    217 (`color_transform`), thus making the ABI backward incompatible with that of
    218 libjpeg v8.  This new field was introduced solely for the purpose of supporting
    219 lossless SmartScale encoding.  Furthermore, there was actually no reason to
    220 extend the API in this manner, as the color transform could have just as easily
    221 been activated by way of a new JPEG colorspace constant, thus preserving
    222 backward ABI compatibility.
    223 
    224 Our research (see link above) has shown that lossless SmartScale does not
    225 generally accomplish anything that can't already be accomplished better with
    226 existing, standard lossless formats.  Therefore, at this time it is our belief
    227 that there is not sufficient technical justification for software projects to
    228 upgrade from libjpeg v8 to libjpeg v9, and thus there is not sufficient
    229 technical justification for us to emulate the libjpeg v9 ABI.
    230 
    231 In-Memory Source/Destination Managers
    232 -------------------------------------
    233 
    234 By default, libjpeg-turbo 1.3 and later includes the `jpeg_mem_src()` and
    235 `jpeg_mem_dest()` functions, even when not emulating the libjpeg v8 API/ABI.
    236 Previously, it was necessary to build libjpeg-turbo from source with libjpeg v8
    237 API/ABI emulation in order to use the in-memory source/destination managers,
    238 but several projects requested that those functions be included when emulating
    239 the libjpeg v6b API/ABI as well.  This allows the use of those functions by
    240 programs that need them, without breaking ABI compatibility for programs that
    241 don't, and it allows those functions to be provided in the "official"
    242 libjpeg-turbo binaries.
    243 
    244 Those who are concerned about maintaining strict conformance with the libjpeg
    245 v6b or v7 API can pass an argument of `--without-mem-srcdst` to `configure` or
    246 an argument of `-DWITH_MEM_SRCDST=0` to `cmake` prior to building
    247 libjpeg-turbo.  This will restore the pre-1.3 behavior, in which
    248 `jpeg_mem_src()` and `jpeg_mem_dest()` are only included when emulating the
    249 libjpeg v8 API/ABI.
    250 
    251 On Un*x systems, including the in-memory source/destination managers changes
    252 the dynamic library version from 62.1.0 to 62.2.0 if using libjpeg v6b API/ABI
    253 emulation and from 7.1.0 to 7.2.0 if using libjpeg v7 API/ABI emulation.
    254 
    255 Note that, on most Un*x systems, the dynamic linker will not look for a
    256 function in a library until that function is actually used.  Thus, if a program
    257 is built against libjpeg-turbo 1.3+ and uses `jpeg_mem_src()` or
    258 `jpeg_mem_dest()`, that program will not fail if run against an older version
    259 of libjpeg-turbo or against libjpeg v7- until the program actually tries to
    260 call `jpeg_mem_src()` or `jpeg_mem_dest()`.  Such is not the case on Windows.
    261 If a program is built against the libjpeg-turbo 1.3+ DLL and uses
    262 `jpeg_mem_src()` or `jpeg_mem_dest()`, then it must use the libjpeg-turbo 1.3+
    263 DLL at run time.
    264 
    265 Both cjpeg and djpeg have been extended to allow testing the in-memory
    266 source/destination manager functions.  See their respective man pages for more
    267 details.
    268 
    269 
    270 Mathematical Compatibility
    271 ==========================
    272 
    273 For the most part, libjpeg-turbo should produce identical output to libjpeg
    274 v6b.  The one exception to this is when using the floating point DCT/IDCT, in
    275 which case the outputs of libjpeg v6b and libjpeg-turbo can differ for the
    276 following reasons:
    277 
    278 - The SSE/SSE2 floating point DCT implementation in libjpeg-turbo is ever so
    279   slightly more accurate than the implementation in libjpeg v6b, but not by
    280   any amount perceptible to human vision (generally in the range of 0.01 to
    281   0.08 dB gain in PNSR.)
    282 
    283 - When not using the SIMD extensions, libjpeg-turbo uses the more accurate
    284   (and slightly faster) floating point IDCT algorithm introduced in libjpeg
    285   v8a as opposed to the algorithm used in libjpeg v6b.  It should be noted,
    286   however, that this algorithm basically brings the accuracy of the floating
    287   point IDCT in line with the accuracy of the slow integer IDCT.  The floating
    288   point DCT/IDCT algorithms are mainly a legacy feature, and they do not
    289   produce significantly more accuracy than the slow integer algorithms (to put
    290   numbers on this, the typical difference in PNSR between the two algorithms
    291   is less than 0.10 dB, whereas changing the quality level by 1 in the upper
    292   range of the quality scale is typically more like a 1.0 dB difference.)
    293 
    294 - If the floating point algorithms in libjpeg-turbo are not implemented using
    295   SIMD instructions on a particular platform, then the accuracy of the
    296   floating point DCT/IDCT can depend on the compiler settings.
    297 
    298 While libjpeg-turbo does emulate the libjpeg v8 API/ABI, under the hood it is
    299 still using the same algorithms as libjpeg v6b, so there are several specific
    300 cases in which libjpeg-turbo cannot be expected to produce the same output as
    301 libjpeg v8:
    302 
    303 - When decompressing using scaling factors of 1/2 and 1/4, because libjpeg v8
    304   implements those scaling algorithms differently than libjpeg v6b does, and
    305   libjpeg-turbo's SIMD extensions are based on the libjpeg v6b behavior.
    306 
    307 - When using chrominance subsampling, because libjpeg v8 implements this
    308   with its DCT/IDCT scaling algorithms rather than with a separate
    309   downsampling/upsampling algorithm.  In our testing, the subsampled/upsampled
    310   output of libjpeg v8 is less accurate than that of libjpeg v6b for this
    311   reason.
    312 
    313 - When decompressing using a scaling factor > 1 and merged (AKA "non-fancy" or
    314   "non-smooth") chrominance upsampling, because libjpeg v8 does not support
    315   merged upsampling with scaling factors > 1.
    316 
    317 
    318 Performance Pitfalls
    319 ====================
    320 
    321 Restart Markers
    322 ---------------
    323 
    324 The optimized Huffman decoder in libjpeg-turbo does not handle restart markers
    325 in a way that makes the rest of the libjpeg infrastructure happy, so it is
    326 necessary to use the slow Huffman decoder when decompressing a JPEG image that
    327 has restart markers.  This can cause the decompression performance to drop by
    328 as much as 20%, but the performance will still be much greater than that of
    329 libjpeg.  Many consumer packages, such as PhotoShop, use restart markers when
    330 generating JPEG images, so images generated by those programs will experience
    331 this issue.
    332 
    333 Fast Integer Forward DCT at High Quality Levels
    334 -----------------------------------------------
    335 
    336 The algorithm used by the SIMD-accelerated quantization function cannot produce
    337 correct results whenever the fast integer forward DCT is used along with a JPEG
    338 quality of 98-100.  Thus, libjpeg-turbo must use the non-SIMD quantization
    339 function in those cases.  This causes performance to drop by as much as 40%.
    340 It is therefore strongly advised that you use the slow integer forward DCT
    341 whenever encoding images with a JPEG quality of 98 or higher.
    342 

README.version

      1 URL: https://sourceforge.net/projects/libjpeg-turbo/files/1.5.1/libjpeg-turbo-1.5.1.tar.gz/download
      2 Version: 1.5.1
      3 BugComponent: 24950
      4 Owners: msarett
      5