Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 1 | USING THE IJG JPEG LIBRARY |
| 2 | |
Thomas G. Lane | a8b67c4 | 1995-03-15 00:00:00 +0000 | [diff] [blame^] | 3 | Copyright (C) 1994-1995, Thomas G. Lane. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 4 | This file is part of the Independent JPEG Group's software. |
| 5 | For conditions of distribution and use, see the accompanying README file. |
| 6 | |
| 7 | |
| 8 | This file describes how to use the IJG JPEG library within an application |
| 9 | program. Read it if you want to write a program that uses the library. |
| 10 | |
| 11 | The file example.c provides heavily commented skeleton code for calling the |
| 12 | JPEG library. Also see jpeglib.h (the include file to be used by application |
| 13 | programs) for full details about data structures and function parameter lists. |
| 14 | The library source code, of course, is the ultimate reference. |
| 15 | |
| 16 | Note that there have been *major* changes from the application interface |
| 17 | presented by IJG version 4 and earlier versions. The old design had several |
| 18 | inherent limitations, and it had accumulated a lot of cruft as we added |
| 19 | features while trying to minimize application-interface changes. We have |
| 20 | sacrificed backward compatibility in the version 5 rewrite, but we think the |
| 21 | improvements justify this. |
| 22 | |
| 23 | |
| 24 | TABLE OF CONTENTS |
| 25 | ----------------- |
| 26 | |
| 27 | Overview: |
| 28 | Functions provided by the library |
| 29 | Outline of typical usage |
| 30 | Basic library usage: |
| 31 | Data formats |
| 32 | Compression details |
| 33 | Decompression details |
| 34 | Mechanics of usage: include files, linking, etc |
| 35 | Advanced features: |
| 36 | Compression parameter selection |
| 37 | Decompression parameter selection |
| 38 | Special color spaces |
| 39 | Error handling |
| 40 | Compressed data handling (source and destination managers) |
| 41 | I/O suspension |
| 42 | Abbreviated datastreams and multiple images |
| 43 | Special markers |
| 44 | Raw (downsampled) image data |
| 45 | Progress monitoring |
| 46 | Memory management |
| 47 | Library compile-time options |
| 48 | Portability considerations |
| 49 | Notes for MS-DOS implementors |
| 50 | |
| 51 | You should read at least the overview and basic usage sections before trying |
| 52 | to program with the library. The sections on advanced features can be read |
| 53 | if and when you need them. |
| 54 | |
| 55 | |
| 56 | OVERVIEW |
| 57 | ======== |
| 58 | |
| 59 | Functions provided by the library |
| 60 | --------------------------------- |
| 61 | |
| 62 | The IJG JPEG library provides C code to read and write JPEG-compressed image |
| 63 | files. The surrounding application program receives or supplies image data a |
| 64 | scanline at a time, using a straightforward uncompressed image format. All |
| 65 | details of color conversion and other preprocessing/postprocessing can be |
| 66 | handled by the library. |
| 67 | |
| 68 | The library includes a substantial amount of code that is not covered by the |
| 69 | JPEG standard but is necessary for typical applications of JPEG. These |
| 70 | functions preprocess the image before JPEG compression or postprocess it after |
| 71 | decompression. They include colorspace conversion, downsampling/upsampling, |
| 72 | and color quantization. The application indirectly selects use of this code |
| 73 | by specifying the format in which it wishes to supply or receive image data. |
| 74 | For example, if colormapped output is requested, then the decompression |
| 75 | library automatically invokes color quantization. |
| 76 | |
| 77 | A wide range of quality vs. speed tradeoffs are possible in JPEG processing, |
| 78 | and even more so in decompression postprocessing. The decompression library |
| 79 | provides multiple implementations that cover most of the useful tradeoffs, |
| 80 | ranging from very-high-quality down to fast-preview operation. On the |
| 81 | compression side we have generally not provided low-quality choices, since |
| 82 | compression is normally less time-critical. It should be understood that the |
| 83 | low-quality modes may not meet the JPEG standard's accuracy requirements; |
| 84 | nonetheless, they are useful for viewers. |
| 85 | |
| 86 | A word about functions *not* provided by the library. We handle a subset of |
| 87 | the ISO JPEG standard; most baseline and extended-sequential JPEG processes |
| 88 | are supported. (Our subset includes all features now in common use.) |
| 89 | Unsupported ISO options include: |
| 90 | * Progressive storage (may be supported in future versions) |
| 91 | * Hierarchical storage |
| 92 | * Lossless JPEG |
| 93 | * Arithmetic entropy coding (unsupported for legal reasons) |
| 94 | * DNL marker |
| 95 | * Nonintegral subsampling ratios |
| 96 | We support both 8- and 12-bit data precision, but this is a compile-time |
| 97 | choice rather than a run-time choice; hence it is difficult to use both |
| 98 | precisions in a single application. |
| 99 | |
| 100 | By itself, the library handles only interchange JPEG datastreams --- in |
| 101 | particular the widely used JFIF file format. The library can be used by |
| 102 | surrounding code to process interchange or abbreviated JPEG datastreams that |
| 103 | are embedded in more complex file formats. (For example, we anticipate that |
| 104 | Sam Leffler's LIBTIFF library will use this code to support the revised TIFF |
| 105 | JPEG format.) |
| 106 | |
| 107 | |
| 108 | Outline of typical usage |
| 109 | ------------------------ |
| 110 | |
| 111 | The rough outline of a JPEG compression operation is: |
| 112 | |
| 113 | Allocate and initialize a JPEG compression object |
| 114 | Specify the destination for the compressed data (eg, a file) |
| 115 | Set parameters for compression, including image size & colorspace |
| 116 | jpeg_start_compress(...); |
| 117 | while (scan lines remain to be written) |
| 118 | jpeg_write_scanlines(...); |
| 119 | jpeg_finish_compress(...); |
| 120 | Release the JPEG compression object |
| 121 | |
| 122 | A JPEG compression object holds parameters and working state for the JPEG |
| 123 | library. We make creation/destruction of the object separate from starting |
| 124 | or finishing compression of an image; the same object can be re-used for a |
| 125 | series of image compression operations. This makes it easy to re-use the |
| 126 | same parameter settings for a sequence of images. Re-use of a JPEG object |
| 127 | also has important implications for processing abbreviated JPEG datastreams, |
| 128 | as discussed later. |
| 129 | |
| 130 | The image data to be compressed is supplied to jpeg_write_scanlines() from |
| 131 | in-memory buffers. If the application is doing file-to-file compression, |
| 132 | reading image data from the source file is the application's responsibility. |
| 133 | The library emits compressed data by calling a "data destination manager", |
| 134 | which typically will write the data into a file; but the application can |
| 135 | provide its own destination manager to do something else. |
| 136 | |
| 137 | Similarly, the rough outline of a JPEG decompression operation is: |
| 138 | |
| 139 | Allocate and initialize a JPEG decompression object |
| 140 | Specify the source of the compressed data (eg, a file) |
| 141 | Call jpeg_read_header() to obtain image info |
| 142 | Set parameters for decompression |
| 143 | jpeg_start_decompress(...); |
| 144 | while (scan lines remain to be read) |
| 145 | jpeg_read_scanlines(...); |
| 146 | jpeg_finish_decompress(...); |
| 147 | Release the JPEG decompression object |
| 148 | |
| 149 | This is comparable to the compression outline except that reading the |
| 150 | datastream header is a separate step. This is helpful because information |
| 151 | about the image's size, colorspace, etc is available when the application |
| 152 | selects decompression parameters. For example, the application can choose an |
| 153 | output scaling ratio that will fit the image into the available screen size. |
| 154 | |
| 155 | The decompression library obtains compressed data by calling a data source |
| 156 | manager, which typically will read the data from a file; but other behaviors |
| 157 | can be obtained with a custom source manager. Decompressed data is delivered |
| 158 | into in-memory buffers passed to jpeg_read_scanlines(). |
| 159 | |
| 160 | It is possible to abort an incomplete compression or decompression operation |
| 161 | by calling jpeg_abort(); or, if you do not need to retain the JPEG object, |
| 162 | simply release it by calling jpeg_destroy(). |
| 163 | |
| 164 | JPEG compression and decompression objects are two separate struct types. |
| 165 | However, they share some common fields, and certain routines such as |
| 166 | jpeg_destroy() can work on either type of object. |
| 167 | |
| 168 | The JPEG library has no static variables: all state is in the compression |
| 169 | or decompression object. Therefore it is possible to process multiple |
| 170 | compression and decompression operations concurrently, using multiple JPEG |
| 171 | objects. |
| 172 | |
| 173 | Both compression and decompression can be done in an incremental memory-to- |
| 174 | memory fashion, if suitable source/destination managers are used. However, |
| 175 | there are some restrictions on the processing that can be done in this mode. |
| 176 | See the section on "I/O suspension" for more details. |
| 177 | |
| 178 | |
| 179 | BASIC LIBRARY USAGE |
| 180 | =================== |
| 181 | |
| 182 | Data formats |
| 183 | ------------ |
| 184 | |
| 185 | Before diving into procedural details, it is helpful to understand the |
| 186 | image data format that the JPEG library expects or returns. |
| 187 | |
| 188 | The standard input image format is a rectangular array of pixels, with each |
| 189 | pixel having the same number of "component" values (color channels). You |
| 190 | must specify how many components there are and the colorspace interpretation |
| 191 | of the components. Most applications will use RGB data (three components |
Thomas G. Lane | a8b67c4 | 1995-03-15 00:00:00 +0000 | [diff] [blame^] | 192 | per pixel) or grayscale data (one component per pixel). PLEASE NOTE THAT |
| 193 | RGB DATA IS THREE SAMPLES PER PIXEL, GRAYSCALE ONLY ONE. A remarkable |
| 194 | number of people manage to miss this, only to find that their programs don't |
| 195 | work with grayscale JPEG files. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 196 | |
| 197 | Note that there is no provision for colormapped input. You can feed in a |
| 198 | colormapped image by expanding it to full-color format. However JPEG often |
| 199 | doesn't work very well with colormapped source data, because of dithering |
| 200 | noise. This is discussed in more detail in the JPEG FAQ and the other |
| 201 | references mentioned in the README file. |
| 202 | |
| 203 | Pixels are stored by scanlines, with each scanline running from left to |
| 204 | right. The component values for each pixel are adjacent in the row; for |
| 205 | example, R,G,B,R,G,B,R,G,B,... for 24-bit RGB color. Each scanline is an |
| 206 | array of data type JSAMPLE --- which is typically "unsigned char", unless |
| 207 | you've changed jmorecfg.h. (You can also change the RGB pixel layout, say |
| 208 | to B,G,R order, by modifying jmorecfg.h. But see the restrictions listed in |
| 209 | that file before doing so.) |
| 210 | |
| 211 | A 2-D array of pixels is formed by making a list of pointers to the starts of |
| 212 | scanlines; so the scanlines need not be physically adjacent in memory. Even |
| 213 | if you process just one scanline at a time, you must make a one-element |
| 214 | pointer array to serve this purpose. Pointers to JSAMPLE rows are of type |
| 215 | JSAMPROW, and the pointer to the pointer array is of type JSAMPARRAY. |
| 216 | |
| 217 | The library accepts or supplies one or more complete scanlines per call. |
| 218 | It is not possible to process part of a row at a time. Scanlines are always |
| 219 | processed top-to-bottom. You can process an entire image in one call if you |
| 220 | have it all in memory, but usually it's simplest to process one scanline at |
| 221 | a time. |
| 222 | |
| 223 | For best results, source data values should have the precision specified by |
| 224 | BITS_IN_JSAMPLE (normally 8 bits). For instance, if you choose to compress |
| 225 | data that's only 6 bits/channel, you should left-justify each value in a |
| 226 | byte before passing it to the compressor. If you need to compress data |
| 227 | that has more than 8 bits/channel, compile with BITS_IN_JSAMPLE = 12. |
| 228 | (See "Library compile-time options", later.) |
| 229 | |
| 230 | The data format returned by the decompressor is the same in all details, |
| 231 | except that colormapped data is supported. If you request colormapped |
| 232 | output then the returned data array contains a single JSAMPLE per pixel; |
| 233 | its value is an index into a color map. The color map is represented as |
| 234 | a 2-D JSAMPARRAY in which each row holds the values of one color component, |
| 235 | that is, colormap[i][j] is the value of the i'th color component for pixel |
| 236 | value (map index) j. Note that since the colormap indexes are stored in |
| 237 | JSAMPLEs, the maximum number of colors is limited by the size of JSAMPLE |
| 238 | (ie, at most 256 colors for an 8-bit JPEG library). |
| 239 | |
| 240 | |
| 241 | Compression details |
| 242 | ------------------- |
| 243 | |
| 244 | Here we revisit the JPEG compression outline given in the overview. |
| 245 | |
| 246 | 1. Allocate and initialize a JPEG compression object. |
| 247 | |
| 248 | A JPEG compression object is a "struct jpeg_compress_struct" (plus a bunch of |
| 249 | subsidiary structures which are allocated via malloc(), but the application |
| 250 | doesn't control those directly). This struct can be just a local variable in |
| 251 | the calling routine, if a single routine is going to execute the whole JPEG |
| 252 | compression sequence. Otherwise it can be static or allocated from malloc(). |
| 253 | |
| 254 | You will also need a structure representing a JPEG error handler. The part |
| 255 | of this that the library cares about is a "struct jpeg_error_mgr". If you |
| 256 | are providing your own error handler, you'll typically want to embed the |
| 257 | jpeg_error_mgr struct in a larger structure; this is discussed later under |
| 258 | "Error handling". For now we'll assume you are just using the default error |
| 259 | handler. The default error handler will print JPEG error/warning messages |
| 260 | on stderr, and it will call exit() if a fatal error occurs. |
| 261 | |
| 262 | You must initialize the error handler structure, store a pointer to it into |
| 263 | the JPEG object's "err" field, and then call jpeg_create_compress() to |
| 264 | initialize the rest of the JPEG object. |
| 265 | |
| 266 | Typical code for this step, if you are using the default error handler, is |
| 267 | |
| 268 | struct jpeg_compress_struct cinfo; |
| 269 | struct jpeg_error_mgr jerr; |
| 270 | ... |
| 271 | cinfo.err = jpeg_std_error(&jerr); |
| 272 | jpeg_create_compress(&cinfo); |
| 273 | |
| 274 | jpeg_create_compress allocates a small amount of memory, so it could fail |
| 275 | if you are out of memory. In that case it will exit via the error handler; |
| 276 | that's why the error handler must be initialized first. |
| 277 | |
| 278 | |
| 279 | 2. Specify the destination for the compressed data (eg, a file). |
| 280 | |
| 281 | As previously mentioned, the JPEG library delivers compressed data to a |
| 282 | "data destination" module. The library includes one data destination |
| 283 | module which knows how to write to a stdio stream. You can use your own |
| 284 | destination module if you want to do something else, as discussed later. |
| 285 | |
| 286 | If you use the standard destination module, you must open the target stdio |
| 287 | stream beforehand. Typical code for this step looks like: |
| 288 | |
| 289 | FILE * outfile; |
| 290 | ... |
| 291 | if ((outfile = fopen(filename, "wb")) == NULL) { |
| 292 | fprintf(stderr, "can't open %s\n", filename); |
| 293 | exit(1); |
| 294 | } |
| 295 | jpeg_stdio_dest(&cinfo, outfile); |
| 296 | |
| 297 | where the last line invokes the standard destination module. |
| 298 | |
| 299 | WARNING: it is critical that the binary compressed data be delivered to the |
| 300 | output file unchanged. On non-Unix systems the stdio library may perform |
| 301 | newline translation or otherwise corrupt binary data. To suppress this |
| 302 | behavior, you may need to use a "b" option to fopen (as shown above), or use |
| 303 | setmode() or another routine to put the stdio stream in binary mode. See |
| 304 | cjpeg.c and djpeg.c for code that has been found to work on many systems. |
| 305 | |
| 306 | You can select the data destination after setting other parameters (step 3), |
| 307 | if that's more convenient. You may not change the destination between |
| 308 | calling jpeg_start_compress() and jpeg_finish_compress(). |
| 309 | |
| 310 | |
| 311 | 3. Set parameters for compression, including image size & colorspace. |
| 312 | |
| 313 | You must supply information about the source image by setting the following |
| 314 | fields in the JPEG object (cinfo structure): |
| 315 | |
| 316 | image_width Width of image, in pixels |
| 317 | image_height Height of image, in pixels |
| 318 | input_components Number of color channels (samples per pixel) |
| 319 | in_color_space Color space of source image |
| 320 | |
| 321 | The image dimensions are, hopefully, obvious. JPEG supports image dimensions |
| 322 | of 1 to 64K pixels in either direction. The input color space is typically |
| 323 | RGB or grayscale, and input_components is 3 or 1 accordingly. (See "Special |
| 324 | color spaces", later, for more info.) The in_color_space field must be |
| 325 | assigned one of the J_COLOR_SPACE enum constants, typically JCS_RGB or |
| 326 | JCS_GRAYSCALE. |
| 327 | |
| 328 | JPEG has a large number of compression parameters that determine how the |
| 329 | image is encoded. Most applications don't need or want to know about all |
| 330 | these parameters. You can set all the parameters to reasonable defaults by |
| 331 | calling jpeg_set_defaults(); then, if there are particular values you want |
| 332 | to change, you can do so after that. The "Compression parameter selection" |
| 333 | section tells about all the parameters. |
| 334 | |
| 335 | You must set in_color_space correctly before calling jpeg_set_defaults(), |
| 336 | because the defaults depend on the source image colorspace. However the |
| 337 | other three source image parameters need not be valid until you call |
| 338 | jpeg_start_compress(). There's no harm in calling jpeg_set_defaults() more |
| 339 | than once, if that happens to be convenient. |
| 340 | |
| 341 | Typical code for a 24-bit RGB source image is |
| 342 | |
| 343 | cinfo.image_width = Width; /* image width and height, in pixels */ |
| 344 | cinfo.image_height = Height; |
| 345 | cinfo.input_components = 3; /* # of color components per pixel */ |
| 346 | cinfo.in_color_space = JCS_RGB; /* colorspace of input image */ |
| 347 | |
| 348 | jpeg_set_defaults(&cinfo); |
| 349 | /* Make optional parameter settings here */ |
| 350 | |
| 351 | |
| 352 | 4. jpeg_start_compress(...); |
| 353 | |
| 354 | After you have established the data destination and set all the necessary |
| 355 | source image info and other parameters, call jpeg_start_compress() to begin |
| 356 | a compression cycle. This will initialize internal state, allocate working |
| 357 | storage, and emit the first few bytes of the JPEG datastream header. |
| 358 | |
| 359 | Typical code: |
| 360 | |
| 361 | jpeg_start_compress(&cinfo, TRUE); |
| 362 | |
| 363 | The "TRUE" parameter ensures that a complete JPEG interchange datastream |
| 364 | will be written. This is appropriate in most cases. If you think you might |
| 365 | want to use an abbreviated datastream, read the section on abbreviated |
| 366 | datastreams, below. |
| 367 | |
| 368 | Once you have called jpeg_start_compress(), you may not alter any JPEG |
| 369 | parameters or other fields of the JPEG object until you have completed |
| 370 | the compression cycle. |
| 371 | |
| 372 | |
| 373 | 5. while (scan lines remain to be written) |
| 374 | jpeg_write_scanlines(...); |
| 375 | |
| 376 | Now write all the required image data by calling jpeg_write_scanlines() |
| 377 | one or more times. You can pass one or more scanlines in each call, up |
| 378 | to the total image height. In most applications it is convenient to pass |
| 379 | just one or a few scanlines at a time. The expected format for the passed |
| 380 | data is discussed under "Data formats", above. |
| 381 | |
| 382 | Image data should be written in top-to-bottom scanline order. The JPEG spec |
| 383 | contains some weasel wording about how top and bottom are application-defined |
| 384 | terms (a curious interpretation of the English language...) but if you want |
| 385 | your files to be compatible with everyone else's, you WILL use top-to-bottom |
| 386 | order. If the source data must be read in bottom-to-top order, you can use |
| 387 | the JPEG library's virtual array mechanism to invert the data efficiently. |
| 388 | Examples of this can be found in the sample application cjpeg. |
| 389 | |
| 390 | The library maintains a count of the number of scanlines written so far |
| 391 | in the next_scanline field of the JPEG object. Usually you can just use |
| 392 | this variable as the loop counter, so that the loop test looks like |
| 393 | "while (cinfo.next_scanline < cinfo.image_height)". |
| 394 | |
| 395 | Code for this step depends heavily on the way that you store the source data. |
| 396 | example.c shows the following code for the case of a full-size 2-D source |
| 397 | array containing 3-byte RGB pixels: |
| 398 | |
| 399 | JSAMPROW row_pointer[1]; /* pointer to a single row */ |
| 400 | int row_stride; /* physical row width in buffer */ |
| 401 | |
| 402 | row_stride = image_width * 3; /* JSAMPLEs per row in image_buffer */ |
| 403 | |
| 404 | while (cinfo.next_scanline < cinfo.image_height) { |
| 405 | row_pointer[0] = & image_buffer[cinfo.next_scanline * row_stride]; |
| 406 | jpeg_write_scanlines(&cinfo, row_pointer, 1); |
| 407 | } |
| 408 | |
| 409 | jpeg_write_scanlines() returns the number of scanlines actually written. |
| 410 | This will normally be equal to the number passed in, so you can usually |
| 411 | ignore the return value. It is different in just two cases: |
| 412 | * If you try to write more scanlines than the declared image height, |
| 413 | the additional scanlines are ignored. |
| 414 | * If you use a suspending data destination manager, output buffer overrun |
| 415 | will cause the compressor to return before accepting all the passed lines. |
| 416 | This feature is discussed under "I/O suspension", below. The normal |
| 417 | stdio destination manager will NOT cause this to happen. |
| 418 | In any case, the return value is the same as the change in the value of |
| 419 | next_scanline. |
| 420 | |
| 421 | |
| 422 | 6. jpeg_finish_compress(...); |
| 423 | |
| 424 | After all the image data has been written, call jpeg_finish_compress() to |
| 425 | complete the compression cycle. This step is ESSENTIAL to ensure that the |
| 426 | last bufferload of data is written to the data destination. |
| 427 | jpeg_finish_compress() also releases working memory associated with the JPEG |
| 428 | object. |
| 429 | |
| 430 | Typical code: |
| 431 | |
| 432 | jpeg_finish_compress(&cinfo); |
| 433 | |
| 434 | If using the stdio destination manager, don't forget to close the output |
| 435 | stdio stream if necessary. |
| 436 | |
| 437 | If you have requested a multi-pass operating mode, such as Huffman code |
| 438 | optimization, jpeg_finish_compress() will perform the additional passes using |
| 439 | data buffered by the first pass. In this case jpeg_finish_compress() may take |
| 440 | quite a while to complete. With the default compression parameters, this will |
| 441 | not happen. |
| 442 | |
| 443 | It is an error to call jpeg_finish_compress() before writing the necessary |
| 444 | total number of scanlines. If you wish to abort compression, call |
| 445 | jpeg_abort() as discussed below. |
| 446 | |
| 447 | After completing a compression cycle, you may dispose of the JPEG object |
| 448 | as discussed next, or you may use it to compress another image. In that case |
| 449 | return to step 2, 3, or 4 as appropriate. If you do not change the |
| 450 | destination manager, the new datastream will be written to the same target. |
| 451 | If you do not change any JPEG parameters, the new datastream will be written |
| 452 | with the same parameters as before. Note that you can change the input image |
| 453 | dimensions freely between cycles, but if you change the input colorspace, you |
| 454 | should call jpeg_set_defaults() to adjust for the new colorspace; and then |
| 455 | you'll need to repeat all of step 3. |
| 456 | |
| 457 | |
| 458 | 7. Release the JPEG compression object. |
| 459 | |
| 460 | When you are done with a JPEG compression object, destroy it by calling |
| 461 | jpeg_destroy_compress(). This will free all subsidiary memory. Or you can |
| 462 | call jpeg_destroy() which works for either compression or decompression |
| 463 | objects --- this may be more convenient if you are sharing code between |
| 464 | compression and decompression cases. (Actually, these routines are equivalent |
| 465 | except for the declared type of the passed pointer. To avoid gripes from |
| 466 | ANSI C compilers, pass a j_common_ptr to jpeg_destroy().) |
| 467 | |
| 468 | If you allocated the jpeg_compress_struct structure from malloc(), freeing |
| 469 | it is your responsibility --- jpeg_destroy() won't. Ditto for the error |
| 470 | handler structure. |
| 471 | |
| 472 | Typical code: |
| 473 | |
| 474 | jpeg_destroy_compress(&cinfo); |
| 475 | |
| 476 | |
| 477 | 8. Aborting. |
| 478 | |
| 479 | If you decide to abort a compression cycle before finishing, you can clean up |
| 480 | in either of two ways: |
| 481 | |
| 482 | * If you don't need the JPEG object any more, just call |
| 483 | jpeg_destroy_compress() or jpeg_destroy() to release memory. This is |
| 484 | legitimate at any point after calling jpeg_create_compress() --- in fact, |
| 485 | it's safe even if jpeg_create_compress() fails. |
| 486 | |
| 487 | * If you want to re-use the JPEG object, call jpeg_abort_compress(), or |
| 488 | jpeg_abort() which works on both compression and decompression objects. |
| 489 | This will return the object to an idle state, releasing any working memory. |
| 490 | jpeg_abort() is allowed at any time after successful object creation. |
| 491 | |
| 492 | Note that cleaning up the data destination, if required, is your |
| 493 | responsibility. |
| 494 | |
| 495 | |
| 496 | Decompression details |
| 497 | --------------------- |
| 498 | |
| 499 | Here we revisit the JPEG decompression outline given in the overview. |
| 500 | |
| 501 | 1. Allocate and initialize a JPEG decompression object. |
| 502 | |
| 503 | This is just like initialization for compression, as discussed above, |
| 504 | except that the object is a "struct jpeg_decompress_struct" and you |
| 505 | call jpeg_create_decompress(). Error handling is exactly the same. |
| 506 | |
| 507 | Typical code: |
| 508 | |
| 509 | struct jpeg_decompress_struct cinfo; |
| 510 | struct jpeg_error_mgr jerr; |
| 511 | ... |
| 512 | cinfo.err = jpeg_std_error(&jerr); |
| 513 | jpeg_create_decompress(&cinfo); |
| 514 | |
| 515 | (Both here and in the IJG code, we usually use variable name "cinfo" for |
| 516 | both compression and decompression objects.) |
| 517 | |
| 518 | |
| 519 | 2. Specify the source of the compressed data (eg, a file). |
| 520 | |
| 521 | As previously mentioned, the JPEG library reads compressed data from a "data |
| 522 | source" module. The library includes one data source module which knows how |
| 523 | to read from a stdio stream. You can use your own source module if you want |
| 524 | to do something else, as discussed later. |
| 525 | |
| 526 | If you use the standard source module, you must open the source stdio stream |
| 527 | beforehand. Typical code for this step looks like: |
| 528 | |
| 529 | FILE * infile; |
| 530 | ... |
| 531 | if ((infile = fopen(filename, "rb")) == NULL) { |
| 532 | fprintf(stderr, "can't open %s\n", filename); |
| 533 | exit(1); |
| 534 | } |
| 535 | jpeg_stdio_src(&cinfo, infile); |
| 536 | |
| 537 | where the last line invokes the standard source module. |
| 538 | |
| 539 | WARNING: it is critical that the binary compressed data be read unchanged. |
| 540 | On non-Unix systems the stdio library may perform newline translation or |
| 541 | otherwise corrupt binary data. To suppress this behavior, you may need to use |
| 542 | a "b" option to fopen (as shown above), or use setmode() or another routine to |
| 543 | put the stdio stream in binary mode. See cjpeg.c and djpeg.c for code that |
| 544 | has been found to work on many systems. |
| 545 | |
| 546 | You may not change the data source between calling jpeg_read_header() and |
| 547 | jpeg_finish_decompress(). If you wish to read a series of JPEG images from |
| 548 | a single source file, you should repeat the jpeg_read_header() to |
| 549 | jpeg_finish_decompress() sequence without reinitializing either the JPEG |
| 550 | object or the data source module; this prevents buffered input data from |
| 551 | being discarded. |
| 552 | |
| 553 | |
| 554 | 3. Call jpeg_read_header() to obtain image info. |
| 555 | |
| 556 | Typical code for this step is just |
| 557 | |
| 558 | jpeg_read_header(&cinfo, TRUE); |
| 559 | |
| 560 | This will read the source datastream header markers, up to the beginning |
| 561 | of the compressed data proper. On return, the image dimensions and other |
| 562 | info have been stored in the JPEG object. The application may wish to |
| 563 | consult this information before selecting decompression parameters. |
| 564 | |
| 565 | More complex code is necessary if |
| 566 | * A suspending data source is used --- in that case jpeg_read_header() |
| 567 | may return before it has read all the header data. See "I/O suspension", |
| 568 | below. The normal stdio source manager will NOT cause this to happen. |
| 569 | * Abbreviated JPEG files are to be processed --- see the section on |
| 570 | abbreviated datastreams. Standard applications that deal only in |
| 571 | interchange JPEG files need not be concerned with this case either. |
| 572 | |
| 573 | It is permissible to stop at this point if you just wanted to find out the |
| 574 | image dimensions and other header info for a JPEG file. In that case, |
| 575 | call jpeg_destroy() when you are done with the JPEG object, or call |
| 576 | jpeg_abort() to return it to an idle state before selecting a new data |
| 577 | source and reading another header. |
| 578 | |
| 579 | |
| 580 | 4. Set parameters for decompression. |
| 581 | |
| 582 | jpeg_read_header() sets appropriate default decompression parameters based on |
| 583 | the properties of the image (in particular, its colorspace). However, you |
| 584 | may well want to alter these defaults before beginning the decompression. |
| 585 | For example, the default is to produce full color output from a color file. |
| 586 | If you want colormapped output you must ask for it. Other options allow the |
| 587 | returned image to be scaled and allow various speed/quality tradeoffs to be |
| 588 | selected. "Decompression parameter selection", below, gives details. |
| 589 | |
| 590 | If the defaults are appropriate, nothing need be done at this step. |
| 591 | |
| 592 | Note that all default values are set by each call to jpeg_read_header(). |
| 593 | If you reuse a decompression object, you cannot expect your parameter |
| 594 | settings to be preserved across cycles, as you can for compression. |
| 595 | You must adjust parameter values each time. |
| 596 | |
| 597 | |
| 598 | 5. jpeg_start_decompress(...); |
| 599 | |
| 600 | Once the parameter values are satisfactory, call jpeg_start_decompress() to |
| 601 | begin decompression. This will initialize internal state, allocate working |
| 602 | memory, and prepare for returning data. |
| 603 | |
| 604 | Typical code is just |
| 605 | |
| 606 | jpeg_start_decompress(&cinfo); |
| 607 | |
| 608 | If you have requested a multi-pass operating mode, such as 2-pass color |
| 609 | quantization, jpeg_start_decompress() will do everything needed before data |
| 610 | output can begin. In this case jpeg_start_decompress() may take quite a while |
| 611 | to complete. With a single-scan (fully interleaved) JPEG file and default |
| 612 | decompression parameters, this will not happen; jpeg_start_decompress() will |
| 613 | return quickly. |
| 614 | |
| 615 | After this call, the final output image dimensions, including any requested |
| 616 | scaling, are available in the JPEG object; so is the selected colormap, if |
| 617 | colormapped output has been requested. Useful fields include |
| 618 | |
| 619 | output_width image width and height, as scaled |
| 620 | output_height |
| 621 | out_color_components # of color components in out_color_space |
| 622 | output_components # of color components returned per pixel |
| 623 | colormap the selected colormap, if any |
| 624 | actual_number_of_colors number of entries in colormap |
| 625 | |
| 626 | output_components is 1 (a colormap index) when quantizing colors; otherwise it |
| 627 | equals out_color_components. It is the number of JSAMPLE values that will be |
| 628 | emitted per pixel in the output arrays. |
| 629 | |
| 630 | Typically you will need to allocate data buffers to hold the incoming image. |
| 631 | You will need output_width * output_components JSAMPLEs per scanline in your |
| 632 | output buffer, and a total of output_height scanlines will be returned. |
| 633 | |
| 634 | Note: if you are using the JPEG library's internal memory manager to allocate |
| 635 | data buffers (as djpeg does), then the manager's protocol requires that you |
| 636 | request large buffers *before* calling jpeg_start_decompress(). This is a |
| 637 | little tricky since the output_XXX fields are not normally valid then. You |
| 638 | can make them valid by calling jpeg_calc_output_dimensions() after setting the |
| 639 | relevant parameters (scaling, output color space, and quantization flag). |
| 640 | |
| 641 | |
| 642 | 6. while (scan lines remain to be read) |
| 643 | jpeg_read_scanlines(...); |
| 644 | |
| 645 | Now you can read the decompressed image data by calling jpeg_read_scanlines() |
| 646 | one or more times. At each call, you pass in the maximum number of scanlines |
| 647 | to be read (ie, the height of your working buffer); jpeg_read_scanlines() |
| 648 | will return up to that many lines. The return value is the number of lines |
| 649 | actually read. The format of the returned data is discussed under "Data |
Thomas G. Lane | a8b67c4 | 1995-03-15 00:00:00 +0000 | [diff] [blame^] | 650 | formats", above. Don't forget that grayscale and color JPEGs will return |
| 651 | different data formats! |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 652 | |
| 653 | Image data is returned in top-to-bottom scanline order. If you must write |
| 654 | out the image in bottom-to-top order, you can use the JPEG library's virtual |
| 655 | array mechanism to invert the data efficiently. Examples of this can be |
| 656 | found in the sample application djpeg. |
| 657 | |
| 658 | The library maintains a count of the number of scanlines returned so far |
| 659 | in the output_scanline field of the JPEG object. Usually you can just use |
| 660 | this variable as the loop counter, so that the loop test looks like |
| 661 | "while (cinfo.output_scanline < cinfo.output_height)". (Note that the test |
| 662 | should NOT be against image_height, unless you never use scaling. The |
| 663 | image_height field is the height of the original unscaled image.) |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 664 | The return value always equals the change in the value of output_scanline. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 665 | |
| 666 | If you don't use a suspending data source, it is safe to assume that |
| 667 | jpeg_read_scanlines() reads at least one scanline per call, until the |
| 668 | bottom of the image has been reached. If you use a buffer larger than one |
| 669 | scanline, it is NOT safe to assume that jpeg_read_scanlines() fills it. |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 670 | (The current implementation won't return more than cinfo.rec_outbuf_height |
| 671 | scanlines per call, no matter how large a buffer you pass.) So you must |
| 672 | always provide a loop that calls jpeg_read_scanlines() repeatedly until |
| 673 | the whole image has been read. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 674 | |
| 675 | |
| 676 | 7. jpeg_finish_decompress(...); |
| 677 | |
| 678 | After all the image data has been read, call jpeg_finish_decompress() to |
| 679 | complete the decompression cycle. This causes working memory associated |
| 680 | with the JPEG object to be released. |
| 681 | |
| 682 | Typical code: |
| 683 | |
| 684 | jpeg_finish_decompress(&cinfo); |
| 685 | |
| 686 | If using the stdio source manager, don't forget to close the source stdio |
| 687 | stream if necessary. |
| 688 | |
| 689 | It is an error to call jpeg_finish_decompress() before reading the correct |
| 690 | total number of scanlines. If you wish to abort compression, call |
| 691 | jpeg_abort() as discussed below. |
| 692 | |
| 693 | After completing a decompression cycle, you may dispose of the JPEG object as |
| 694 | discussed next, or you may use it to decompress another image. In that case |
| 695 | return to step 2 or 3 as appropriate. If you do not change the source |
| 696 | manager, the next image will be read from the same source. |
| 697 | |
| 698 | |
| 699 | 8. Release the JPEG decompression object. |
| 700 | |
| 701 | When you are done with a JPEG decompression object, destroy it by calling |
| 702 | jpeg_destroy_decompress() or jpeg_destroy(). The previous discussion of |
| 703 | destroying compression objects applies here too. |
| 704 | |
| 705 | Typical code: |
| 706 | |
| 707 | jpeg_destroy_decompress(&cinfo); |
| 708 | |
| 709 | |
| 710 | 9. Aborting. |
| 711 | |
| 712 | You can abort a decompression cycle by calling jpeg_destroy_decompress() or |
| 713 | jpeg_destroy() if you don't need the JPEG object any more, or |
| 714 | jpeg_abort_decompress() or jpeg_abort() if you want to reuse the object. |
| 715 | The previous discussion of aborting compression cycles applies here too. |
| 716 | |
| 717 | |
| 718 | Mechanics of usage: include files, linking, etc |
| 719 | ----------------------------------------------- |
| 720 | |
| 721 | Applications using the JPEG library should include the header file jpeglib.h |
| 722 | to obtain declarations of data types and routines. Before including |
| 723 | jpeglib.h, include system headers that define at least the typedefs FILE and |
| 724 | size_t. On ANSI-conforming systems, including <stdio.h> is sufficient; on |
| 725 | older Unix systems, you may need <sys/types.h> to define size_t. |
| 726 | |
| 727 | If the application needs to refer to individual JPEG library error codes, also |
| 728 | include jerror.h to define those symbols. |
| 729 | |
| 730 | jpeglib.h indirectly includes the files jconfig.h and jmorecfg.h. If you are |
| 731 | installing the JPEG header files in a system directory, you will want to |
| 732 | install all four files: jpeglib.h, jerror.h, jconfig.h, jmorecfg.h. |
| 733 | |
| 734 | The most convenient way to include the JPEG code into your executable program |
| 735 | is to prepare a library file ("libjpeg.a", or a corresponding name on non-Unix |
| 736 | machines) and reference it at your link step. If you use only half of the |
| 737 | library (only compression or only decompression), only that much code will be |
| 738 | included from the library, unless your linker is hopelessly brain-damaged. |
| 739 | The supplied makefiles build libjpeg.a automatically (see install.doc). |
| 740 | |
| 741 | On some systems your application may need to set up a signal handler to ensure |
| 742 | that temporary files are deleted if the program is interrupted. This is most |
| 743 | critical if you are on MS-DOS and use the jmemdos.c memory manager back end; |
| 744 | it will try to grab extended memory for temp files, and that space will NOT be |
| 745 | freed automatically. See cjpeg.c or djpeg.c for an example signal handler. |
| 746 | |
| 747 | It may be worth pointing out that the core JPEG library does not actually |
| 748 | require the stdio library: only the default source/destination managers and |
| 749 | error handler need it. You can use the library in a stdio-less environment |
| 750 | if you replace those modules and use jmemnobs.c (or another memory manager of |
| 751 | your own devising). More info about the minimum system library requirements |
| 752 | may be found in jinclude.h. |
| 753 | |
| 754 | |
| 755 | ADVANCED FEATURES |
| 756 | ================= |
| 757 | |
| 758 | Compression parameter selection |
| 759 | ------------------------------- |
| 760 | |
| 761 | This section describes all the optional parameters you can set for JPEG |
| 762 | compression, as well as the "helper" routines provided to assist in this |
| 763 | task. Proper setting of some parameters requires detailed understanding |
| 764 | of the JPEG standard; if you don't know what a parameter is for, it's best |
| 765 | not to mess with it! See REFERENCES in the README file for pointers to |
| 766 | more info about JPEG. |
| 767 | |
| 768 | It's a good idea to call jpeg_set_defaults() first, even if you plan to set |
| 769 | all the parameters; that way your code is more likely to work with future JPEG |
| 770 | libraries that have additional parameters. For the same reason, we recommend |
| 771 | you use a helper routine where one is provided, in preference to twiddling |
| 772 | cinfo fields directly. |
| 773 | |
| 774 | The helper routines are: |
| 775 | |
| 776 | jpeg_set_defaults (j_compress_ptr cinfo) |
| 777 | This routine sets all JPEG parameters to reasonable defaults, using |
| 778 | only the input image's color space (field in_color_space, which must |
| 779 | already be set in cinfo). Many applications will only need to use |
| 780 | this routine and perhaps jpeg_set_quality(). |
| 781 | |
| 782 | jpeg_set_colorspace (j_compress_ptr cinfo, J_COLOR_SPACE colorspace) |
| 783 | Sets the JPEG file's colorspace (field jpeg_color_space) as specified, |
| 784 | and sets other color-space-dependent parameters appropriately. See |
| 785 | "Special color spaces", below, before using this. A large number of |
| 786 | parameters, including all per-component parameters, are set by this |
| 787 | routine; if you want to twiddle individual parameters you should call |
| 788 | jpeg_set_colorspace() before rather than after. |
| 789 | |
| 790 | jpeg_default_colorspace (j_compress_ptr cinfo) |
| 791 | Selects an appropriate JPEG colorspace based on cinfo->in_color_space, |
| 792 | and calls jpeg_set_colorspace(). This is actually a subroutine of |
| 793 | jpeg_set_defaults(). It's broken out in case you want to change |
| 794 | just the colorspace-dependent JPEG parameters. |
| 795 | |
| 796 | jpeg_set_quality (j_compress_ptr cinfo, int quality, boolean force_baseline) |
| 797 | Constructs JPEG quantization tables appropriate for the indicated |
| 798 | quality setting. The quality value is expressed on the 0..100 scale |
| 799 | recommended by IJG (cjpeg's "-quality" switch uses this routine). |
| 800 | Note that the exact mapping from quality values to tables may change |
| 801 | in future IJG releases as more is learned about DCT quantization. |
| 802 | If the force_baseline parameter is TRUE, then the quantization table |
| 803 | entries are constrained to the range 1..255 for full JPEG baseline |
| 804 | compatibility. In the current implementation, this only makes a |
| 805 | difference for quality settings below 25, and it effectively prevents |
| 806 | very small/low quality files from being generated. The IJG decoder |
| 807 | is capable of reading the non-baseline files generated at low quality |
| 808 | settings when force_baseline is FALSE, but other decoders may not be. |
| 809 | |
| 810 | jpeg_set_linear_quality (j_compress_ptr cinfo, int scale_factor, |
| 811 | boolean force_baseline) |
| 812 | Same as jpeg_set_quality() except that the generated tables are the |
| 813 | sample tables given in the JPEC spec section K.1, multiplied by the |
| 814 | specified scale factor (which is expressed as a percentage; thus |
| 815 | scale_factor = 100 reproduces the spec's tables). Note that larger |
| 816 | scale factors give lower quality. This entry point is useful for |
| 817 | conforming to the Adobe PostScript DCT conventions, but we do not |
| 818 | recommend linear scaling as a user-visible quality scale otherwise. |
| 819 | force_baseline again constrains the computed table entries to 1..255. |
| 820 | |
| 821 | int jpeg_quality_scaling (int quality) |
| 822 | Converts a value on the IJG-recommended quality scale to a linear |
| 823 | scaling percentage. Note that this routine may change or go away |
| 824 | in future releases --- IJG may choose to adopt a scaling method that |
| 825 | can't be expressed as a simple scalar multiplier, in which case the |
| 826 | premise of this routine collapses. Caveat user. |
| 827 | |
| 828 | jpeg_add_quant_table (j_compress_ptr cinfo, int which_tbl, |
| 829 | const unsigned int *basic_table, |
| 830 | int scale_factor, boolean force_baseline)); |
| 831 | Allows an arbitrary quantization table to be created. which_tbl |
| 832 | indicates which table slot to fill. basic_table points to an array |
| 833 | of 64 unsigned ints given in JPEG zigzag order. These values are |
| 834 | multiplied by scale_factor/100 and then clamped to the range 1..65535 |
| 835 | (or to 1..255 if force_baseline is TRUE). |
| 836 | |
| 837 | |
| 838 | Compression parameters (cinfo fields) include: |
| 839 | |
| 840 | boolean optimize_coding |
| 841 | TRUE causes the compressor to compute optimal Huffman coding tables |
| 842 | for the image. This requires an extra pass over the data and |
| 843 | therefore costs a good deal of space and time. The default is |
| 844 | FALSE, which tells the compressor to use the supplied or default |
| 845 | Huffman tables. In most cases optimal tables save only a few percent |
| 846 | of file size compared to the default tables. Note that when this is |
| 847 | TRUE, you need not supply Huffman tables at all, and any you do |
| 848 | supply will be overwritten. |
| 849 | |
| 850 | int smoothing_factor |
| 851 | If non-zero, the input image is smoothed; the value should be 1 for |
| 852 | minimal smoothing to 100 for maximum smoothing. Consult jcsample.c |
| 853 | for details of the smoothing algorithm. The default is zero. |
| 854 | |
| 855 | J_DCT_METHOD dct_method |
| 856 | Selects the algorithm used for the DCT step. Choices are: |
| 857 | JDCT_ISLOW: slow but accurate integer algorithm |
| 858 | JDCT_IFAST: faster, less accurate integer method |
| 859 | JDCT_FLOAT: floating-point method |
| 860 | JDCT_DEFAULT: default method (normally JDCT_ISLOW) |
| 861 | JDCT_FASTEST: fastest method (normally JDCT_IFAST) |
Thomas G. Lane | a8b67c4 | 1995-03-15 00:00:00 +0000 | [diff] [blame^] | 862 | The FLOAT method is very slightly more accurate than the ISLOW method, |
| 863 | but may give different results on different machines due to varying |
| 864 | roundoff behavior. The integer methods should give the same results |
| 865 | on all machines. On machines with sufficiently fast FP hardware, the |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 866 | floating-point method may also be the fastest. The IFAST method is |
| 867 | considerably less accurate than the other two; its use is not |
| 868 | recommended if high quality is a concern. JDCT_DEFAULT and |
| 869 | JDCT_FASTEST are macros configurable by each installation. |
| 870 | |
| 871 | unsigned int restart_interval |
| 872 | int restart_in_rows |
| 873 | To emit restart markers in the JPEG file, set one of these nonzero. |
| 874 | Set restart_interval to specify the exact interval in MCU blocks. |
| 875 | Set restart_in_rows to specify the interval in MCU rows. (If |
| 876 | restart_in_rows is not 0, then restart_interval is set after the |
| 877 | image width in MCUs is computed.) Defaults are zero (no restarts). |
| 878 | |
| 879 | J_COLOR_SPACE jpeg_color_space |
| 880 | int num_components |
| 881 | The JPEG color space and corresponding number of components; see |
| 882 | "Special color spaces", below, for more info. We recommend using |
| 883 | jpeg_set_color_space() if you want to change these. |
| 884 | |
| 885 | boolean write_JFIF_header |
| 886 | If TRUE, a JFIF APP0 marker is emitted. jpeg_set_defaults() and |
| 887 | jpeg_set_colorspace() set this TRUE if a JFIF-legal JPEG color space |
| 888 | (ie, YCbCr or grayscale) is selected, otherwise FALSE. |
| 889 | |
| 890 | UINT8 density_unit |
| 891 | UINT16 X_density |
| 892 | UINT16 Y_density |
| 893 | The resolution information to be written into the JFIF marker; |
| 894 | not used otherwise. density_unit may be 0 for unknown, |
| 895 | 1 for dots/inch, or 2 for dots/cm. The default values are 0,1,1 |
| 896 | indicating square pixels of unknown size. |
| 897 | |
| 898 | boolean write_Adobe_marker |
| 899 | If TRUE, an Adobe APP14 marker is emitted. jpeg_set_defaults() and |
| 900 | jpeg_set_colorspace() set this TRUE if JPEG color space RGB, CMYK, |
| 901 | or YCCK is selected, otherwise FALSE. It is generally a bad idea |
| 902 | to set both write_JFIF_header and write_Adobe_marker. In fact, |
| 903 | you probably shouldn't change the default settings at all --- the |
| 904 | default behavior ensures that the JPEG file's color space can be |
| 905 | recognized by the decoder. |
| 906 | |
| 907 | JQUANT_TBL * quant_tbl_ptrs[NUM_QUANT_TBLS] |
| 908 | Pointers to coefficient quantization tables, one per table slot, |
| 909 | or NULL if no table is defined for a slot. Usually these should |
| 910 | be set via one of the above helper routines; jpeg_add_quant_table() |
| 911 | is general enough to define any quantization table. The other |
| 912 | routines will set up table slot 0 for luminance quality and table |
| 913 | slot 1 for chrominance. |
| 914 | |
| 915 | JHUFF_TBL * dc_huff_tbl_ptrs[NUM_HUFF_TBLS] |
| 916 | JHUFF_TBL * ac_huff_tbl_ptrs[NUM_HUFF_TBLS] |
| 917 | Pointers to Huffman coding tables, one per table slot, or NULL if |
| 918 | no table is defined for a slot. Slots 0 and 1 are filled with the |
| 919 | JPEG sample tables by jpeg_set_defaults(). If you need to allocate |
| 920 | more table structures, jpeg_alloc_huff_table() may be used. |
| 921 | Note that optimal Huffman tables can be computed for an image |
| 922 | by setting optimize_coding, as discussed above; there's seldom |
| 923 | any need to mess with providing your own Huffman tables. |
| 924 | |
| 925 | There are some additional cinfo fields which are not documented here |
| 926 | because you currently can't change them; for example, you can't set |
| 927 | arith_code TRUE because arithmetic coding is unsupported. |
| 928 | |
| 929 | |
| 930 | Per-component parameters are stored in the struct cinfo.comp_info[i] for |
| 931 | component number i. Note that components here refer to components of the |
| 932 | JPEG color space, *not* the source image color space. A suitably large |
| 933 | comp_info[] array is allocated by jpeg_set_defaults(); if you choose not |
| 934 | to use that routine, it's up to you to allocate the array. |
| 935 | |
| 936 | int component_id |
| 937 | The one-byte identifier code to be recorded in the JPEG file for |
| 938 | this component. For the standard color spaces, we recommend you |
| 939 | leave the default values alone. |
| 940 | |
| 941 | int h_samp_factor |
| 942 | int v_samp_factor |
| 943 | Horizontal and vertical sampling factors for the component; must |
| 944 | be 1..4 according to the JPEG standard. Note that larger sampling |
| 945 | factors indicate a higher-resolution component; many people find |
| 946 | this behavior quite unintuitive. The default values are 2,2 for |
| 947 | luminance components and 1,1 for chrominance components, except |
| 948 | for grayscale where 1,1 is used. |
| 949 | |
| 950 | int quant_tbl_no |
| 951 | Quantization table number for component. The default value is |
| 952 | 0 for luminance components and 1 for chrominance components. |
| 953 | |
| 954 | int dc_tbl_no |
| 955 | int ac_tbl_no |
| 956 | DC and AC entropy coding table numbers. The default values are |
| 957 | 0 for luminance components and 1 for chrominance components. |
| 958 | |
| 959 | int component_index |
| 960 | Must equal the component's index in comp_info[]. |
| 961 | |
| 962 | |
| 963 | Decompression parameter selection |
| 964 | --------------------------------- |
| 965 | |
| 966 | Decompression parameter selection is somewhat simpler than compression |
| 967 | parameter selection, since all of the JPEG internal parameters are |
| 968 | recorded in the source file and need not be supplied by the application. |
| 969 | (Unless you are working with abbreviated files, in which case see |
| 970 | "Abbreviated datastreams", below.) Decompression parameters control |
| 971 | the postprocessing done on the image to deliver it in a format suitable |
| 972 | for the application's use. Many of the parameters control speed/quality |
| 973 | tradeoffs, in which faster decompression may be obtained at the price of |
| 974 | a poorer-quality image. The defaults select the highest quality (slowest) |
| 975 | processing. |
| 976 | |
| 977 | The following fields in the JPEG object are set by jpeg_read_header() and |
| 978 | may be useful to the application in choosing decompression parameters: |
| 979 | |
| 980 | JDIMENSION image_width Width and height of image |
| 981 | JDIMENSION image_height |
| 982 | int num_components Number of color components |
| 983 | J_COLOR_SPACE jpeg_color_space Colorspace of image |
| 984 | boolean saw_JFIF_marker TRUE if a JFIF APP0 marker was seen |
| 985 | UINT8 density_unit Resolution data from JFIF marker |
| 986 | UINT16 X_density |
| 987 | UINT16 Y_density |
| 988 | boolean saw_Adobe_marker TRUE if an Adobe APP14 marker was seen |
| 989 | UINT8 Adobe_transform Color transform code from Adobe marker |
| 990 | |
| 991 | The JPEG color space, unfortunately, is something of a guess since the JPEG |
| 992 | standard proper does not provide a way to record it. In practice most files |
| 993 | adhere to the JFIF or Adobe conventions, and the decoder will recognize these |
| 994 | correctly. See "Special color spaces", below, for more info. |
| 995 | |
| 996 | |
| 997 | The decompression parameters that determine the basic properties of the |
| 998 | returned image are: |
| 999 | |
| 1000 | J_COLOR_SPACE out_color_space |
| 1001 | Output color space. jpeg_read_header() sets an appropriate default |
| 1002 | based on jpeg_color_space; typically it will be RGB or grayscale. |
| 1003 | The application can change this field to request output in a different |
| 1004 | colorspace. For example, set it to JCS_GRAYSCALE to get grayscale |
| 1005 | output from a color file. (This is useful for previewing: grayscale |
| 1006 | output is faster than full color since the color components need not |
| 1007 | be processed.) Note that not all possible color space transforms are |
| 1008 | currently implemented; you may need to extend jdcolor.c if you want an |
| 1009 | unusual conversion. |
| 1010 | |
| 1011 | unsigned int scale_num, scale_denom |
| 1012 | Scale the image by the fraction scale_num/scale_denom. Default is |
| 1013 | 1/1, or no scaling. Currently, the only supported scaling ratios |
| 1014 | are 1/1, 1/2, 1/4, and 1/8. (The library design allows for arbitrary |
| 1015 | scaling ratios but this is not likely to be implemented any time soon.) |
| 1016 | Smaller scaling ratios permit significantly faster decoding since |
| 1017 | fewer pixels need be processed and a simpler IDCT method can be used. |
| 1018 | |
| 1019 | boolean quantize_colors |
| 1020 | If set TRUE, colormapped output will be delivered. Default is FALSE, |
| 1021 | meaning that full-color output will be delivered. |
| 1022 | |
| 1023 | The next three parameters are relevant only if quantize_colors is TRUE. |
| 1024 | |
| 1025 | int desired_number_of_colors |
| 1026 | Maximum number of colors to use in generating a library-supplied color |
| 1027 | map (the actual number of colors is returned in a different field). |
| 1028 | Default 256. Ignored when the application supplies its own color map. |
| 1029 | |
| 1030 | boolean two_pass_quantize |
| 1031 | If TRUE, an extra pass over the image is made to select a custom color |
| 1032 | map for the image. This usually looks a lot better than the one-size- |
| 1033 | fits-all colormap that is used otherwise. Default is TRUE. Ignored |
| 1034 | when the application supplies its own color map. |
| 1035 | |
| 1036 | J_DITHER_MODE dither_mode |
| 1037 | Selects color dithering method. Supported values are: |
| 1038 | JDITHER_NONE no dithering: fast, very low quality |
| 1039 | JDITHER_ORDERED ordered dither: moderate speed and quality |
| 1040 | JDITHER_FS Floyd-Steinberg dither: slow, high quality |
| 1041 | Default is JDITHER_FS. (At present, ordered dither is implemented |
| 1042 | only in the single-pass, standard-colormap case. If you ask for |
| 1043 | ordered dither when two_pass_quantize is TRUE or when you supply |
| 1044 | an external color map, you'll get F-S dithering.) |
| 1045 | |
| 1046 | When quantize_colors is TRUE, the target color map is described by the next |
| 1047 | two fields. colormap is set to NULL by jpeg_read_header(). The application |
| 1048 | can supply a color map by setting colormap non-NULL and setting |
| 1049 | actual_number_of_colors to the map size. Otherwise, jpeg_start_decompress() |
| 1050 | selects a suitable color map and sets these two fields itself. |
| 1051 | [Implementation restriction: at present, an externally supplied colormap is |
| 1052 | only accepted for 3-component output color spaces.] |
| 1053 | |
| 1054 | JSAMPARRAY colormap |
| 1055 | The color map, represented as a 2-D pixel array of out_color_components |
| 1056 | rows and actual_number_of_colors columns. Ignored if not quantizing. |
Thomas G. Lane | a8b67c4 | 1995-03-15 00:00:00 +0000 | [diff] [blame^] | 1057 | CAUTION: if the JPEG library creates its own colormap, the storage |
| 1058 | pointed to by this field is released by jpeg_finish_decompress(). |
| 1059 | Copy the colormap somewhere else first, if you want to save it. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 1060 | |
| 1061 | int actual_number_of_colors |
| 1062 | The number of colors in the color map. |
| 1063 | |
| 1064 | Additional decompression parameters that the application may set include: |
| 1065 | |
| 1066 | J_DCT_METHOD dct_method |
| 1067 | Selects the algorithm used for the DCT step. Choices are the same |
| 1068 | as described above for compression. |
| 1069 | |
| 1070 | boolean do_fancy_upsampling |
| 1071 | If TRUE, do careful upsampling of chroma components. If FALSE, |
| 1072 | a faster but sloppier method is used. Default is TRUE. The visual |
| 1073 | impact of the sloppier method is often very small. |
| 1074 | |
| 1075 | |
| 1076 | The output image dimensions are given by the following fields. These are |
| 1077 | computed from the source image dimensions and the decompression parameters |
| 1078 | by jpeg_start_decompress(). You can also call jpeg_calc_output_dimensions() |
| 1079 | to obtain the values that will result from the current parameter settings. |
| 1080 | This can be useful if you are trying to pick a scaling ratio that will get |
| 1081 | close to a desired target size. It's also important if you are using the |
| 1082 | JPEG library's memory manager to allocate output buffer space, because you |
| 1083 | are supposed to request such buffers *before* jpeg_start_decompress(). |
| 1084 | |
| 1085 | JDIMENSION output_width Actual dimensions of output image. |
| 1086 | JDIMENSION output_height |
| 1087 | int out_color_components Number of color components in out_color_space. |
| 1088 | int output_components Number of color components returned. |
| 1089 | int rec_outbuf_height Recommended height of scanline buffer. |
| 1090 | |
| 1091 | When quantizing colors, output_components is 1, indicating a single color map |
| 1092 | index per pixel. Otherwise it equals out_color_components. The output arrays |
| 1093 | are required to be output_width * output_components JSAMPLEs wide. |
| 1094 | |
| 1095 | rec_outbuf_height is the recommended minimum height (in scanlines) of the |
| 1096 | buffer passed to jpeg_read_scanlines(). If the buffer is smaller, the |
| 1097 | library will still work, but time will be wasted due to unnecessary data |
| 1098 | copying. In high-quality modes, rec_outbuf_height is always 1, but some |
| 1099 | faster, lower-quality modes set it to larger values (typically 2 to 4). |
| 1100 | If you are going to ask for a high-speed processing mode, you may as well |
| 1101 | go to the trouble of honoring rec_outbuf_height so as to avoid data copying. |
| 1102 | |
| 1103 | |
| 1104 | Special color spaces |
| 1105 | -------------------- |
| 1106 | |
| 1107 | The JPEG standard itself is "color blind" and doesn't specify any particular |
| 1108 | color space. It is customary to convert color data to a luminance/chrominance |
| 1109 | color space before compressing, since this permits greater compression. The |
| 1110 | existing de-facto JPEG file format standards specify YCbCr or grayscale data |
| 1111 | (JFIF), or grayscale, RGB, YCbCr, CMYK, or YCCK (Adobe). For special |
| 1112 | applications such as multispectral images, other color spaces can be used, |
| 1113 | but it must be understood that such files will be unportable. |
| 1114 | |
| 1115 | The JPEG library can handle the most common colorspace conversions (namely |
| 1116 | RGB <=> YCbCr and CMYK <=> YCCK). It can also deal with data of an unknown |
| 1117 | color space, passing it through without conversion. If you deal extensively |
| 1118 | with an unusual color space, you can easily extend the library to understand |
| 1119 | additional color spaces and perform appropriate conversions. |
| 1120 | |
| 1121 | For compression, the source data's color space is specified by field |
| 1122 | in_color_space. This is transformed to the JPEG file's color space given |
| 1123 | by jpeg_color_space. jpeg_set_defaults() chooses a reasonable JPEG color |
| 1124 | space depending on in_color_space, but you can override this by calling |
| 1125 | jpeg_set_colorspace(). Of course you must select a supported transformation. |
| 1126 | jccolor.c currently supports the following transformations: |
| 1127 | RGB => YCbCr |
| 1128 | RGB => GRAYSCALE |
| 1129 | YCbCr => GRAYSCALE |
| 1130 | CMYK => YCCK |
| 1131 | plus the null transforms: GRAYSCALE => GRAYSCALE, RGB => RGB, |
| 1132 | YCbCr => YCbCr, CMYK => CMYK, YCCK => YCCK, and UNKNOWN => UNKNOWN. |
| 1133 | |
| 1134 | The de-facto file format standards (JFIF and Adobe) specify APPn markers that |
| 1135 | indicate the color space of the JPEG file. It is important to ensure that |
| 1136 | these are written correctly, or omitted if the JPEG file's color space is not |
| 1137 | one of the ones supported by the de-facto standards. jpeg_set_colorspace() |
| 1138 | will set the compression parameters to include or omit the APPn markers |
| 1139 | properly, so long as it is told the truth about the JPEG color space. |
| 1140 | For example, if you are writing some random 3-component color space without |
| 1141 | conversion, don't try to fake out the library by setting in_color_space and |
| 1142 | jpeg_color_space to JCS_YCbCr; use JCS_UNKNOWN. You may want to write an |
| 1143 | APPn marker of your own devising to identify the colorspace --- see "Special |
| 1144 | markers", below. |
| 1145 | |
| 1146 | When told that the color space is UNKNOWN, the library will default to using |
| 1147 | luminance-quality compression parameters for all color components. You may |
| 1148 | well want to change these parameters. See the source code for |
| 1149 | jpeg_set_colorspace(), in jcparam.c, for details. |
| 1150 | |
| 1151 | For decompression, the JPEG file's color space is given in jpeg_color_space, |
| 1152 | and this is transformed to the output color space out_color_space. |
| 1153 | jpeg_read_header's setting of jpeg_color_space can be relied on if the file |
| 1154 | conforms to JFIF or Adobe conventions, but otherwise it is no better than a |
| 1155 | guess. If you know the JPEG file's color space for certain, you can override |
| 1156 | jpeg_read_header's guess by setting jpeg_color_space. jpeg_read_header also |
| 1157 | selects a default output color space based on (its guess of) jpeg_color_space; |
| 1158 | set out_color_space to override this. Again, you must select a supported |
| 1159 | transformation. jdcolor.c currently supports |
| 1160 | YCbCr => GRAYSCALE |
| 1161 | YCbCr => RGB |
| 1162 | YCCK => CMYK |
| 1163 | as well as the null transforms. |
| 1164 | |
| 1165 | The two-pass color quantizer, jquant2.c, is specialized to handle RGB data |
| 1166 | (it weights distances appropriately for RGB colors). You'll need to modify |
| 1167 | the code if you want to use it for non-RGB output color spaces. Note that |
| 1168 | jquant2.c is used to map to an application-supplied colormap as well as for |
| 1169 | the normal two-pass colormap selection process. |
| 1170 | |
| 1171 | CAUTION: it appears that Adobe Photoshop writes inverted data in CMYK JPEG |
| 1172 | files: 0 represents 100% ink coverage, rather than 0% ink as you'd expect. |
| 1173 | This is arguably a bug in Photoshop, but if you need to work with Photoshop |
| 1174 | CMYK files, you will have to deal with it in your application. We cannot |
| 1175 | "fix" this in the library by inverting the data during the CMYK<=>YCCK |
| 1176 | transform, because that would break other applications, notably Ghostscript. |
| 1177 | Photoshop versions prior to 3.0 write EPS files containing JPEG-encoded CMYK |
| 1178 | data in the same inverted-YCCK representation used in bare JPEG files, but |
| 1179 | the surrounding PostScript code performs an inversion using the PS image |
| 1180 | operator. I am told that Photoshop 3.0 will write uninverted YCCK in |
| 1181 | EPS/JPEG files, and will omit the PS-level inversion. (But the data |
| 1182 | polarity used in bare JPEG files will not change in 3.0.) In either case, |
| 1183 | the JPEG library must not invert the data itself, or else Ghostscript would |
| 1184 | read these EPS files incorrectly. |
| 1185 | |
| 1186 | |
| 1187 | Error handling |
| 1188 | -------------- |
| 1189 | |
| 1190 | When the default error handler is used, any error detected inside the JPEG |
| 1191 | routines will cause a message to be printed on stderr, followed by exit(). |
| 1192 | You can supply your own error handling routines to override this behavior |
| 1193 | and to control the treatment of nonfatal warnings and trace/debug messages. |
| 1194 | The file example.c illustrates the most common case, which is to have the |
| 1195 | application regain control after an error rather than exiting. |
| 1196 | |
| 1197 | The JPEG library never writes any message directly; it always goes through |
| 1198 | the error handling routines. Three classes of messages are recognized: |
| 1199 | * Fatal errors: the library cannot continue. |
| 1200 | * Warnings: the library can continue, but the data is corrupt, and a |
| 1201 | damaged output image is likely to result. |
| 1202 | * Trace/informational messages. These come with a trace level indicating |
| 1203 | the importance of the message; you can control the verbosity of the |
| 1204 | program by adjusting the maximum trace level that will be displayed. |
| 1205 | |
| 1206 | You may, if you wish, simply replace the entire JPEG error handling module |
| 1207 | (jerror.c) with your own code. However, you can avoid code duplication by |
| 1208 | only replacing some of the routines depending on the behavior you need. |
| 1209 | This is accomplished by calling jpeg_std_error() as usual, but then overriding |
| 1210 | some of the method pointers in the jpeg_error_mgr struct, as illustrated by |
| 1211 | example.c. |
| 1212 | |
| 1213 | All of the error handling routines will receive a pointer to the JPEG object |
| 1214 | (a j_common_ptr which points to either a jpeg_compress_struct or a |
| 1215 | jpeg_decompress_struct; if you need to tell which, test the is_decompressor |
| 1216 | field). This struct includes a pointer to the error manager struct in its |
| 1217 | "err" field. Frequently, custom error handler routines will need to access |
| 1218 | additional data which is not known to the JPEG library or the standard error |
| 1219 | handler. The most convenient way to do this is to embed either the JPEG |
| 1220 | object or the jpeg_error_mgr struct in a larger structure that contains |
| 1221 | additional fields; then casting the passed pointer provides access to the |
| 1222 | additional fields. Again, see example.c for one way to do it. |
| 1223 | |
| 1224 | The individual methods that you might wish to override are: |
| 1225 | |
| 1226 | error_exit (j_common_ptr cinfo) |
| 1227 | Receives control for a fatal error. Information sufficient to |
| 1228 | generate the error message has been stored in cinfo->err; call |
| 1229 | output_message to display it. Control must NOT return to the caller; |
| 1230 | generally this routine will exit() or longjmp() somewhere. |
| 1231 | Typically you would override this routine to get rid of the exit() |
| 1232 | default behavior. Note that if you continue processing, you should |
| 1233 | clean up the JPEG object with jpeg_abort() or jpeg_destroy(). |
| 1234 | |
| 1235 | output_message (j_common_ptr cinfo) |
| 1236 | Actual output of any JPEG message. Override this to send messages |
| 1237 | somewhere other than stderr. Note that this method does not know |
| 1238 | how to generate a message, only where to send it. |
| 1239 | |
| 1240 | format_message (j_common_ptr cinfo, char * buffer) |
| 1241 | Constructs a readable error message string based on the error info |
| 1242 | stored in cinfo->err. This method is called by output_message. Few |
| 1243 | applications should need to override this method. One possible |
| 1244 | reason for doing so is to implement dynamic switching of error message |
| 1245 | language. |
| 1246 | |
| 1247 | emit_message (j_common_ptr cinfo, int msg_level) |
| 1248 | Decide whether or not to emit a warning or trace message; if so, |
| 1249 | calls output_message. The main reason for overriding this method |
| 1250 | would be to abort on warnings. msg_level is -1 for warnings, |
| 1251 | 0 and up for trace messages. |
| 1252 | |
| 1253 | Only error_exit() and emit_message() are called from the rest of the JPEG |
| 1254 | library; the other two are internal to the error handler. |
| 1255 | |
| 1256 | The actual message texts are stored in an array of strings which is pointed to |
| 1257 | by the field err->jpeg_message_table. The messages are numbered from 0 to |
| 1258 | err->last_jpeg_message, and it is these code numbers that are used in the |
| 1259 | JPEG library code. You could replace the message texts (for instance, with |
| 1260 | messages in French or German) by changing the message table pointer. See |
| 1261 | jerror.h for the default texts. CAUTION: this table will almost certainly |
| 1262 | change or grow from one library version to the next. |
| 1263 | |
| 1264 | It may be useful for an application to add its own message texts that are |
| 1265 | handled by the same mechanism. The error handler supports a second "add-on" |
| 1266 | message table for this purpose. To define an addon table, set the pointer |
| 1267 | err->addon_message_table and the message numbers err->first_addon_message and |
| 1268 | err->last_addon_message. If you number the addon messages beginning at 1000 |
| 1269 | or so, you won't have to worry about conflicts with the library's built-in |
| 1270 | messages. See the sample applications cjpeg/djpeg for an example of using |
| 1271 | addon messages (the addon messages are defined in cderror.h). |
| 1272 | |
| 1273 | Actual invocation of the error handler is done via macros defined in jerror.h: |
| 1274 | ERREXITn(...) for fatal errors |
| 1275 | WARNMSn(...) for corrupt-data warnings |
| 1276 | TRACEMSn(...) for trace and informational messages. |
| 1277 | These macros store the message code and any additional parameters into the |
| 1278 | error handler struct, then invoke the error_exit() or emit_message() method. |
| 1279 | The variants of each macro are for varying numbers of additional parameters. |
| 1280 | The additional parameters are inserted into the generated message using |
| 1281 | standard printf() format codes. |
| 1282 | |
| 1283 | See jerror.h and jerror.c for further details. |
| 1284 | |
| 1285 | |
| 1286 | Compressed data handling (source and destination managers) |
| 1287 | ---------------------------------------------------------- |
| 1288 | |
| 1289 | The JPEG compression library sends its compressed data to a "destination |
| 1290 | manager" module. The default destination manager just writes the data to a |
| 1291 | stdio stream, but you can provide your own manager to do something else. |
| 1292 | Similarly, the decompression library calls a "source manager" to obtain the |
| 1293 | compressed data; you can provide your own source manager if you want the data |
| 1294 | to come from somewhere other than a stdio stream. |
| 1295 | |
| 1296 | In both cases, compressed data is processed a bufferload at a time: the |
| 1297 | destination or source manager provides a work buffer, and the library invokes |
| 1298 | the manager only when the buffer is filled or emptied. (You could define a |
| 1299 | one-character buffer to force the manager to be invoked for each byte, but |
| 1300 | that would be rather inefficient.) The buffer's size and location are |
| 1301 | controlled by the manager, not by the library. For example, if you desired to |
| 1302 | decompress a JPEG datastream that was all in memory, you could just make the |
| 1303 | buffer pointer and length point to the original data in memory. Then the |
| 1304 | buffer-reload procedure would be invoked only if the decompressor ran off the |
| 1305 | end of the datastream, which would indicate an erroneous datastream. |
| 1306 | |
| 1307 | The work buffer is defined as an array of datatype JOCTET, which is generally |
| 1308 | "char" or "unsigned char". On a machine where char is not exactly 8 bits |
| 1309 | wide, you must define JOCTET as a wider data type and then modify the data |
| 1310 | source and destination modules to transcribe the work arrays into 8-bit units |
| 1311 | on external storage. |
| 1312 | |
| 1313 | A data destination manager struct contains a pointer and count defining the |
| 1314 | next byte to write in the work buffer and the remaining free space: |
| 1315 | |
| 1316 | JOCTET * next_output_byte; /* => next byte to write in buffer */ |
| 1317 | size_t free_in_buffer; /* # of byte spaces remaining in buffer */ |
| 1318 | |
| 1319 | The library increments the pointer and decrements the count until the buffer |
| 1320 | is filled. The manager's empty_output_buffer method must reset the pointer |
| 1321 | and count. The manager is expected to remember the buffer's starting address |
| 1322 | and total size in private fields not visible to the library. |
| 1323 | |
| 1324 | A data destination manager provides three methods: |
| 1325 | |
| 1326 | init_destination (j_compress_ptr cinfo) |
| 1327 | Initialize destination. This is called by jpeg_start_compress() |
| 1328 | before any data is actually written. It must initialize |
| 1329 | next_output_byte and free_in_buffer. free_in_buffer must be |
| 1330 | initialized to a positive value. |
| 1331 | |
| 1332 | empty_output_buffer (j_compress_ptr cinfo) |
| 1333 | This is called whenever the buffer has filled (free_in_buffer |
| 1334 | reaches zero). In typical applications, it should write out the |
| 1335 | *entire* buffer (use the saved start address and buffer length; |
| 1336 | ignore the current state of next_output_byte and free_in_buffer). |
| 1337 | Then reset the pointer & count to the start of the buffer, and |
| 1338 | return TRUE indicating that the buffer has been dumped. |
| 1339 | free_in_buffer must be set to a positive value when TRUE is |
| 1340 | returned. A FALSE return should only be used when I/O suspension is |
| 1341 | desired (this operating mode is discussed in the next section). |
| 1342 | |
| 1343 | term_destination (j_compress_ptr cinfo) |
| 1344 | Terminate destination --- called by jpeg_finish_compress() after all |
| 1345 | data has been written. In most applications, this must flush any |
| 1346 | data remaining in the buffer. Use either next_output_byte or |
| 1347 | free_in_buffer to determine how much data is in the buffer. |
| 1348 | |
| 1349 | term_destination() is NOT called by jpeg_abort() or jpeg_destroy(). If you |
| 1350 | want the destination manager to be cleaned up during an abort, you must do it |
| 1351 | yourself. |
| 1352 | |
| 1353 | You will also need code to create a jpeg_destination_mgr struct, fill in its |
| 1354 | method pointers, and insert a pointer to the struct into the "dest" field of |
| 1355 | the JPEG compression object. This can be done in-line in your setup code if |
| 1356 | you like, but it's probably cleaner to provide a separate routine similar to |
| 1357 | the jpeg_stdio_dest() routine of the supplied destination manager. |
| 1358 | |
| 1359 | Decompression source managers follow a parallel design, but with some |
| 1360 | additional frammishes. The source manager struct contains a pointer and count |
| 1361 | defining the next byte to read from the work buffer and the number of bytes |
| 1362 | remaining: |
| 1363 | |
| 1364 | const JOCTET * next_input_byte; /* => next byte to read from buffer */ |
| 1365 | size_t bytes_in_buffer; /* # of bytes remaining in buffer */ |
| 1366 | |
| 1367 | The library increments the pointer and decrements the count until the buffer |
| 1368 | is emptied. The manager's fill_input_buffer method must reset the pointer and |
| 1369 | count. In most applications, the manager must remember the buffer's starting |
| 1370 | address and total size in private fields not visible to the library. |
| 1371 | |
| 1372 | A data source manager provides five methods: |
| 1373 | |
| 1374 | init_source (j_decompress_ptr cinfo) |
| 1375 | Initialize source. This is called by jpeg_read_header() before any |
| 1376 | data is actually read. Unlike init_destination(), it may leave |
| 1377 | bytes_in_buffer set to 0 (in which case a fill_input_buffer() call |
| 1378 | will occur immediately). |
| 1379 | |
| 1380 | fill_input_buffer (j_decompress_ptr cinfo) |
| 1381 | This is called whenever bytes_in_buffer has reached zero and more |
| 1382 | data is wanted. In typical applications, it should read fresh data |
| 1383 | into the buffer (ignoring the current state of next_input_byte and |
| 1384 | bytes_in_buffer), reset the pointer & count to the start of the |
| 1385 | buffer, and return TRUE indicating that the buffer has been reloaded. |
| 1386 | It is not necessary to fill the buffer entirely, only to obtain at |
| 1387 | least one more byte. bytes_in_buffer MUST be set to a positive value |
| 1388 | if TRUE is returned. A FALSE return should only be used when I/O |
| 1389 | suspension is desired (this mode is discussed in the next section). |
| 1390 | |
| 1391 | skip_input_data (j_decompress_ptr cinfo, long num_bytes) |
| 1392 | Skip num_bytes worth of data. The buffer pointer and count should |
| 1393 | be advanced over num_bytes input bytes, refilling the buffer as |
| 1394 | needed. This is used to skip over a potentially large amount of |
| 1395 | uninteresting data (such as an APPn marker). In some applications |
| 1396 | it may be possible to optimize away the reading of the skipped data, |
| 1397 | but it's not clear that being smart is worth much trouble; large |
| 1398 | skips are uncommon. bytes_in_buffer may be zero on return. |
| 1399 | A zero or negative skip count should be treated as a no-op. |
| 1400 | |
| 1401 | resync_to_restart (j_decompress_ptr cinfo) |
| 1402 | This routine is called only when the decompressor has failed to find |
| 1403 | a restart (RSTn) marker where one is expected. Its mission is to |
| 1404 | find a suitable point for resuming decompression. For most |
| 1405 | applications, we recommend that you just use the default resync |
| 1406 | procedure, jpeg_resync_to_restart(). However, if you are able to back |
| 1407 | up in the input data stream, or if you have a-priori knowledge about |
| 1408 | the likely location of restart markers, you may be able to do better. |
| 1409 | Read the read_restart_marker() and jpeg_resync_to_restart() routines |
| 1410 | in jdmarker.c if you think you'd like to implement your own resync |
| 1411 | procedure. |
| 1412 | |
| 1413 | term_source (j_decompress_ptr cinfo) |
| 1414 | Terminate source --- called by jpeg_finish_decompress() after all |
| 1415 | data has been read. Often a no-op. |
| 1416 | |
| 1417 | For both fill_input_buffer() and skip_input_data(), there is no such thing |
| 1418 | as an EOF return. If the end of the file has been reached, the routine has |
| 1419 | a choice of exiting via ERREXIT() or inserting fake data into the buffer. |
| 1420 | In most cases, generating a warning message and inserting a fake EOI marker |
| 1421 | is the best course of action --- this will allow the decompressor to output |
| 1422 | however much of the image is there. In pathological cases, the decompressor |
| 1423 | may swallow the EOI and again demand data ... just keep feeding it fake EOIs. |
| 1424 | jdatasrc.c illustrates the recommended error recovery behavior. |
| 1425 | |
| 1426 | term_source() is NOT called by jpeg_abort() or jpeg_destroy(). If you want |
| 1427 | the source manager to be cleaned up during an abort, you must do it yourself. |
| 1428 | |
| 1429 | You will also need code to create a jpeg_source_mgr struct, fill in its method |
| 1430 | pointers, and insert a pointer to the struct into the "src" field of the JPEG |
| 1431 | decompression object. This can be done in-line in your setup code if you |
| 1432 | like, but it's probably cleaner to provide a separate routine similar to the |
| 1433 | jpeg_stdio_src() routine of the supplied source manager. |
| 1434 | |
| 1435 | For more information, consult the stdio source and destination managers |
| 1436 | in jdatasrc.c and jdatadst.c. |
| 1437 | |
| 1438 | |
| 1439 | I/O suspension |
| 1440 | -------------- |
| 1441 | |
| 1442 | Some applications need to use the JPEG library as an incremental memory-to- |
| 1443 | memory filter: when the compressed data buffer is filled or emptied, they want |
| 1444 | control to return to the outer loop, rather than expecting that the buffer can |
| 1445 | be flushed or reloaded within the data source/destination manager subroutine. |
| 1446 | The library supports this need by providing an "I/O suspension" mode, which we |
| 1447 | describe in this section. |
| 1448 | |
| 1449 | The I/O suspension mode is a limited solution: it works only in the simplest |
| 1450 | operating modes (namely single-pass processing of single-scan JPEG files), and |
| 1451 | it has several other restrictions which are documented below. Furthermore, |
| 1452 | nothing is guaranteed about the maximum amount of time spent in any one call |
| 1453 | to the library, so a single-threaded application may still have response-time |
| 1454 | problems. If you need multi-pass processing or guaranteed response time, we |
| 1455 | suggest you "bite the bullet" and implement a real multi-tasking capability. |
| 1456 | |
| 1457 | To use I/O suspension, cooperation is needed between the calling application |
| 1458 | and the data source or destination manager; you will always need a custom |
| 1459 | source/destination manager. (Please read the previous section if you haven't |
| 1460 | already.) The basic idea is that the empty_output_buffer() or |
| 1461 | fill_input_buffer() routine is a no-op, merely returning FALSE to indicate |
| 1462 | that it has done nothing. Upon seeing this, the JPEG library suspends |
| 1463 | operation and returns to its caller. The surrounding application is |
| 1464 | responsible for emptying or refilling the work buffer before calling the JPEG |
| 1465 | library again. |
| 1466 | |
| 1467 | Compression suspension: |
| 1468 | |
| 1469 | For compression suspension, use an empty_output_buffer() routine that |
| 1470 | returns FALSE; typically it will not do anything else. This will cause the |
| 1471 | compressor to return to the caller of jpeg_write_scanlines(), with the |
| 1472 | return value indicating that not all the supplied scanlines have been |
| 1473 | accepted. The application must make more room in the output buffer, adjust |
| 1474 | the buffer pointer/count appropriately, and then call jpeg_write_scanlines() |
| 1475 | again, pointing to the first unconsumed scanline. |
| 1476 | |
| 1477 | When forced to suspend, the compressor will backtrack to a convenient stopping |
| 1478 | point (usually the start of the current MCU); it will regenerate some output |
| 1479 | data when restarted. Therefore, although empty_output_buffer() is only called |
| 1480 | when the buffer is filled, you should NOT dump out the entire buffer, only the |
| 1481 | data up to the current position of next_output_byte/free_in_buffer. The data |
| 1482 | beyond that point will be regenerated after resumption. |
| 1483 | |
| 1484 | Because of the backtracking behavior, a good-size output buffer is essential |
| 1485 | for efficiency; you don't want the compressor to suspend often. (In fact, an |
| 1486 | overly small buffer could lead to infinite looping, if a single MCU required |
| 1487 | more data than would fit in the buffer.) We recommend a buffer of at least |
| 1488 | several Kbytes. You may want to insert explicit code to ensure that you don't |
| 1489 | call jpeg_write_scanlines() unless there is a reasonable amount of space in |
| 1490 | the output buffer; in other words, flush the buffer before trying to compress |
| 1491 | more data. |
| 1492 | |
| 1493 | The JPEG compressor does not support suspension while it is trying to write |
| 1494 | JPEG markers at the beginning and end of the file. This means that |
| 1495 | * At the beginning of a compression operation, there must be enough free |
| 1496 | space in the output buffer to hold the header markers (typically 600 or |
| 1497 | so bytes). The recommended buffer size is bigger than this anyway, so |
| 1498 | this is not a problem as long as you start with an empty buffer. However, |
| 1499 | this restriction might catch you if you insert large special markers, such |
| 1500 | as a JFIF thumbnail image. |
| 1501 | * When you call jpeg_finish_compress(), there must be enough space in the |
| 1502 | output buffer to emit any buffered data and the final EOI marker. In the |
| 1503 | current implementation, half a dozen bytes should suffice for this, but |
| 1504 | for safety's sake we recommend ensuring that at least 100 bytes are free |
| 1505 | before calling jpeg_finish_compress(). |
| 1506 | Furthermore, since jpeg_finish_compress() cannot suspend, you cannot request |
| 1507 | multi-pass operating modes such as Huffman code optimization or multiple-scan |
| 1508 | output. That would imply that a large amount of data would be written inside |
| 1509 | jpeg_finish_compress(), which would certainly trigger a buffer overrun. |
| 1510 | |
| 1511 | Decompression suspension: |
| 1512 | |
| 1513 | For decompression suspension, use a fill_input_buffer() routine that simply |
| 1514 | returns FALSE (except perhaps during error recovery, as discussed below). |
| 1515 | This will cause the decompressor to return to its caller with an indication |
| 1516 | that suspension has occurred. This can happen at three places: |
| 1517 | * jpeg_read_header(): will return JPEG_SUSPENDED. |
| 1518 | * jpeg_read_scanlines(): will return the number of scanlines already |
| 1519 | completed (possibly 0). |
| 1520 | * jpeg_finish_decompress(): will return FALSE, rather than its usual TRUE. |
| 1521 | The surrounding application must recognize these cases, load more data into |
| 1522 | the input buffer, and repeat the call. In the case of jpeg_read_scanlines(), |
| 1523 | adjust the passed pointers to reflect any scanlines successfully read. |
| 1524 | |
| 1525 | Just as with compression, the decompressor will typically backtrack to a |
| 1526 | convenient restart point before suspending. The data beyond the current |
| 1527 | position of next_input_byte/bytes_in_buffer must NOT be discarded; it will |
| 1528 | be re-read upon resumption. In most implementations, you'll need to shift |
| 1529 | this data down to the start of your work buffer and then load more data |
| 1530 | after it. Again, this behavior means that a several-Kbyte work buffer is |
| 1531 | essential for decent performance; furthermore, you should load a reasonable |
| 1532 | amount of new data before resuming decompression. (If you loaded, say, |
| 1533 | only one new byte each time around, you could waste a LOT of cycles.) |
| 1534 | |
| 1535 | The skip_input_data() source manager routine requires special care in a |
| 1536 | suspension scenario. This routine is NOT granted the ability to suspend the |
| 1537 | decompressor; it can decrement bytes_in_buffer to zero, but no more. If the |
| 1538 | requested skip distance exceeds the amount of data currently in the input |
| 1539 | buffer, then skip_input_data() must set bytes_in_buffer to zero and record the |
| 1540 | additional skip distance somewhere else. The decompressor will immediately |
| 1541 | call fill_input_buffer(), which will return FALSE, which will cause a |
| 1542 | suspension return. The surrounding application must then arrange to discard |
| 1543 | the right number of bytes before it resumes loading the input buffer. (Yes, |
| 1544 | this design is rather baroque, but it avoids complexity in the far more common |
| 1545 | case where a non-suspending source manager is used.) |
| 1546 | |
| 1547 | If the input data has been exhausted, we recommend that you emit a warning |
| 1548 | and insert dummy EOI markers just as a non-suspending data source manager |
| 1549 | would do. This can be handled either in the surrounding application logic or |
| 1550 | within fill_input_buffer(); the latter is probably more efficient. If |
| 1551 | fill_input_buffer() knows that no more data is available, it can set the |
| 1552 | pointer/count to point to a dummy EOI marker and then return TRUE just as |
| 1553 | though it had read more data in a non-suspending situation. |
| 1554 | |
| 1555 | The decompressor does not support suspension within jpeg_start_decompress(). |
| 1556 | This means that you cannot use suspension with any multi-pass processing mode |
| 1557 | (eg, two-pass color quantization or multiple-scan JPEG files). In single-pass |
| 1558 | modes, jpeg_start_decompress() reads no data and thus need never suspend. |
| 1559 | |
| 1560 | The decompressor does not attempt to suspend within any JPEG marker; it will |
| 1561 | backtrack to the start of the marker. Hence the input buffer must be large |
| 1562 | enough to hold the longest marker in the file. We recommend at least a 2K |
| 1563 | buffer. The buffer would need to be 64K to allow for arbitrary COM or APPn |
| 1564 | markers, but the decompressor does not actually try to read these; it just |
| 1565 | skips them by calling skip_input_data(). If you provide a special marker |
| 1566 | handling routine that does look at such markers, coping with buffer overflow |
| 1567 | is your problem. Ordinary JPEG markers should normally not exceed a few |
| 1568 | hundred bytes each (DHT tables are typically the longest). For robustness |
| 1569 | against damaged marker length counts, you may wish to insert a test in your |
| 1570 | application for the case that the input buffer is completely full and yet the |
| 1571 | decoder has suspended without consuming any data --- otherwise, if this |
| 1572 | situation did occur, it would lead to an endless loop. |
| 1573 | |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 1574 | Multiple-buffer management: |
| 1575 | |
| 1576 | In some applications it is desirable to store the compressed data in a linked |
| 1577 | list of buffer areas, so as to avoid data copying. This can be handled by |
| 1578 | having empty_output_buffer() or fill_input_buffer() set the pointer and count |
| 1579 | to reference the next available buffer; FALSE is returned only if no more |
| 1580 | buffers are available. Although seemingly straightforward, there is a |
| 1581 | pitfall in this approach: the backtrack that occurs when FALSE is returned |
| 1582 | could back up into an earlier buffer. Do not discard "completed" buffers in |
| 1583 | the empty_output_buffer() or fill_input_buffer() routine, unless you can tell |
| 1584 | from the saved pointer/bytecount that the JPEG library will no longer attempt |
| 1585 | to backtrack that far. It's probably simplest to postpone releasing any |
| 1586 | buffers until the library returns to its caller; then you can use the final |
| 1587 | bytecount to tell how much data has been fully processed, and release buffers |
| 1588 | on that basis. |
| 1589 | |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 1590 | |
| 1591 | Abbreviated datastreams and multiple images |
| 1592 | ------------------------------------------- |
| 1593 | |
| 1594 | A JPEG compression or decompression object can be reused to process multiple |
| 1595 | images. This saves a small amount of time per image by eliminating the |
| 1596 | "create" and "destroy" operations, but that isn't the real purpose of the |
| 1597 | feature. Rather, reuse of an object provides support for abbreviated JPEG |
| 1598 | datastreams. Object reuse can also simplify processing a series of images in |
| 1599 | a single input or output file. This section explains these features. |
| 1600 | |
| 1601 | A JPEG file normally contains several hundred bytes worth of quantization |
| 1602 | and Huffman tables. In a situation where many images will be stored or |
| 1603 | transmitted with identical tables, this may represent an annoying overhead. |
| 1604 | The JPEG standard therefore permits tables to be omitted. The standard |
| 1605 | defines three classes of JPEG datastreams: |
| 1606 | * "Interchange" datastreams contain an image and all tables needed to decode |
| 1607 | the image. These are the usual kind of JPEG file. |
| 1608 | * "Abbreviated image" datastreams contain an image, but are missing some or |
| 1609 | all of the tables needed to decode that image. |
| 1610 | * "Abbreviated table specification" (henceforth "tables-only") datastreams |
| 1611 | contain only table specifications. |
| 1612 | To decode an abbreviated image, it is necessary to load the missing table(s) |
| 1613 | into the decoder beforehand. This can be accomplished by reading a separate |
| 1614 | tables-only file. A variant scheme uses a series of images in which the first |
| 1615 | image is an interchange (complete) datastream, while subsequent ones are |
| 1616 | abbreviated and rely on the tables loaded by the first image. It is assumed |
| 1617 | that once the decoder has read a table, it will remember that table until a |
| 1618 | new definition for the same table number is encountered. |
| 1619 | |
| 1620 | It is the application designer's responsibility to figure out how to associate |
| 1621 | the correct tables with an abbreviated image. While abbreviated datastreams |
| 1622 | can be useful in a closed environment, their use is strongly discouraged in |
| 1623 | any situation where data exchange with other applications might be needed. |
| 1624 | Caveat designer. |
| 1625 | |
| 1626 | The JPEG library provides support for reading and writing any combination of |
| 1627 | tables-only datastreams and abbreviated images. In both compression and |
| 1628 | decompression objects, a quantization or Huffman table will be retained for |
| 1629 | the lifetime of the object, unless it is overwritten by a new table definition. |
| 1630 | |
| 1631 | |
| 1632 | To create abbreviated image datastreams, it is only necessary to tell the |
| 1633 | compressor not to emit some or all of the tables it is using. Each |
| 1634 | quantization and Huffman table struct contains a boolean field "sent_table", |
| 1635 | which normally is initialized to FALSE. For each table used by the image, the |
| 1636 | header-writing process emits the table and sets sent_table = TRUE unless it is |
| 1637 | already TRUE. (In normal usage, this prevents outputting the same table |
| 1638 | definition multiple times, as would otherwise occur because the chroma |
| 1639 | components typically share tables.) Thus, setting this field to TRUE before |
| 1640 | calling jpeg_start_compress() will prevent the table from being written at |
| 1641 | all. |
| 1642 | |
| 1643 | If you want to create a "pure" abbreviated image file containing no tables, |
| 1644 | just call "jpeg_suppress_tables(&cinfo, TRUE)" after constructing all the |
| 1645 | tables. If you want to emit some but not all tables, you'll need to set the |
| 1646 | individual sent_table fields directly. |
| 1647 | |
| 1648 | To create an abbreviated image, you must also call jpeg_start_compress() |
| 1649 | with a second parameter of FALSE, not TRUE. Otherwise jpeg_start_compress() |
| 1650 | will force all the sent_table fields to FALSE. (This is a safety feature to |
| 1651 | prevent abbreviated images from being created accidentally.) |
| 1652 | |
| 1653 | To create a tables-only file, perform the same parameter setup that you |
| 1654 | normally would, but instead of calling jpeg_start_compress() and so on, call |
| 1655 | jpeg_write_tables(&cinfo). This will write an abbreviated datastream |
| 1656 | containing only SOI, DQT and/or DHT markers, and EOI. All the quantization |
| 1657 | and Huffman tables that are currently defined in the compression object will |
| 1658 | be emitted unless their sent_tables flag is already TRUE, and then all the |
| 1659 | sent_tables flags will be set TRUE. |
| 1660 | |
| 1661 | A sure-fire way to create matching tables-only and abbreviated image files |
| 1662 | is to proceed as follows: |
| 1663 | |
| 1664 | create JPEG compression object |
| 1665 | set JPEG parameters |
| 1666 | set destination to tables-only file |
| 1667 | jpeg_write_tables(&cinfo); |
| 1668 | set destination to image file |
| 1669 | jpeg_start_compress(&cinfo, FALSE); |
| 1670 | write data... |
| 1671 | jpeg_finish_compress(&cinfo); |
| 1672 | |
| 1673 | Since the JPEG parameters are not altered between writing the table file and |
| 1674 | the abbreviated image file, the same tables are sure to be used. Of course, |
| 1675 | you can repeat the jpeg_start_compress() ... jpeg_finish_compress() sequence |
| 1676 | many times to produce many abbreviated image files matching the table file. |
| 1677 | |
| 1678 | You cannot suppress output of the computed Huffman tables when Huffman |
| 1679 | optimization is selected. (If you could, there'd be no way to decode the |
| 1680 | image...) Generally, you don't want to set optimize_coding = TRUE when |
| 1681 | you are trying to produce abbreviated files. |
| 1682 | |
| 1683 | In some cases you might want to compress an image using tables which are |
| 1684 | not stored in the application, but are defined in an interchange or |
| 1685 | tables-only file readable by the application. This can be done by setting up |
| 1686 | a JPEG decompression object to read the specification file, then copying the |
| 1687 | tables into your compression object. |
| 1688 | |
| 1689 | |
| 1690 | To read abbreviated image files, you simply need to load the proper tables |
| 1691 | into the decompression object before trying to read the abbreviated image. |
| 1692 | If the proper tables are stored in the application program, you can just |
| 1693 | allocate the table structs and fill in their contents directly. More commonly |
| 1694 | you'd want to read the tables from a tables-only file. The jpeg_read_header() |
| 1695 | call is sufficient to read a tables-only file. You must pass a second |
| 1696 | parameter of FALSE to indicate that you do not require an image to be present. |
| 1697 | Thus, the typical scenario is |
| 1698 | |
| 1699 | create JPEG decompression object |
| 1700 | set source to tables-only file |
| 1701 | jpeg_read_header(&cinfo, FALSE); |
| 1702 | set source to abbreviated image file |
| 1703 | jpeg_read_header(&cinfo, TRUE); |
| 1704 | set decompression parameters |
| 1705 | jpeg_start_decompress(&cinfo); |
| 1706 | read data... |
| 1707 | jpeg_finish_decompress(&cinfo); |
| 1708 | |
| 1709 | In some cases, you may want to read a file without knowing whether it contains |
| 1710 | an image or just tables. In that case, pass FALSE and check the return value |
| 1711 | from jpeg_read_header(): it will be JPEG_HEADER_OK if an image was found, |
| 1712 | JPEG_HEADER_TABLES_ONLY if only tables were found. (A third return value, |
| 1713 | JPEG_SUSPENDED, is possible when using a suspending data source manager.) |
| 1714 | Note that jpeg_read_header() will not complain if you read an abbreviated |
| 1715 | image for which you haven't loaded the missing tables; the missing-table check |
| 1716 | occurs in jpeg_start_decompress(). |
| 1717 | |
| 1718 | |
| 1719 | It is possible to read a series of images from a single source file by |
| 1720 | repeating the jpeg_read_header() ... jpeg_finish_decompress() sequence, |
| 1721 | without releasing/recreating the JPEG object or the data source module. |
| 1722 | (If you did reinitialize, any partial bufferload left in the data source |
| 1723 | buffer at the end of one image would be discarded, causing you to lose the |
| 1724 | start of the next image.) When you use this method, stored tables are |
| 1725 | automatically carried forward, so some of the images can be abbreviated images |
| 1726 | that depend on tables from earlier images. |
| 1727 | |
| 1728 | If you intend to write a series of images into a single destination file, |
| 1729 | you might want to make a specialized data destination module that doesn't |
| 1730 | flush the output buffer at term_destination() time. This would speed things |
| 1731 | up by some trifling amount. Of course, you'd need to remember to flush the |
| 1732 | buffer after the last image. You can make the later images be abbreviated |
| 1733 | ones by passing FALSE to jpeg_start_compress(). |
| 1734 | |
| 1735 | |
| 1736 | Special markers |
| 1737 | --------------- |
| 1738 | |
| 1739 | Some applications may need to insert or extract special data in the JPEG |
| 1740 | datastream. The JPEG standard provides marker types "COM" (comment) and |
| 1741 | "APP0" through "APP15" (application) to hold application-specific data. |
| 1742 | Unfortunately, the use of these markers is not specified by the standard. |
| 1743 | COM markers are fairly widely used to hold user-supplied text. The JFIF file |
| 1744 | format spec uses APP0 markers with specified initial strings to hold certain |
| 1745 | data. Adobe applications use APP14 markers beginning with the string "Adobe" |
| 1746 | for miscellaneous data. Other APPn markers are rarely seen, but might |
| 1747 | contain almost anything. |
| 1748 | |
| 1749 | If you wish to store user-supplied text, we recommend you use COM markers |
| 1750 | and place readable 7-bit ASCII text in them. Newline conventions are not |
| 1751 | standardized --- expect to find LF (Unix style), CR/LF (DOS style), or CR |
| 1752 | (Mac style). A robust COM reader should be able to cope with random binary |
| 1753 | garbage, including nulls, since some applications generate COM markers |
| 1754 | containing non-ASCII junk. (But yours should not be one of them.) |
| 1755 | |
| 1756 | For program-supplied data, use an APPn marker, and be sure to begin it with an |
| 1757 | identifying string so that you can tell whether the marker is actually yours. |
| 1758 | It's probably best to avoid using APP0 or APP14 for any private markers. |
| 1759 | |
| 1760 | Keep in mind that at most 65533 bytes can be put into one marker, but you |
| 1761 | can have as many markers as you like. |
| 1762 | |
| 1763 | By default, the JPEG compression library will write a JFIF APP0 marker if the |
| 1764 | selected JPEG colorspace is grayscale or YCbCr, or an Adobe APP14 marker if |
| 1765 | the selected colorspace is RGB, CMYK, or YCCK. You can disable this, but |
| 1766 | we don't recommend it. The decompression library will recognize JFIF and |
| 1767 | Adobe markers and will set the JPEG colorspace properly when one is found. |
| 1768 | |
| 1769 | You can write special markers immediately following the datastream header by |
| 1770 | calling jpeg_write_marker() after jpeg_start_compress() and before the first |
| 1771 | call to jpeg_write_scanlines(). When you do this, the markers appear after |
| 1772 | the SOI and the JFIF APP0 and Adobe APP14 markers (if written), but before |
| 1773 | all else. Write the marker type parameter as "JPEG_COM" for COM or |
| 1774 | "JPEG_APP0 + n" for APPn. (Actually, jpeg_write_marker will let you write |
| 1775 | any marker type, but we don't recommend writing any other kinds of marker.) |
| 1776 | For example, to write a user comment string pointed to by comment_text: |
| 1777 | jpeg_write_marker(cinfo, JPEG_COM, comment_text, strlen(comment_text)); |
| 1778 | Or if you prefer to synthesize the marker byte sequence yourself, you can |
| 1779 | just cram it straight into the data destination module. |
| 1780 | |
| 1781 | For decompression, you can supply your own routine to process COM or APPn |
| 1782 | markers by calling jpeg_set_marker_processor(). Usually you'd call this |
| 1783 | after creating a decompression object and before calling jpeg_read_header(), |
| 1784 | because the markers of interest will normally be scanned by jpeg_read_header. |
| 1785 | Once you've supplied a routine, it will be used for the life of that |
| 1786 | decompression object. A separate routine may be registered for COM and for |
| 1787 | each APPn marker code. |
| 1788 | |
| 1789 | A marker processor routine must have the signature |
| 1790 | boolean jpeg_marker_parser_method (j_decompress_ptr cinfo) |
| 1791 | Although the marker code is not explicitly passed, the routine can find it |
| 1792 | in cinfo->unread_marker. At the time of call, the marker proper has been |
| 1793 | read from the data source module. The processor routine is responsible for |
| 1794 | reading the marker length word and the remaining parameter bytes, if any. |
| 1795 | Return TRUE to indicate success. (FALSE should be returned only if you are |
| 1796 | using a suspending data source and it tells you to suspend. See the standard |
| 1797 | marker processors in jdmarker.c for appropriate coding methods if you need to |
| 1798 | use a suspending data source.) |
| 1799 | |
| 1800 | If you override the default APP0 or APP14 processors, it is up to you to |
| 1801 | recognize JFIF and Adobe markers if you want colorspace recognition to occur |
| 1802 | properly. We recommend copying and extending the default processors if you |
| 1803 | want to do that. |
| 1804 | |
| 1805 | A simple example of an external COM processor can be found in djpeg.c. |
| 1806 | |
| 1807 | |
| 1808 | Raw (downsampled) image data |
| 1809 | ---------------------------- |
| 1810 | |
| 1811 | Some applications need to supply already-downsampled image data to the JPEG |
| 1812 | compressor, or to receive raw downsampled data from the decompressor. The |
| 1813 | library supports this requirement by allowing the application to write or |
| 1814 | read raw data, bypassing the normal preprocessing or postprocessing steps. |
| 1815 | The interface is different from the standard one and is somewhat harder to |
| 1816 | use. If your interest is merely in bypassing color conversion, we recommend |
| 1817 | that you use the standard interface and simply set jpeg_color_space = |
| 1818 | in_color_space (or jpeg_color_space = out_color_space for decompression). |
| 1819 | The mechanism described in this section is necessary only to supply or |
| 1820 | receive downsampled image data, in which not all components have the same |
| 1821 | dimensions. |
| 1822 | |
| 1823 | |
| 1824 | To compress raw data, you must supply the data in the colorspace to be used |
| 1825 | in the JPEG file (please read the earlier section on Special color spaces) |
| 1826 | and downsampled to the sampling factors specified in the JPEG parameters. |
| 1827 | You must supply the data in the format used internally by the JPEG library, |
| 1828 | namely a JSAMPIMAGE array. This is an array of pointers to two-dimensional |
| 1829 | arrays, each of type JSAMPARRAY. Each 2-D array holds the values for one |
| 1830 | color component. This structure is necessary since the components are of |
| 1831 | different sizes. If the image dimensions are not a multiple of the MCU size, |
| 1832 | you must also pad the data correctly (usually, this is done by replicating |
| 1833 | the last column and/or row). The data must be padded to a multiple of a DCT |
| 1834 | block in each component: that is, each downsampled row must contain a |
| 1835 | multiple of 8 valid samples, and there must be a multiple of 8 sample rows |
| 1836 | for each component. (For applications such as conversion of digital TV |
| 1837 | images, the standard image size is usually a multiple of the DCT block size, |
| 1838 | so that no padding need actually be done.) |
| 1839 | |
| 1840 | The procedure for compression of raw data is basically the same as normal |
| 1841 | compression, except that you call jpeg_write_raw_data() in place of |
| 1842 | jpeg_write_scanlines(). Before calling jpeg_start_compress(), you must do |
| 1843 | the following: |
| 1844 | * Set cinfo->raw_data_in to TRUE. (It is set FALSE by jpeg_set_defaults().) |
| 1845 | This notifies the library that you will be supplying raw data. |
| 1846 | * Ensure jpeg_color_space is correct --- an explicit jpeg_set_colorspace() |
| 1847 | call is a good idea. Note that since color conversion is bypassed, |
| 1848 | in_color_space is ignored, except that jpeg_set_defaults() uses it to |
| 1849 | choose the default jpeg_color_space setting. |
| 1850 | * Ensure the sampling factors, cinfo->comp_info[i].h_samp_factor and |
| 1851 | cinfo->comp_info[i].v_samp_factor, are correct. Since these indicate the |
| 1852 | dimensions of the data you are supplying, it's wise to set them |
| 1853 | explicitly, rather than assuming the library's defaults are what you want. |
| 1854 | |
| 1855 | To pass raw data to the library, call jpeg_write_raw_data() in place of |
| 1856 | jpeg_write_scanlines(). The two routines work similarly except that |
| 1857 | jpeg_write_raw_data takes a JSAMPIMAGE data array rather than JSAMPARRAY. |
| 1858 | The scanlines count passed to and returned from jpeg_write_raw_data is |
| 1859 | measured in terms of the component with the largest v_samp_factor. |
| 1860 | |
| 1861 | jpeg_write_raw_data() processes one MCU row per call, which is to say |
| 1862 | v_samp_factor*DCTSIZE sample rows of each component. The passed num_lines |
| 1863 | value must be at least max_v_samp_factor*DCTSIZE, and the return value will |
| 1864 | be exactly that amount (or possibly some multiple of that amount, in future |
| 1865 | library versions). This is true even on the last call at the bottom of the |
| 1866 | image; don't forget to pad your data as necessary. |
| 1867 | |
| 1868 | The required dimensions of the supplied data can be computed for each |
| 1869 | component as |
| 1870 | cinfo->comp_info[i].width_in_blocks*DCTSIZE samples per row |
| 1871 | cinfo->comp_info[i].height_in_blocks*DCTSIZE rows in image |
| 1872 | after jpeg_start_compress() has initialized those fields. If the valid data |
| 1873 | is smaller than this, it must be padded appropriately. For some sampling |
| 1874 | factors and image sizes, additional dummy DCT blocks are inserted to make |
| 1875 | the image a multiple of the MCU dimensions. The library creates such dummy |
| 1876 | blocks itself; it does not read them from your supplied data. Therefore you |
| 1877 | need never pad by more than DCTSIZE samples. An example may help here. |
| 1878 | Assume 2h2v downsampling of YCbCr data, that is |
| 1879 | cinfo->comp_info[0].h_samp_factor = 2 for Y |
| 1880 | cinfo->comp_info[0].v_samp_factor = 2 |
| 1881 | cinfo->comp_info[1].h_samp_factor = 1 for Cb |
| 1882 | cinfo->comp_info[1].v_samp_factor = 1 |
| 1883 | cinfo->comp_info[2].h_samp_factor = 1 for Cr |
| 1884 | cinfo->comp_info[2].v_samp_factor = 1 |
| 1885 | and suppose that the nominal image dimensions (cinfo->image_width and |
| 1886 | cinfo->image_height) are 101x101 pixels. Then jpeg_start_compress() will |
| 1887 | compute downsampled_width = 101 and width_in_blocks = 13 for Y, |
| 1888 | downsampled_width = 51 and width_in_blocks = 7 for Cb and Cr (and the same |
| 1889 | for the height fields). You must pad the Y data to at least 13*8 = 104 |
| 1890 | columns and rows, the Cb/Cr data to at least 7*8 = 56 columns and rows. The |
| 1891 | MCU height is max_v_samp_factor = 2 DCT rows so you must pass at least 16 |
| 1892 | scanlines on each call to jpeg_write_raw_data(), which is to say 16 actual |
| 1893 | sample rows of Y and 8 each of Cb and Cr. A total of 7 MCU rows are needed, |
| 1894 | so you must pass a total of 7*16 = 112 "scanlines". The last DCT block row |
| 1895 | of Y data is dummy, so it doesn't matter what you pass for it in the data |
| 1896 | arrays, but the scanlines count must total up to 112 so that all of the Cb |
| 1897 | and Cr data gets passed. |
| 1898 | |
Thomas G. Lane | a8b67c4 | 1995-03-15 00:00:00 +0000 | [diff] [blame^] | 1899 | Output suspension is supported with raw-data compression: if the data |
| 1900 | destination module suspends, jpeg_write_raw_data() will return 0. |
| 1901 | In this case the same data rows must be passed again on the next call. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 1902 | |
| 1903 | |
| 1904 | Decompression with raw data output implies bypassing all postprocessing: |
| 1905 | you cannot ask for color quantization, for instance. More seriously, you must |
| 1906 | deal with the color space and sampling factors present in the incoming file. |
| 1907 | If your application only handles, say, 2h1v YCbCr data, you must check for |
| 1908 | and fail on other color spaces or other sampling factors. |
| 1909 | |
| 1910 | To obtain raw data output, set cinfo->raw_data_out = TRUE before |
| 1911 | jpeg_start_decompress() (it is set FALSE by jpeg_read_header()). Be sure to |
| 1912 | verify that the color space and sampling factors are ones you can handle. |
| 1913 | Then call jpeg_read_raw_data() in place of jpeg_read_scanlines(). The |
| 1914 | decompression process is otherwise the same as usual. |
| 1915 | |
| 1916 | jpeg_read_raw_data() returns one MCU row per call, and thus you must pass a |
| 1917 | buffer of at least max_v_samp_factor*DCTSIZE scanlines (scanline counting is |
| 1918 | the same as for raw-data compression). The buffer you pass must be large |
| 1919 | enough to hold the actual data plus padding to DCT-block boundaries. As with |
| 1920 | compression, any entirely dummy DCT blocks are not processed so you need not |
| 1921 | allocate space for them, but the total scanline count includes them. The |
| 1922 | above example of computing buffer dimensions for raw-data compression is |
| 1923 | equally valid for decompression. |
| 1924 | |
| 1925 | Input suspension is supported with raw-data decompression: if the data source |
| 1926 | module suspends, jpeg_read_raw_data() will return 0. |
| 1927 | |
| 1928 | |
| 1929 | Progress monitoring |
| 1930 | ------------------- |
| 1931 | |
| 1932 | Some applications may need to regain control from the JPEG library every so |
| 1933 | often. The typical use of this feature is to produce a percent-done bar or |
| 1934 | other progress display. (For a simple example, see cjpeg.c or djpeg.c.) |
| 1935 | Although you do get control back frequently during the data-transferring pass |
| 1936 | (the jpeg_read_scanlines or jpeg_write_scanlines loop), any additional passes |
| 1937 | will occur inside jpeg_finish_compress or jpeg_start_decompress; those |
| 1938 | routines may take a long time to execute, and you don't get control back |
| 1939 | until they are done. |
| 1940 | |
| 1941 | You can define a progress-monitor routine which will be called periodically |
| 1942 | by the library. No guarantees are made about how often this call will occur, |
| 1943 | so we don't recommend you use it for mouse tracking or anything like that. |
| 1944 | At present, a call will occur once per MCU row, scanline, or sample row |
| 1945 | group, whichever unit is convenient for the current processing mode; so the |
| 1946 | wider the image, the longer the time between calls. (During the data |
| 1947 | transferring pass, only one call occurs per call of jpeg_read_scanlines or |
| 1948 | jpeg_write_scanlines, so don't pass a large number of scanlines at once if |
| 1949 | you want fine resolution in the progress count.) |
| 1950 | |
| 1951 | To establish a progress-monitor callback, create a struct jpeg_progress_mgr, |
| 1952 | fill in its progress_monitor field with a pointer to your callback routine, |
| 1953 | and set cinfo->progress to point to the struct. The callback will be called |
| 1954 | whenever cinfo->progress is non-NULL. (This pointer is set to NULL by |
| 1955 | jpeg_create_compress or jpeg_create_decompress; the library will not change |
| 1956 | it thereafter. So if you allocate dynamic storage for the progress struct, |
| 1957 | make sure it will live as long as the JPEG object does. Allocating from the |
| 1958 | JPEG memory manager with lifetime JPOOL_PERMANENT will work nicely.) You |
| 1959 | can use the same callback routine for both compression and decompression. |
| 1960 | |
| 1961 | The jpeg_progress_mgr struct contains four fields which are set by the library: |
| 1962 | long pass_counter; /* work units completed in this pass */ |
| 1963 | long pass_limit; /* total number of work units in this pass */ |
| 1964 | int completed_passes; /* passes completed so far */ |
| 1965 | int total_passes; /* total number of passes expected */ |
| 1966 | During any one pass, pass_counter increases from 0 up to (not including) |
| 1967 | pass_limit; the step size is not necessarily 1. Both the step size and the |
| 1968 | limit may differ from one pass to another. The expected total number of |
| 1969 | passes is in total_passes, and the number of passes already completed is in |
| 1970 | completed_passes. Thus the fraction of work completed may be estimated as |
| 1971 | completed_passes + (pass_counter/pass_limit) |
| 1972 | -------------------------------------------- |
| 1973 | total_passes |
| 1974 | ignoring the fact that the passes may not be equal amounts of work. |
| 1975 | |
| 1976 | When decompressing, the total_passes value is not trustworthy, because it |
| 1977 | depends on the number of scans in the JPEG file, which isn't always known in |
| 1978 | advance. In the current implementation, completed_passes may jump by more |
| 1979 | than one when dealing with a multiple-scan input file. About all that is |
| 1980 | really safe to assume is that when completed_passes = total_passes - 1, the |
| 1981 | current pass will be the last one. |
| 1982 | |
| 1983 | If you really need to use the callback mechanism for time-critical tasks |
| 1984 | like mouse tracking, you could insert additional calls inside some of the |
| 1985 | library's inner loops. |
| 1986 | |
| 1987 | |
| 1988 | Memory management |
| 1989 | ----------------- |
| 1990 | |
| 1991 | This section covers some key facts about the JPEG library's built-in memory |
| 1992 | manager. For more info, please read structure.doc's section about the memory |
| 1993 | manager, and consult the source code if necessary. |
| 1994 | |
| 1995 | All memory and temporary file allocation within the library is done via the |
| 1996 | memory manager. If necessary, you can replace the "back end" of the memory |
| 1997 | manager to control allocation yourself (for example, if you don't want the |
| 1998 | library to use malloc() and free() for some reason). |
| 1999 | |
| 2000 | Some data is allocated "permanently" and will not be freed until the JPEG |
| 2001 | object is destroyed. Most data is allocated "per image" and is freed by |
| 2002 | jpeg_finish_compress, jpeg_finish_decompress, or jpeg_abort. You can call the |
| 2003 | memory manager yourself to allocate structures that will automatically be |
| 2004 | freed at these times. Typical code for this is |
| 2005 | ptr = (*cinfo->mem->alloc_small) ((j_common_ptr) cinfo, JPOOL_IMAGE, size); |
| 2006 | Use JPOOL_PERMANENT to get storage that lasts as long as the JPEG object. |
| 2007 | Use alloc_large instead of alloc_small for anything bigger than a few Kbytes. |
| 2008 | There are also alloc_sarray and alloc_barray routines that automatically |
| 2009 | build 2-D sample or block arrays. |
| 2010 | |
| 2011 | The library's minimum space requirements to process an image depend on the |
| 2012 | image's width, but not on its height, because the library ordinarily works |
| 2013 | with "strip" buffers that are as wide as the image but just a few rows high. |
| 2014 | Some operating modes (eg, two-pass color quantization) require full-image |
| 2015 | buffers. Such buffers are treated as "virtual arrays": only the current strip |
| 2016 | need be in memory, and the rest can be swapped out to a temporary file. |
| 2017 | |
| 2018 | If you use the simplest memory manager back end (jmemnobs.c), then no |
| 2019 | temporary files are used; virtual arrays are simply malloc()'d. Images bigger |
| 2020 | than memory can be processed only if your system supports virtual memory. |
| 2021 | The other memory manager back ends support temporary files of various flavors |
| 2022 | and thus work in machines without virtual memory. They may also be useful on |
| 2023 | Unix machines if you need to process images that exceed available swap space. |
| 2024 | |
| 2025 | When using temporary files, the library will make the in-memory buffers for |
| 2026 | its virtual arrays just big enough to stay within a "maximum memory" setting. |
| 2027 | Your application can set this limit by setting cinfo->mem->max_memory_to_use |
| 2028 | after creating the JPEG object. (Of course, there is still a minimum size for |
| 2029 | the buffers, so the max-memory setting is effective only if it is bigger than |
| 2030 | the minimum space needed.) If you allocate any large structures yourself, you |
| 2031 | must allocate them before jpeg_start_compress() or jpeg_start_decompress() in |
| 2032 | order to have them counted against the max memory limit. Also keep in mind |
| 2033 | that space allocated with alloc_small() is ignored, on the assumption that |
| 2034 | it's too small to be worth worrying about. |
| 2035 | |
| 2036 | If you use the jmemname.c or jmemdos.c memory manager back end, it is |
| 2037 | important to clean up the JPEG object properly to ensure that the temporary |
| 2038 | files get deleted. (This is especially crucial with jmemdos.c, where the |
| 2039 | "temporary files" may be extended-memory segments; if they are not freed, |
| 2040 | DOS will require a reboot to recover the memory.) Thus, with these memory |
| 2041 | managers, it's a good idea to provide a signal handler that will trap any |
| 2042 | early exit from your program. The handler should call either jpeg_abort() |
| 2043 | or jpeg_destroy() for any active JPEG objects. A handler is not needed with |
| 2044 | jmemnobs.c, and shouldn't be necessary with jmemansi.c either, since the C |
| 2045 | library is supposed to take care of deleting files made with tmpfile(). |
| 2046 | |
| 2047 | |
| 2048 | Library compile-time options |
| 2049 | ---------------------------- |
| 2050 | |
| 2051 | A number of compile-time options are available by modifying jmorecfg.h. |
| 2052 | |
| 2053 | The JPEG standard provides for both the baseline 8-bit DCT process and |
| 2054 | a 12-bit DCT process. 12-bit lossy JPEG is supported if you define |
| 2055 | BITS_IN_JSAMPLE as 12 rather than 8. Note that this causes JSAMPLE to be |
| 2056 | larger than a char, so it affects the surrounding application's image data. |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 2057 | The sample applications cjpeg and djpeg can support 12-bit mode only for PPM |
| 2058 | and GIF file formats; you must disable the other file formats to compile a |
Thomas G. Lane | a8b67c4 | 1995-03-15 00:00:00 +0000 | [diff] [blame^] | 2059 | 12-bit cjpeg or djpeg. (install.doc has more information about that.) |
| 2060 | At present, a 12-bit library can handle *only* 12-bit images, not both |
| 2061 | precisions. (If you need to include both 8- and 12-bit libraries in a single |
| 2062 | application, you could probably do it by defining NEED_SHORT_EXTERNAL_NAMES |
| 2063 | for just one of the copies. You'd have to access the 8-bit and 12-bit copies |
| 2064 | from separate application source files. This is untested ... if you try it, |
| 2065 | we'd like to hear whether it works!) |
| 2066 | |
| 2067 | Note that a 12-bit library always compresses in Huffman optimization mode, |
| 2068 | in order to generate valid Huffman tables. This is necessary because our |
| 2069 | default Huffman tables only cover 8-bit data. If you need to output 12-bit |
| 2070 | files in one pass, you'll have to supply suitable default Huffman tables. |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 2071 | |
| 2072 | The maximum number of components (color channels) in the image is determined |
| 2073 | by MAX_COMPONENTS. The JPEG standard allows up to 255 components, but we |
| 2074 | expect that few applications will need more than four or so. |
| 2075 | |
| 2076 | On machines with unusual data type sizes, you may be able to improve |
| 2077 | performance or reduce memory space by tweaking the various typedefs in |
| 2078 | jmorecfg.h. In particular, on some RISC CPUs, access to arrays of "short"s |
| 2079 | is quite slow; consider trading memory for speed by making JCOEF, INT16, and |
| 2080 | UINT16 be "int" or "unsigned int". UINT8 is also a candidate to become int. |
| 2081 | You probably don't want to make JSAMPLE be int unless you have lots of memory |
| 2082 | to burn. |
| 2083 | |
| 2084 | You can reduce the size of the library by compiling out various optional |
| 2085 | functions. To do this, undefine xxx_SUPPORTED symbols as necessary. |
| 2086 | |
| 2087 | |
| 2088 | Portability considerations |
| 2089 | -------------------------- |
| 2090 | |
| 2091 | The JPEG library has been written to be extremely portable; the sample |
| 2092 | applications cjpeg and djpeg are slightly less so. This section summarizes |
| 2093 | the design goals in this area. (If you encounter any bugs that cause the |
| 2094 | library to be less portable than is claimed here, we'd appreciate hearing |
| 2095 | about them.) |
| 2096 | |
| 2097 | The code works fine on both ANSI and pre-ANSI C compilers, using any of the |
| 2098 | popular system include file setups, and some not-so-popular ones too. See |
| 2099 | install.doc for configuration procedures. |
| 2100 | |
| 2101 | The code is not dependent on the exact sizes of the C data types. As |
| 2102 | distributed, we make the assumptions that |
| 2103 | char is at least 8 bits wide |
| 2104 | short is at least 16 bits wide |
| 2105 | int is at least 16 bits wide |
| 2106 | long is at least 32 bits wide |
| 2107 | (These are the minimum requirements of the ANSI C standard.) Wider types will |
| 2108 | work fine, although memory may be used inefficiently if char is much larger |
| 2109 | than 8 bits or short is much bigger than 16 bits. The code should work |
| 2110 | equally well with 16- or 32-bit ints. |
| 2111 | |
| 2112 | In a system where these assumptions are not met, you may be able to make the |
| 2113 | code work by modifying the typedefs in jmorecfg.h. However, you will probably |
| 2114 | have difficulty if int is less than 16 bits wide, since references to plain |
| 2115 | int abound in the code. |
| 2116 | |
| 2117 | char can be either signed or unsigned, although the code runs faster if an |
| 2118 | unsigned char type is available. If char is wider than 8 bits, you will need |
| 2119 | to redefine JOCTET and/or provide custom data source/destination managers so |
| 2120 | that JOCTET represents exactly 8 bits of data on external storage. |
| 2121 | |
| 2122 | The JPEG library proper does not assume ASCII representation of characters. |
| 2123 | But some of the image file I/O modules in cjpeg/djpeg do have ASCII |
| 2124 | dependencies in file-header manipulation; so does cjpeg's select_file_type() |
| 2125 | routine. |
| 2126 | |
| 2127 | The JPEG library does not rely heavily on the C library. In particular, C |
| 2128 | stdio is used only by the data source/destination modules and the error |
| 2129 | handler, all of which are application-replaceable. (cjpeg/djpeg are more |
| 2130 | heavily dependent on stdio.) malloc and free are called only from the memory |
| 2131 | manager "back end" module, so you can use a different memory allocator by |
| 2132 | replacing that one file. |
| 2133 | |
| 2134 | The code generally assumes that C names must be unique in the first 15 |
| 2135 | characters. However, global function names can be made unique in the |
| 2136 | first 6 characters by defining NEED_SHORT_EXTERNAL_NAMES. |
| 2137 | |
| 2138 | More info about porting the code may be gleaned by reading jconfig.doc, |
| 2139 | jmorecfg.h, and jinclude.h. |
| 2140 | |
| 2141 | |
| 2142 | Notes for MS-DOS implementors |
| 2143 | ----------------------------- |
| 2144 | |
| 2145 | The IJG code is designed to work efficiently in 80x86 "small" or "medium" |
| 2146 | memory models (i.e., data pointers are 16 bits unless explicitly declared |
| 2147 | "far"; code pointers can be either size). You may be able to use small |
| 2148 | model to compile cjpeg or djpeg by itself, but you will probably have to use |
| 2149 | medium model for any larger application. This won't make much difference in |
| 2150 | performance. You *will* take a noticeable performance hit if you use a |
| 2151 | large-data memory model (perhaps 10%-25%), and you should avoid "huge" model |
| 2152 | if at all possible. |
| 2153 | |
| 2154 | The JPEG library typically needs 2Kb-3Kb of stack space. It will also |
| 2155 | malloc about 20K-30K of near heap space while executing (and lots of far |
| 2156 | heap, but that doesn't count in this calculation). This figure will vary |
| 2157 | depending on selected operating mode, and to a lesser extent on image size. |
Thomas G. Lane | 9ba2f5e | 1994-12-07 00:00:00 +0000 | [diff] [blame] | 2158 | There is also about 5Kb-6Kb of constant data which will be allocated in the |
| 2159 | near data segment (about 4Kb of this is the error message table). |
| 2160 | Thus you have perhaps 20K available for other modules' static data and near |
Thomas G. Lane | 36a4ccc | 1994-09-24 00:00:00 +0000 | [diff] [blame] | 2161 | heap space before you need to go to a larger memory model. The C library's |
| 2162 | static data will account for several K of this, but that still leaves a good |
| 2163 | deal for your needs. (If you are tight on space, you could reduce the sizes |
| 2164 | of the I/O buffers allocated by jdatasrc.c and jdatadst.c, say from 4K to |
| 2165 | 1K.) |
| 2166 | |
| 2167 | About 2K of the near heap space is "permanent" memory that will not be |
| 2168 | released until you destroy the JPEG object. This is only an issue if you |
| 2169 | save a JPEG object between compression or decompression operations. |
| 2170 | |
| 2171 | Far data space may also be a tight resource when you are dealing with large |
| 2172 | images. The most memory-intensive case is decompression with two-pass color |
| 2173 | quantization, or single-pass quantization to an externally supplied color |
| 2174 | map. This requires a 128Kb color lookup table plus strip buffers amounting |
| 2175 | to about 50 bytes per column for typical sampling ratios (eg, about 32000 |
| 2176 | bytes for a 640-pixel-wide image). You may not be able to process wide |
| 2177 | images if you have large data structures of your own. |
| 2178 | |
| 2179 | Of course, all of these concerns vanish if you use a 32-bit flat-memory-model |
| 2180 | compiler, such as DJGPP or Watcom C. We highly recommend flat model if you |
| 2181 | can use it; the JPEG library is significantly faster in flat model. |