source: trunk/libjpeg/cjpeg.1 @ 15

Last change on this file since 15 was 15, checked in by Eugene Romanenko, 15 years ago

needed libs update

File size: 10.2 KB
1.TH CJPEG 1 "20 March 1998"
3cjpeg \- compress an image file to a JPEG file
5.B cjpeg
7.I options
10.I filename
15.B cjpeg
16compresses the named image file, or the standard input if no file is
17named, and produces a JPEG/JFIF file on the standard output.
18The currently supported input file formats are: PPM (PBMPLUS color
19format), PGM (PBMPLUS gray-scale format), BMP, Targa, and RLE (Utah Raster
20Toolkit format).  (RLE is supported only if the URT library is available.)
22All switch names may be abbreviated; for example,
23.B \-grayscale
24may be written
25.B \-gray
27.BR \-gr .
28Most of the "basic" switches can be abbreviated to as little as one letter.
29Upper and lower case are equivalent (thus
30.B \-BMP
31is the same as
32.BR \-bmp ).
33British spellings are also accepted (e.g.,
34.BR \-greyscale ),
35though for brevity these are not mentioned below.
37The basic switches are:
39.BI \-quality " N"
40Scale quantization tables to adjust image quality.  Quality is 0 (worst) to
41100 (best); default is 75.  (See below for more info.)
43.B \-grayscale
44Create monochrome JPEG file from color input.  Be sure to use this switch when
45compressing a grayscale BMP file, because
46.B cjpeg
47isn't bright enough to notice whether a BMP file uses only shades of gray.
48By saying
49.BR \-grayscale ,
50you'll get a smaller JPEG file that takes less time to process.
52.B \-optimize
53Perform optimization of entropy encoding parameters.  Without this, default
54encoding parameters are used.
55.B \-optimize
56usually makes the JPEG file a little smaller, but
57.B cjpeg
58runs somewhat slower and needs much more memory.  Image quality and speed of
59decompression are unaffected by
60.BR \-optimize .
62.B \-progressive
63Create progressive JPEG file (see below).
65.B \-targa
66Input file is Targa format.  Targa files that contain an "identification"
67field will not be automatically recognized by
68.BR cjpeg ;
69for such files you must specify
70.B \-targa
71to make
72.B cjpeg
73treat the input as Targa format.
74For most Targa files, you won't need this switch.
77.B \-quality
78switch lets you trade off compressed file size against quality of the
79reconstructed image: the higher the quality setting, the larger the JPEG file,
80and the closer the output image will be to the original input.  Normally you
81want to use the lowest quality setting (smallest file) that decompresses into
82something visually indistinguishable from the original image.  For this
83purpose the quality setting should be between 50 and 95; the default of 75 is
84often about right.  If you see defects at
85.B \-quality
8675, then go up 5 or 10 counts at a time until you are happy with the output
87image.  (The optimal setting will vary from one image to another.)
89.B \-quality
90100 will generate a quantization table of all 1's, minimizing loss in the
91quantization step (but there is still information loss in subsampling, as well
92as roundoff error).  This setting is mainly of interest for experimental
93purposes.  Quality values above about 95 are
94.B not
95recommended for normal use; the compressed file size goes up dramatically for
96hardly any gain in output image quality.
98In the other direction, quality values below 50 will produce very small files
99of low image quality.  Settings around 5 to 10 might be useful in preparing an
100index of a large image library, for example.  Try
101.B \-quality
1022 (or so) for some amusing Cubist effects.  (Note: quality
103values below about 25 generate 2-byte quantization tables, which are
104considered optional in the JPEG standard.
105.B cjpeg
106emits a warning message when you give such a quality value, because some
107other JPEG programs may be unable to decode the resulting file.  Use
108.B \-baseline
109if you need to ensure compatibility at low quality values.)
112.B \-progressive
113switch creates a "progressive JPEG" file.  In this type of JPEG file, the data
114is stored in multiple scans of increasing quality.  If the file is being
115transmitted over a slow communications link, the decoder can use the first
116scan to display a low-quality image very quickly, and can then improve the
117display with each subsequent scan.  The final image is exactly equivalent to a
118standard JPEG file of the same quality setting, and the total file size is
119about the same --- often a little smaller.
120.B Caution:
121progressive JPEG is not yet widely implemented, so many decoders will be
122unable to view a progressive JPEG file at all.
124Switches for advanced users:
126.B \-dct int
127Use integer DCT method (default).
129.B \-dct fast
130Use fast integer DCT (less accurate).
132.B \-dct float
133Use floating-point DCT method.
134The float method is very slightly more accurate than the int method, but is
135much slower unless your machine has very fast floating-point hardware.  Also
136note that results of the floating-point method may vary slightly across
137machines, while the integer methods should give the same results everywhere.
138The fast integer method is much less accurate than the other two.
140.BI \-restart " N"
141Emit a JPEG restart marker every N MCU rows, or every N MCU blocks if "B" is
142attached to the number.
143.B \-restart 0
144(the default) means no restart markers.
146.BI \-smooth " N"
147Smooth the input image to eliminate dithering noise.  N, ranging from 1 to
148100, indicates the strength of smoothing.  0 (the default) means no smoothing.
150.BI \-maxmemory " N"
151Set limit for amount of memory to use in processing large images.  Value is
152in thousands of bytes, or millions of bytes if "M" is attached to the
153number.  For example,
154.B \-max 4m
155selects 4000000 bytes.  If more space is needed, temporary files will be used.
157.BI \-outfile " name"
158Send output image to the named file, not to standard output.
160.B \-verbose
161Enable debug printout.  More
162.BR \-v 's
163give more output.  Also, version information is printed at startup.
165.B \-debug
166Same as
167.BR \-verbose .
170.B \-restart
171option inserts extra markers that allow a JPEG decoder to resynchronize after
172a transmission error.  Without restart markers, any damage to a compressed
173file will usually ruin the image from the point of the error to the end of the
174image; with restart markers, the damage is usually confined to the portion of
175the image up to the next restart marker.  Of course, the restart markers
176occupy extra space.  We recommend
177.B \-restart 1
178for images that will be transmitted across unreliable networks such as Usenet.
181.B \-smooth
182option filters the input to eliminate fine-scale noise.  This is often useful
183when converting dithered images to JPEG: a moderate smoothing factor of 10 to
18450 gets rid of dithering patterns in the input file, resulting in a smaller
185JPEG file and a better-looking image.  Too large a smoothing factor will
186visibly blur the image, however.
188Switches for wizards:
190.B \-baseline
191Force baseline-compatible quantization tables to be generated.  This clamps
192quantization values to 8 bits even at low quality settings.  (This switch is
193poorly named, since it does not ensure that the output is actually baseline
194JPEG.  For example, you can use
195.B \-baseline
197.B \-progressive
200.BI \-qtables " file"
201Use the quantization tables given in the specified text file.
203.BI \-qslots " N[,...]"
204Select which quantization table to use for each color component.
206.BI \-sample " HxV[,...]"
207Set JPEG sampling factors for each color component.
209.BI \-scans " file"
210Use the scan script given in the specified text file.
212The "wizard" switches are intended for experimentation with JPEG.  If you
213don't know what you are doing, \fBdon't use them\fR.  These switches are
214documented further in the file wizard.doc.
217This example compresses the PPM file foo.ppm with a quality factor of
21860 and saves the output as foo.jpg:
220.B cjpeg \-quality
221.I 60 foo.ppm
222.B >
223.I foo.jpg
225Color GIF files are not the ideal input for JPEG; JPEG is really intended for
226compressing full-color (24-bit) images.  In particular, don't try to convert
227cartoons, line drawings, and other images that have only a few distinct
228colors.  GIF works great on these, JPEG does not.  If you want to convert a
229GIF to JPEG, you should experiment with
230.BR cjpeg 's
231.B \-quality
233.B \-smooth
234options to get a satisfactory conversion.
235.B \-smooth 10
236or so is often helpful.
238Avoid running an image through a series of JPEG compression/decompression
239cycles.  Image quality loss will accumulate; after ten or so cycles the image
240may be noticeably worse than it was after one cycle.  It's best to use a
241lossless format while manipulating an image, then convert to JPEG format when
242you are ready to file the image away.
245.B \-optimize
246option to
247.B cjpeg
248is worth using when you are making a "final" version for posting or archiving.
249It's also a win when you are using low quality settings to make very small
250JPEG files; the percentage improvement is often a lot more than it is on
251larger files.  (At present,
252.B \-optimize
253mode is always selected when generating progressive JPEG files.)
257If this environment variable is set, its value is the default memory limit.
258The value is specified as described for the
259.B \-maxmemory
262overrides the default value specified when the program was compiled, and
263itself is overridden by an explicit
264.BR \-maxmemory .
266.BR djpeg (1),
267.BR jpegtran (1),
268.BR rdjpgcom (1),
269.BR wrjpgcom (1)
271.BR ppm (5),
272.BR pgm (5)
274Wallace, Gregory K.  "The JPEG Still Picture Compression Standard",
275Communications of the ACM, April 1991 (vol. 34, no. 4), pp. 30-44.
277Independent JPEG Group
279Arithmetic coding is not supported for legal reasons.
281GIF input files are no longer supported, to avoid the Unisys LZW patent.
282Use a Unisys-licensed program if you need to read a GIF file.  (Conversion
283of GIF files to JPEG is usually a bad idea anyway.)
285Not all variants of BMP and Targa file formats are supported.
288.B \-targa
289switch is not a bug, it's a feature.  (It would be a bug if the Targa format
290designers had not been clueless.)
292Still not as fast as we'd like.
Note: See TracBrowser for help on using the repository browser.