| /external/opencv3/3rdparty/libwebp/utils/ |
| filters.c | 55 // Leftmost pixel is predicted from above (except for topmost scanline).
|
| /external/opencv3/3rdparty/openexr/IlmImf/ |
| ImfScanLineInputFile.h | 149 void readPixels (int scanLine);
|
| ImfEnvmap.h | 48 // Environment maps can be stored in scanline-based or in tiled
64 // dataWindow parameter. For scanline-based images, and for
|
| /external/pdfium/core/src/fpdfapi/fpdf_render/ |
| fpdf_render_loadimage.cpp | 751 uint8_t* scanline = (uint8_t*)m_pCachedBitmap->GetScanline(row); local
753 *scanline = (*scanline) >> scale;
754 ++scanline;
[all...] |
| /external/skia/dm/ |
| DMSrcSink.h | 113 kCroppedScanline_Mode, // Tests (jpeg) cropped scanline optimization
|
| /external/skia/src/codec/ |
| SkCodec.cpp | 257 // We only support subsetting in the x-dimension for scanline decoder.
|
| SkBmpRLECodec.cpp | 265 // FIXME: Support subsets for scanline decodes.
343 // success, but we may be performing a scanline decode, which
|
| /external/skia/src/effects/gradients/ |
| Sk4fGradientBase.cpp | 245 // Linear search, using the last scanline interval as a starting point.
|
| /external/webp/src/dsp/ |
| filters.c | 57 // Leftmost pixel is the same as input for topmost scanline.
|
| /hardware/qcom/camera/QCamera2/stack/common/ |
| cam_types.h | 195 /* Note: For all raw formats, each scanline needs to be 16 bytes aligned */
498 int32_t scanline; member in struct:__anon32665
502 int32_t meta_scanline; /*Meta Scanline*/
[all...] |
| /hardware/qcom/camera/QCamera2/stack/mm-camera-test/src/ |
| mm_qcamera_rdi.c | 185 buf_planes->plane_info.mp[0].stride, buf_planes->plane_info.mp[0].scanline,
|
| /packages/apps/Camera2/src/com/android/camera/util/ |
| JpegUtilNative.java | 61 * rendered in scanline order. Only rotations which are multiples of
|
| /device/huawei/angler/camera/QCamera2/stack/mm-jpeg-interface/test/ |
| mm_jpeg_test.c | 287 p_params->src_main_buf[i].offset.mp[0].scanline = p_input->height;
298 p_params->src_thumb_buf[i].offset.mp[0].scanline = p_input->height;
|
| /device/lge/bullhead/camera/QCamera2/stack/mm-jpeg-interface/test/ |
| mm_jpeg_test.c | 287 p_params->src_main_buf[i].offset.mp[0].scanline = p_input->height;
298 p_params->src_thumb_buf[i].offset.mp[0].scanline = p_input->height;
|
| /device/moto/shamu/camera/QCamera2/stack/mm-jpeg-interface/test/ |
| mm_jpeg_test.c | 285 p_params->src_main_buf[i].offset.mp[0].scanline = p_input->height;
296 p_params->src_thumb_buf[i].offset.mp[0].scanline = p_input->height;
|
| /external/ImageMagick/ImageMagick/script/ |
| architecture.html | 78 <li>a single scanline (e.g. all pixels from row 4)</li>
134 <p>As you can see, the convenience of the pixel cache sometimes comes with a trade-off in storage (e.g. storing a 1-bit monochrome image as 16-bit RGBA is wasteful) and speed (i.e. storing the entire image in memory is generally slower than accessing one scanline of pixels at a time). In most cases, the benefits of the pixel cache typically outweigh any disadvantages.</p>
204 <p>The pixel cache manager decides whether to give you direct or indirect access to the image pixels. In some cases the pixels are staged to an intermediate buffer-- and that is why you must call SyncAuthenticPixels() to ensure this buffer is <var>pushed</var> out to the pixel cache to guarantee the corresponding pixels in the cache are updated. For this reason we recommend that you only read or update a scanline or a few scanlines of pixels at a time. However, you can get any rectangular region of pixels you want. GetAuthenticPixels() requires that the region you request is within the bounds of the image area. For a 640 by 480 image, you can get a scanline of 640 pixels at row 479 but if you ask for a scanline at row 480, an exception is returned (rows are numbered starting at 0). GetVirtualPixels() does not have this constraint. For example,</p>
341 <p>GetVirtualPixels(), GetAuthenticPixels(), QueueAuthenticPixels(), and SyncAuthenticPixels(), from the MagickCore API, can only deal with one pixel cache area per image at a time. Suppose you want to access the first and last scanline from the same image at the same time? The solution is to use a <var>cache view</var>. A cache view permits you to access as many areas simultaneously in the pixel cache as you require. The cache view <a href="../api/cache-view.php">methods</a> are analogous to the previous methods except you must first open a view and close it when you are finished with it. Here is a snippet of MagickCore code that permits us to access the first and last pixel row of the image simultaneously:</p>
373 <p>Although you can request any pixel from the pixel cache, any block of pixels, any scanline, multiple scanlines, any row, or multiple rows with the GetVirtualPixels(), GetAuthenticPixels(), QueueAuthenticPixels, GetCacheViewVirtualPixels(), GetCacheViewAuthenticPixels(), and QueueCacheViewAuthenticPixels() methods, ImageMagick is optimized to return a few pixels or a few pixels rows at time. There are additional optimizations if you request a single scanline or a few scanlines at a time. These methods also permit random access to the pixel cache, however, ImageMagick is optimized for sequential access. Although you can access scanlines of pixels sequentially from the last row of the image to the first, you may get a performance boost if you access scanlines from the first row of the image to the last, in sequential order.</p>
[all...] |
| /external/ImageMagick/www/ |
| architecture.html | 82 <li>a single scanline (e.g. all pixels from row 4)</li>
138 <p>As you can see, the convenience of the pixel cache sometimes comes with a trade-off in storage (e.g. storing a 1-bit monochrome image as 16-bit is wasteful) and speed (i.e. storing the entire image in memory is generally slower than accessing one scanline of pixels at a time). In most cases, the benefits of the pixel cache typically outweigh any disadvantages.</p>
208 <p>The pixel cache manager decides whether to give you direct or indirect access to the image pixels. In some cases the pixels are staged to an intermediate buffer-- and that is why you must call SyncAuthenticPixels() to ensure this buffer is <var>pushed</var> out to the pixel cache to guarantee the corresponding pixels in the cache are updated. For this reason we recommend that you only read or update a scanline or a few scanlines of pixels at a time. However, you can get any rectangular region of pixels you want. GetAuthenticPixels() requires that the region you request is within the bounds of the image area. For a 640 by 480 image, you can get a scanline of 640 pixels at row 479 but if you ask for a scanline at row 480, an exception is returned (rows are numbered starting at 0). GetVirtualPixels() does not have this constraint. For example,</p>
351 <p>GetVirtualPixels(), GetAuthenticPixels(), QueueAuthenticPixels(), and SyncAuthenticPixels(), from the MagickCore API, can only deal with one pixel cache area per image at a time. Suppose you want to access the first and last scanline from the same image at the same time? The solution is to use a <var>cache view</var>. A cache view permits you to access as many areas simultaneously in the pixel cache as you require. The cache view <a href="api/cache-view.html">methods</a> are analogous to the previous methods except you must first open a view and close it when you are finished with it. Here is a snippet of MagickCore code that permits us to access the first and last pixel row of the image simultaneously:</p>
383 <p>Although you can request any pixel from the pixel cache, any block of pixels, any scanline, multiple scanlines, any row, or multiple rows with the GetVirtualPixels(), GetAuthenticPixels(), QueueAuthenticPixels, GetCacheViewVirtualPixels(), GetCacheViewAuthenticPixels(), and QueueCacheViewAuthenticPixels() methods, ImageMagick is optimized to return a few pixels or a few pixels rows at time. There are additional optimizations if you request a single scanline or a few scanlines at a time. These methods also permit random access to the pixel cache, however, ImageMagick is optimized for sequential access. Although you can access scanlines of pixels sequentially from the last row of the image to the first, you may get a performance boost if you access scanlines from the first row of the image to the last, in sequential order.</p>
[all...] |
| /external/opencv3/3rdparty/libjpeg/ |
| change.log | 364 scanline-by-scanline basis.
|
| /external/opencv3/3rdparty/libtiff/ |
| tif_predict.c | 91 * Calculate the scanline/tile-width size in bytes.
406 * Decode a scanline and apply the predictor routine.
|
| /external/pdfium/third_party/libtiff/ |
| tif_predict.c | 93 * Calculate the scanline/tile-width size in bytes.
414 * Decode a scanline and apply the predictor routine.
|
| /hardware/qcom/camera/QCamera2/stack/mm-jpeg-interface/src/ |
| mm_jpegdec.c | 317 (OMX_U32)p_src_buf->offset.mp[0].scanline;
584 p_params->dest_buf[p_jobparams->dst_index].offset.mp[0].scanline;
|
| /hardware/qcom/camera/QCamera2/stack/mm-jpeg-interface/test/ |
| mm_jpeg_test.c | 355 p_params->src_main_buf[i].offset.mp[0].scanline = p_input->height;
366 p_params->src_thumb_buf[i].offset.mp[0].scanline = p_input->height;
|
| /external/ImageMagick/MagickCore/ |
| image-view.c | 176 % parallel and calls your transfer method for each scanline of the view. The
509 % your get method for each scanline of the view. The pixel extent is
[all...] |
| /external/ImageMagick/MagickWand/ |
| wand-view.c | 224 % parallel and calls your transfer method for each scanline of the view. The
495 % your get method for each scanline of the view. The pixel extent is
[all...] |
| /external/libgdx/gdx/jni/gdx2d/ |
| stb_image.h | 5909 stbi_uc *scanline; local
[all...] |
