Audio plugin host https://kx.studio/carla
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README 19KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385
  1. The Independent JPEG Group's JPEG software
  2. ==========================================
  3. README for release 6b of 27-Mar-1998
  4. ====================================
  5. This distribution contains the sixth public release of the Independent JPEG
  6. Group's free JPEG software. You are welcome to redistribute this software and
  7. to use it for any purpose, subject to the conditions under LEGAL ISSUES, below.
  8. Serious users of this software (particularly those incorporating it into
  9. larger programs) should contact IJG at jpeg-info@uunet.uu.net to be added to
  10. our electronic mailing list. Mailing list members are notified of updates
  11. and have a chance to participate in technical discussions, etc.
  12. This software is the work of Tom Lane, Philip Gladstone, Jim Boucher,
  13. Lee Crocker, Julian Minguillon, Luis Ortiz, George Phillips, Davide Rossi,
  14. Guido Vollbeding, Ge' Weijers, and other members of the Independent JPEG
  15. Group.
  16. IJG is not affiliated with the official ISO JPEG standards committee.
  17. DOCUMENTATION ROADMAP
  18. =====================
  19. This file contains the following sections:
  20. OVERVIEW General description of JPEG and the IJG software.
  21. LEGAL ISSUES Copyright, lack of warranty, terms of distribution.
  22. REFERENCES Where to learn more about JPEG.
  23. ARCHIVE LOCATIONS Where to find newer versions of this software.
  24. RELATED SOFTWARE Other stuff you should get.
  25. FILE FORMAT WARS Software *not* to get.
  26. TO DO Plans for future IJG releases.
  27. Other documentation files in the distribution are:
  28. User documentation:
  29. install.doc How to configure and install the IJG software.
  30. usage.doc Usage instructions for cjpeg, djpeg, jpegtran,
  31. rdjpgcom, and wrjpgcom.
  32. *.1 Unix-style man pages for programs (same info as usage.doc).
  33. wizard.doc Advanced usage instructions for JPEG wizards only.
  34. change.log Version-to-version change highlights.
  35. Programmer and internal documentation:
  36. libjpeg.doc How to use the JPEG library in your own programs.
  37. example.c Sample code for calling the JPEG library.
  38. structure.doc Overview of the JPEG library's internal structure.
  39. filelist.doc Road map of IJG files.
  40. coderules.doc Coding style rules --- please read if you contribute code.
  41. Please read at least the files install.doc and usage.doc. Useful information
  42. can also be found in the JPEG FAQ (Frequently Asked Questions) article. See
  43. ARCHIVE LOCATIONS below to find out where to obtain the FAQ article.
  44. If you want to understand how the JPEG code works, we suggest reading one or
  45. more of the REFERENCES, then looking at the documentation files (in roughly
  46. the order listed) before diving into the code.
  47. OVERVIEW
  48. ========
  49. This package contains C software to implement JPEG image compression and
  50. decompression. JPEG (pronounced "jay-peg") is a standardized compression
  51. method for full-color and gray-scale images. JPEG is intended for compressing
  52. "real-world" scenes; line drawings, cartoons and other non-realistic images
  53. are not its strong suit. JPEG is lossy, meaning that the output image is not
  54. exactly identical to the input image. Hence you must not use JPEG if you
  55. have to have identical output bits. However, on typical photographic images,
  56. very good compression levels can be obtained with no visible change, and
  57. remarkably high compression levels are possible if you can tolerate a
  58. low-quality image. For more details, see the references, or just experiment
  59. with various compression settings.
  60. This software implements JPEG baseline, extended-sequential, and progressive
  61. compression processes. Provision is made for supporting all variants of these
  62. processes, although some uncommon parameter settings aren't implemented yet.
  63. For legal reasons, we are not distributing code for the arithmetic-coding
  64. variants of JPEG; see LEGAL ISSUES. We have made no provision for supporting
  65. the hierarchical or lossless processes defined in the standard.
  66. We provide a set of library routines for reading and writing JPEG image files,
  67. plus two sample applications "cjpeg" and "djpeg", which use the library to
  68. perform conversion between JPEG and some other popular image file formats.
  69. The library is intended to be reused in other applications.
  70. In order to support file conversion and viewing software, we have included
  71. considerable functionality beyond the bare JPEG coding/decoding capability;
  72. for example, the color quantization modules are not strictly part of JPEG
  73. decoding, but they are essential for output to colormapped file formats or
  74. colormapped displays. These extra functions can be compiled out of the
  75. library if not required for a particular application. We have also included
  76. "jpegtran", a utility for lossless transcoding between different JPEG
  77. processes, and "rdjpgcom" and "wrjpgcom", two simple applications for
  78. inserting and extracting textual comments in JFIF files.
  79. The emphasis in designing this software has been on achieving portability and
  80. flexibility, while also making it fast enough to be useful. In particular,
  81. the software is not intended to be read as a tutorial on JPEG. (See the
  82. REFERENCES section for introductory material.) Rather, it is intended to
  83. be reliable, portable, industrial-strength code. We do not claim to have
  84. achieved that goal in every aspect of the software, but we strive for it.
  85. We welcome the use of this software as a component of commercial products.
  86. No royalty is required, but we do ask for an acknowledgement in product
  87. documentation, as described under LEGAL ISSUES.
  88. LEGAL ISSUES
  89. ============
  90. In plain English:
  91. 1. We don't promise that this software works. (But if you find any bugs,
  92. please let us know!)
  93. 2. You can use this software for whatever you want. You don't have to pay us.
  94. 3. You may not pretend that you wrote this software. If you use it in a
  95. program, you must acknowledge somewhere in your documentation that
  96. you've used the IJG code.
  97. In legalese:
  98. The authors make NO WARRANTY or representation, either express or implied,
  99. with respect to this software, its quality, accuracy, merchantability, or
  100. fitness for a particular purpose. This software is provided "AS IS", and you,
  101. its user, assume the entire risk as to its quality and accuracy.
  102. This software is copyright (C) 1991-1998, Thomas G. Lane.
  103. All Rights Reserved except as specified below.
  104. Permission is hereby granted to use, copy, modify, and distribute this
  105. software (or portions thereof) for any purpose, without fee, subject to these
  106. conditions:
  107. (1) If any part of the source code for this software is distributed, then this
  108. README file must be included, with this copyright and no-warranty notice
  109. unaltered; and any additions, deletions, or changes to the original files
  110. must be clearly indicated in accompanying documentation.
  111. (2) If only executable code is distributed, then the accompanying
  112. documentation must state that "this software is based in part on the work of
  113. the Independent JPEG Group".
  114. (3) Permission for use of this software is granted only if the user accepts
  115. full responsibility for any undesirable consequences; the authors accept
  116. NO LIABILITY for damages of any kind.
  117. These conditions apply to any software derived from or based on the IJG code,
  118. not just to the unmodified library. If you use our work, you ought to
  119. acknowledge us.
  120. Permission is NOT granted for the use of any IJG author's name or company name
  121. in advertising or publicity relating to this software or products derived from
  122. it. This software may be referred to only as "the Independent JPEG Group's
  123. software".
  124. We specifically permit and encourage the use of this software as the basis of
  125. commercial products, provided that all warranty or liability claims are
  126. assumed by the product vendor.
  127. ansi2knr.c is included in this distribution by permission of L. Peter Deutsch,
  128. sole proprietor of its copyright holder, Aladdin Enterprises of Menlo Park, CA.
  129. ansi2knr.c is NOT covered by the above copyright and conditions, but instead
  130. by the usual distribution terms of the Free Software Foundation; principally,
  131. that you must include source code if you redistribute it. (See the file
  132. ansi2knr.c for full details.) However, since ansi2knr.c is not needed as part
  133. of any program generated from the IJG code, this does not limit you more than
  134. the foregoing paragraphs do.
  135. The Unix configuration script "configure" was produced with GNU Autoconf.
  136. It is copyright by the Free Software Foundation but is freely distributable.
  137. The same holds for its supporting scripts (config.guess, config.sub,
  138. ltconfig, ltmain.sh). Another support script, install-sh, is copyright
  139. by M.I.T. but is also freely distributable.
  140. It appears that the arithmetic coding option of the JPEG spec is covered by
  141. patents owned by IBM, AT&T, and Mitsubishi. Hence arithmetic coding cannot
  142. legally be used without obtaining one or more licenses. For this reason,
  143. support for arithmetic coding has been removed from the free JPEG software.
  144. (Since arithmetic coding provides only a marginal gain over the unpatented
  145. Huffman mode, it is unlikely that very many implementations will support it.)
  146. So far as we are aware, there are no patent restrictions on the remaining
  147. code.
  148. The IJG distribution formerly included code to read and write GIF files.
  149. To avoid entanglement with the Unisys LZW patent, GIF reading support has
  150. been removed altogether, and the GIF writer has been simplified to produce
  151. "uncompressed GIFs". This technique does not use the LZW algorithm; the
  152. resulting GIF files are larger than usual, but are readable by all standard
  153. GIF decoders.
  154. We are required to state that
  155. "The Graphics Interchange Format(c) is the Copyright property of
  156. CompuServe Incorporated. GIF(sm) is a Service Mark property of
  157. CompuServe Incorporated."
  158. REFERENCES
  159. ==========
  160. We highly recommend reading one or more of these references before trying to
  161. understand the innards of the JPEG software.
  162. The best short technical introduction to the JPEG compression algorithm is
  163. Wallace, Gregory K. "The JPEG Still Picture Compression Standard",
  164. Communications of the ACM, April 1991 (vol. 34 no. 4), pp. 30-44.
  165. (Adjacent articles in that issue discuss MPEG motion picture compression,
  166. applications of JPEG, and related topics.) If you don't have the CACM issue
  167. handy, a PostScript file containing a revised version of Wallace's article is
  168. available at ftp://ftp.uu.net/graphics/jpeg/wallace.ps.gz. The file (actually
  169. a preprint for an article that appeared in IEEE Trans. Consumer Electronics)
  170. omits the sample images that appeared in CACM, but it includes corrections
  171. and some added material. Note: the Wallace article is copyright ACM and IEEE,
  172. and it may not be used for commercial purposes.
  173. A somewhat less technical, more leisurely introduction to JPEG can be found in
  174. "The Data Compression Book" by Mark Nelson and Jean-loup Gailly, published by
  175. M&T Books (New York), 2nd ed. 1996, ISBN 1-55851-434-1. This book provides
  176. good explanations and example C code for a multitude of compression methods
  177. including JPEG. It is an excellent source if you are comfortable reading C
  178. code but don't know much about data compression in general. The book's JPEG
  179. sample code is far from industrial-strength, but when you are ready to look
  180. at a full implementation, you've got one here...
  181. The best full description of JPEG is the textbook "JPEG Still Image Data
  182. Compression Standard" by William B. Pennebaker and Joan L. Mitchell, published
  183. by Van Nostrand Reinhold, 1993, ISBN 0-442-01272-1. Price US$59.95, 638 pp.
  184. The book includes the complete text of the ISO JPEG standards (DIS 10918-1
  185. and draft DIS 10918-2). This is by far the most complete exposition of JPEG
  186. in existence, and we highly recommend it.
  187. The JPEG standard itself is not available electronically; you must order a
  188. paper copy through ISO or ITU. (Unless you feel a need to own a certified
  189. official copy, we recommend buying the Pennebaker and Mitchell book instead;
  190. it's much cheaper and includes a great deal of useful explanatory material.)
  191. In the USA, copies of the standard may be ordered from ANSI Sales at (212)
  192. 642-4900, or from Global Engineering Documents at (800) 854-7179. (ANSI
  193. doesn't take credit card orders, but Global does.) It's not cheap: as of
  194. 1992, ANSI was charging $95 for Part 1 and $47 for Part 2, plus 7%
  195. shipping/handling. The standard is divided into two parts, Part 1 being the
  196. actual specification, while Part 2 covers compliance testing methods. Part 1
  197. is titled "Digital Compression and Coding of Continuous-tone Still Images,
  198. Part 1: Requirements and guidelines" and has document numbers ISO/IEC IS
  199. 10918-1, ITU-T T.81. Part 2 is titled "Digital Compression and Coding of
  200. Continuous-tone Still Images, Part 2: Compliance testing" and has document
  201. numbers ISO/IEC IS 10918-2, ITU-T T.83.
  202. Some extensions to the original JPEG standard are defined in JPEG Part 3,
  203. a newer ISO standard numbered ISO/IEC IS 10918-3 and ITU-T T.84. IJG
  204. currently does not support any Part 3 extensions.
  205. The JPEG standard does not specify all details of an interchangeable file
  206. format. For the omitted details we follow the "JFIF" conventions, revision
  207. 1.02. A copy of the JFIF spec is available from:
  208. Literature Department
  209. C-Cube Microsystems, Inc.
  210. 1778 McCarthy Blvd.
  211. Milpitas, CA 95035
  212. phone (408) 944-6300, fax (408) 944-6314
  213. A PostScript version of this document is available by FTP at
  214. ftp://ftp.uu.net/graphics/jpeg/jfif.ps.gz. There is also a plain text
  215. version at ftp://ftp.uu.net/graphics/jpeg/jfif.txt.gz, but it is missing
  216. the figures.
  217. The TIFF 6.0 file format specification can be obtained by FTP from
  218. ftp://ftp.sgi.com/graphics/tiff/TIFF6.ps.gz. The JPEG incorporation scheme
  219. found in the TIFF 6.0 spec of 3-June-92 has a number of serious problems.
  220. IJG does not recommend use of the TIFF 6.0 design (TIFF Compression tag 6).
  221. Instead, we recommend the JPEG design proposed by TIFF Technical Note #2
  222. (Compression tag 7). Copies of this Note can be obtained from ftp.sgi.com or
  223. from ftp://ftp.uu.net/graphics/jpeg/. It is expected that the next revision
  224. of the TIFF spec will replace the 6.0 JPEG design with the Note's design.
  225. Although IJG's own code does not support TIFF/JPEG, the free libtiff library
  226. uses our library to implement TIFF/JPEG per the Note. libtiff is available
  227. from ftp://ftp.sgi.com/graphics/tiff/.
  228. ARCHIVE LOCATIONS
  229. =================
  230. The "official" archive site for this software is ftp.uu.net (Internet
  231. address 192.48.96.9). The most recent released version can always be found
  232. there in directory graphics/jpeg. This particular version will be archived
  233. as ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz. If you don't have
  234. direct Internet access, UUNET's archives are also available via UUCP; contact
  235. help@uunet.uu.net for information on retrieving files that way.
  236. Numerous Internet sites maintain copies of the UUNET files. However, only
  237. ftp.uu.net is guaranteed to have the latest official version.
  238. You can also obtain this software in DOS-compatible "zip" archive format from
  239. the SimTel archives (ftp://ftp.simtel.net/pub/simtelnet/msdos/graphics/), or
  240. on CompuServe in the Graphics Support forum (GO CIS:GRAPHSUP), library 12
  241. "JPEG Tools". Again, these versions may sometimes lag behind the ftp.uu.net
  242. release.
  243. The JPEG FAQ (Frequently Asked Questions) article is a useful source of
  244. general information about JPEG. It is updated constantly and therefore is
  245. not included in this distribution. The FAQ is posted every two weeks to
  246. Usenet newsgroups comp.graphics.misc, news.answers, and other groups.
  247. It is available on the World Wide Web at http://www.faqs.org/faqs/jpeg-faq/
  248. and other news.answers archive sites, including the official news.answers
  249. archive at rtfm.mit.edu: ftp://rtfm.mit.edu/pub/usenet/news.answers/jpeg-faq/.
  250. If you don't have Web or FTP access, send e-mail to mail-server@rtfm.mit.edu
  251. with body
  252. send usenet/news.answers/jpeg-faq/part1
  253. send usenet/news.answers/jpeg-faq/part2
  254. RELATED SOFTWARE
  255. ================
  256. Numerous viewing and image manipulation programs now support JPEG. (Quite a
  257. few of them use this library to do so.) The JPEG FAQ described above lists
  258. some of the more popular free and shareware viewers, and tells where to
  259. obtain them on Internet.
  260. If you are on a Unix machine, we highly recommend Jef Poskanzer's free
  261. PBMPLUS software, which provides many useful operations on PPM-format image
  262. files. In particular, it can convert PPM images to and from a wide range of
  263. other formats, thus making cjpeg/djpeg considerably more useful. The latest
  264. version is distributed by the NetPBM group, and is available from numerous
  265. sites, notably ftp://wuarchive.wustl.edu/graphics/graphics/packages/NetPBM/.
  266. Unfortunately PBMPLUS/NETPBM is not nearly as portable as the IJG software is;
  267. you are likely to have difficulty making it work on any non-Unix machine.
  268. A different free JPEG implementation, written by the PVRG group at Stanford,
  269. is available from ftp://havefun.stanford.edu/pub/jpeg/. This program
  270. is designed for research and experimentation rather than production use;
  271. it is slower, harder to use, and less portable than the IJG code, but it
  272. is easier to read and modify. Also, the PVRG code supports lossless JPEG,
  273. which we do not. (On the other hand, it doesn't do progressive JPEG.)
  274. FILE FORMAT WARS
  275. ================
  276. Some JPEG programs produce files that are not compatible with our library.
  277. The root of the problem is that the ISO JPEG committee failed to specify a
  278. concrete file format. Some vendors "filled in the blanks" on their own,
  279. creating proprietary formats that no one else could read. (For example, none
  280. of the early commercial JPEG implementations for the Macintosh were able to
  281. exchange compressed files.)
  282. The file format we have adopted is called JFIF (see REFERENCES). This format
  283. has been agreed to by a number of major commercial JPEG vendors, and it has
  284. become the de facto standard. JFIF is a minimal or "low end" representation.
  285. We recommend the use of TIFF/JPEG (TIFF revision 6.0 as modified by TIFF
  286. Technical Note #2) for "high end" applications that need to record a lot of
  287. additional data about an image. TIFF/JPEG is fairly new and not yet widely
  288. supported, unfortunately.
  289. The upcoming JPEG Part 3 standard defines a file format called SPIFF.
  290. SPIFF is interoperable with JFIF, in the sense that most JFIF decoders should
  291. be able to read the most common variant of SPIFF. SPIFF has some technical
  292. advantages over JFIF, but its major claim to fame is simply that it is an
  293. official standard rather than an informal one. At this point it is unclear
  294. whether SPIFF will supersede JFIF or whether JFIF will remain the de-facto
  295. standard. IJG intends to support SPIFF once the standard is frozen, but we
  296. have not decided whether it should become our default output format or not.
  297. (In any case, our decoder will remain capable of reading JFIF indefinitely.)
  298. Various proprietary file formats incorporating JPEG compression also exist.
  299. We have little or no sympathy for the existence of these formats. Indeed,
  300. one of the original reasons for developing this free software was to help
  301. force convergence on common, open format standards for JPEG files. Don't
  302. use a proprietary file format!
  303. TO DO
  304. =====
  305. The major thrust for v7 will probably be improvement of visual quality.
  306. The current method for scaling the quantization tables is known not to be
  307. very good at low Q values. We also intend to investigate block boundary
  308. smoothing, "poor man's variable quantization", and other means of improving
  309. quality-vs-file-size performance without sacrificing compatibility.
  310. In future versions, we are considering supporting some of the upcoming JPEG
  311. Part 3 extensions --- principally, variable quantization and the SPIFF file
  312. format.
  313. As always, speeding things up is of great interest.
  314. Please send bug reports, offers of help, etc. to jpeg-info@uunet.uu.net.