Lines Matching full:scan
119 while (scan lines remain to be written)
146 while (scan lines remain to be read)
379 5. while (scan lines remain to be written)
624 to complete. With a single-scan (non progressive) JPEG file and default
655 6. while (scan lines remain to be read)
868 Generates a default scan script for writing a progressive-JPEG file.
870 unless you want to make a custom scan sequence. You must ensure that
924 single-scan sequential JPEG file. If not NULL, scan_info points to
925 an array of scan definition records of length num_scans. The
926 compressor will then write a JPEG file having one scan for each scan
928 progressive JPEG files. The library checks that the scan array
929 defines a valid JPEG scan sequence. (jpeg_simple_progression creates
930 a suitable scan definition array for progressive JPEG.) This is
1594 Huffman code optimization and multiple-scan output. Those modes write the
1706 quickly from the first scan, then gradually improve the displayed quality as
1714 suitable "scan script" defining how to divide the data into scans.
1724 Each displayed scan requires about as much work to decode as a full JPEG
1739 To create a progressive JPEG file (or a multiple-scan sequential JPEG file),
1740 set the scan_info cinfo field to point to an array of scan descriptors, and
1741 perform compression as usual. Instead of constructing your own scan list,
1745 progressive scan sequence design. (If you want to provide user control of
1746 scan sequences, you may wish to borrow the scan script reading code found
1747 in rdswitch.c, so that you can read scan script files just like cjpeg's.)
1751 multiple-scan output cannot be created with a suspending data destination
1760 a multi-scan file during jpeg_start_decompress(), so that it can provide a
1761 final decoded image. (Here "multi-scan" means either progressive or
1762 multi-scan sequential.) This makes multi-scan files transparent to the
1777 but it can be used with any JPEG file. Each scan of a progressive JPEG file
1779 display in lockstep with the source file (one display pass per input scan),
1810 pass for each scan appearing in the input file. In this case the outer loop
1815 The second parameter to jpeg_start_output() indicates which scan of the input
1818 the library's input scan counter is easier.) The library automatically reads
1819 data as necessary to complete each requested scan, and jpeg_finish_output()
1820 advances to the next scan or end-of-image marker (hence input_scan_number
1825 After reading the final scan and reaching the end of the input file, the
1834 In general the last scan of a progressive file cannot be recognized as such
1845 JPEG_REACHED_SOS: reached an SOS marker (the start of a new scan)
1848 JPEG_SCAN_COMPLETED: completed reading last MCU row of current scan
1874 When input arrives fast enough that more than one new scan is available
1876 corresponding to the completed scan. This occurs for free if you pass
1877 cinfo.input_scan_number as the target scan number to jpeg_start_output().
1878 The input_scan_number field is simply the index of the scan currently being
1884 The target scan number passed to jpeg_start_output() is saved in the
1886 jpeg_consume_input() whenever the current input scan number and row within
1887 that scan is less than or equal to the current output scan number and row.
1890 manipulating this interlock rule. For example, if you pass a target scan
1891 number greater than the current input scan number, the output processor will
1892 wait until that scan starts to arrive before producing any output. (To avoid
1893 an infinite loop, the target scan number is automatically reset to the last
1894 scan number when the end of image is reached. Thus, if you specify a large
1895 target scan number, the library will just absorb the entire input file and
1898 When you pass a target scan number equal to the current input scan number,
1899 the image is displayed no faster than the current input scan arrives. The
1900 final possibility is to pass a target scan number less than the current input
1901 scan number; this disables the input/output interlock and causes the output
1903 waiting for input. (However, the library will not accept a target scan
1904 number less than one, so you can't avoid waiting for the first scan.)
1910 the point where the input is more than one whole scan ahead of the output.
1914 Then, when the next output scan is started, you have a choice of what target
1915 scan number to use. The recommended choice is to use the current input scan
1918 previous output scan. In this way, the decoder automatically adapts its
1950 pass was performed in sync with the final input scan. This form of the loop
1963 scan arrives during an output pass; this can be detected by noting
1972 the current input scan number for the output target scan number; if a
1976 the parameters of the current input scan and decide whether to display it or
1977 not. If the scan contains only chroma data, one might choose not to use it
1978 as the target scan, expecting that the scan will be small and will arrive
1979 quickly. To skip to the next scan, call jpeg_consume_input() until it
1981 number as the target scan for jpeg_start_output(); but that method doesn't
1982 let you inspect the next scan's parameters before deciding to display it.
1990 and the target scan isn't fully read yet. (This is discussed below.)
1993 * jpeg_finish_output() will read any markers following the target scan,
1994 up to the end of the file or the SOS marker that begins another scan.
1996 end of the file or a SOS marker beyond the target output scan.)
2013 to a higher quality method for the final scan.
2024 During the first DC-only scan, block smoothing provides a very "fuzzy" look
2090 important to realize that if the specified target scan number is greater than
2091 or equal to the current input scan number, jpeg_start_output() will attempt
2095 target scan is the only case in which jpeg_start_output() will consume input.
2099 for all JPEG images, even single-scan ones. This will work, but it is
2101 single-scan images. Requesting buffered-image mode for such an image wastes
2828 3. A full-image DCT coefficient buffer is needed to decode a multi-scan JPEG
