Lines Matching refs:In
19 In this document, JPEG-specific terminology follows the JPEG standard:
141 In addition to these modules we need overall control, marker generation,
181 only to the next block (8-sample) boundary. In an interleaved-scan situation,
252 and decompression libraries. In IJG implementations prior to v5, overall
300 * In some processing modes, a given interstep buffer need only be a "strip"
301 buffer large enough to accommodate the desired data chunk sizes. In other
307 In theory, we might be able to make all of the data buffer controllers
308 interchangeable and provide just one set of implementations for all. In
380 In addition to the above objects, the compression library includes these
438 to make context rows available. In the current design, the main buffer is
485 always be a single component representing colormap indexes. In the current
499 In addition to the above objects, the decompression library includes these
540 section needs more data.) In this way the application can avoid making
620 In general, a specific sample value is accessed by code such as
654 depending on where the block is in the processing pipeline. In the current
679 In some applications it is desirable to use the JPEG library as an
680 incremental, memory-to-memory filter. In this situation the data source or
693 be prepared to stop at arbitrary times. In turn, the controllers that call
716 In a successive-approximation AC refinement scan, the progressive Huffman
752 In all cases, allocated objects are tied to a particular compression or
794 In the present implementation, virtual arrays are only permitted to have image
801 In a non-virtual-memory machine, some performance benefit can be gained by
805 of the buffers to fit within a prespecified maximum memory usage. In order
828 In a virtual-memory machine, we simply pretend that the available space is
903 In these files the SOF marker claims the image height is 0, and you only
914 In cases where image-size data structures are allocated, this approach will