Lines Matching full:marker
97 * DNL marker
915 One restart marker per MCU row is often a good choice.
939 If TRUE, a JFIF APP0 marker is emitted. jpeg_set_defaults() and
945 The version number to be written into the JFIF marker.
953 The resolution information to be written into the JFIF marker;
959 If TRUE, an Adobe APP14 marker is emitted. jpeg_set_defaults() and
1046 boolean saw_JFIF_marker TRUE if a JFIF APP0 marker was seen
1047 UINT8 JFIF_major_version Version information from JFIF marker
1049 UINT8 density_unit Resolution data from JFIF marker
1052 boolean saw_Adobe_marker TRUE if an Adobe APP14 marker was seen
1053 UINT8 Adobe_transform Color transform code from Adobe marker
1223 APPn marker of your own devising to identify the colorspace --- see "Special
1481 uninteresting data (such as an APPn marker). In some applications
1489 a restart (RSTn) marker where one is expected. Its mission is to
1506 In most cases, generating a warning message and inserting a fake EOI marker
1587 output buffer to emit any buffered data and the final EOI marker. In the
1644 pointer/count to point to a dummy EOI marker and then return TRUE just as
1648 instead it will backtrack to the start of the marker and reprocess the whole
1649 marker next time. Hence the input buffer must be large enough to hold the
1650 longest standard marker in the file. Standard JPEG markers should normally
1653 larger than any correct marker is likely to be. For robustness against
1654 damaged marker length counts, you may wish to insert a test in your
1666 Note that if you provide your own marker handling routine for large markers,
1820 advances to the next scan or end-of-image marker (hence input_scan_number
1845 JPEG_REACHED_SOS: reached an SOS marker (the start of a new scan)
1846 JPEG_REACHED_EOI: reached the EOI marker (end of image)
1853 events occurs. (If called after the EOI marker is reached, it will
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.)
2124 Once the first SOS marker has been reached, you must call
2316 datastream. The JPEG standard provides marker types "COM" (comment) and
2332 For program-supplied data, use an APPn marker, and be sure to begin it with an
2333 identifying string so that you can tell whether the marker is actually yours.
2338 Keep in mind that at most 65533 bytes can be put into one marker, but you
2341 By default, the IJG compression library will write a JFIF APP0 marker if the
2342 selected JPEG colorspace is grayscale or YCbCr, or an Adobe APP14 marker if
2352 all else. Specify the marker type parameter as "JPEG_COM" for COM or
2354 any marker type, but we don't recommend writing any other kinds of marker.)
2358 If it's not convenient to store all the marker data in memory at once,
2363 output buffer partway through a marker, which might be important when
2368 Or, if you prefer to synthesize the marker byte sequence yourself,
2373 correct JFIF version number in the JFIF header marker. The library's default
2387 data source; writing a marker processor that copes with input suspension is
2388 not easy (consider what happens if the marker is longer than your available
2389 input buffer). However, the second method conserves memory since the marker
2392 For either method, you'd normally set up marker handling after creating a
2395 be scanned by jpeg_read_header. Once you've established a marker handling
2397 (potentially many datastreams), unless you change it. Marker handling is
2398 determined separately for COM markers and for each APPn marker code.
2403 where marker_code is the marker type to save, JPEG_COM or JPEG_APP0+n.
2404 (To arrange to save all the special marker types, you need to call this
2405 routine 17 times, for COM and APP0-APP15.) If the incoming marker is longer
2408 first few bytes of a potentially large marker. If you want to save all the
2409 data, set length_limit to 0xFFFF; that is enough since marker lengths are only
2410 16 bits. As a special case, setting length_limit to 0 prevents that marker
2418 will not exceed length_limit for the particular marker type. Note that these
2419 lengths exclude the marker length word, whereas the stored representation
2424 SOS marker at which jpeg_read_header stops; if so, the marker list will be
2427 limit to zero for all marker types after finishing jpeg_read_header, to
2431 The marker list remains stored until you call jpeg_finish_decompress or
2444 If you want to supply your own marker-reading routine, you do it by calling
2445 jpeg_set_marker_processor(). A marker processor routine must have the
2448 Although the marker code is not explicitly passed, the routine can find it
2449 in cinfo->unread_marker. At the time of call, the marker proper has been
2451 reading the marker length word and the remaining parameter bytes, if any.
2454 marker processors in jdmarker.c for appropriate coding methods if you need to
2460 want to do that. (A better idea is to save these marker types for later
2466 particular marker type specified.
