Lines Matching refs:jpeg_write_scanlines

123                 jpeg_write_scanlines(...);
135 The image data to be compressed is supplied to jpeg_write_scanlines() from
383         jpeg_write_scanlines(...);
385 Now write all the required image data by calling jpeg_write_scanlines()
415             jpeg_write_scanlines(&cinfo, row_pointer, 1);
418 jpeg_write_scanlines() returns the number of scanlines actually written.
1721 compressor to return to the caller of jpeg_write_scanlines(), with the return
1724 buffer pointer/count appropriately, and then call jpeg_write_scanlines()
1740 call jpeg_write_scanlines() unless there is a reasonable amount of space in
1915 into a buffer array as jpeg_write_scanlines() is called, and will emit all
2516 call to jpeg_write_scanlines().  When you do this, the markers appear after
2658 before the first call to jpeg_write_scanlines() or jpeg_write_raw_data().  This
2710 jpeg_write_scanlines().  Before calling jpeg_start_compress(), you must do
2724 jpeg_write_scanlines().  The two routines work similarly except that
2851 jpeg_start_compress() and jpeg_write_scanlines().  Thus the sequence is
2895 (the jpeg_read_scanlines or jpeg_write_scanlines loop), any additional passes
2907 jpeg_write_scanlines, so don't pass a large number of scanlines at once if