| /external/libmtp/logs/ |
| mtp-detect-nokia-lumia-630.txt | 466 380d: TIFF
[all...] |
| mtp-detect-nokia-lumia-820.txt | 456 380d: TIFF
[all...] |
| mtp-detect-nokia-n9.txt | 142 380d: TIFF
[all...] |
| /external/ImageMagick/ImageMagick/script/ |
| binary-releases.html | 261 <li>tiff</li>
|
| porting.html | 272 <p>In version 7, we introduce pixel user channels. Traditionally we utilize 4 channels, red, green, blue, and alpha. For CMYK we also have a black channel. User channels are designed to contain whatever additional channel information that makes sense for your application. Some examples include extra channels in TIFF or PSD images or perhaps you require a channel with infrared information for the pixel. You can associate traits with the user channels so that they when they are acted upon by an image processing algorithm (e.g. blur) the pixels are copied, acted upon by the algorithm, or even blended with the alpha channel if that makes sense.</p>
[all...] |
| architecture.html | 61 <p>An image typically consists of a rectangular region of pixels and metadata. To convert, edit, or compose an image in an efficient manner we need convenient access to any pixel anywhere within the region (and sometimes outside the region). And in the case of an image sequence, we need access to any pixel of any region of any image in the sequence. However, there are hundreds of image formats such JPEG, TIFF, PNG, GIF, etc., that makes it difficult to access pixels on demand. Within these formats we find differences in:</p>
97 <p>ImageMagick consists of nearly a half million lines of C code and optionally depends on several million lines of code in dependent libraries (e.g. JPEG, PNG, TIFF libraries). Given that, one might expect a huge architecture document. However, a great majority of image processing is simply accessing pixels and its metadata and our simple, elegant, and efficient implementation makes this easy for the ImageMagick developer. We discuss the implementation of the pixel cache and getting and setting image properties and profiles in the next few sections. Next, we discuss using ImageMagick within a <a href="architecture.php#threads">thread</a> of execution. In the final sections, we discuss <a href="architecture.php#coders">image coders</a> to read or write a particular image format followed by a few words on creating a <a href="architecture.php#filters">filter</a> to access or update pixels based on your custom requirements.</p>
[all...] |
| command-line-processing.html | 159 the better known JPEG, PNG, TIFF and others. ImageMagick must know the format
[all...] |
| /external/ImageMagick/config/ |
| config.h.in | 935 /* Define if you have TIFF library */
|
| /external/ImageMagick/www/ |
| binary-releases.html | 258 <li>tiff</li>
|
| porting.html | 276 <p>In version 7, we introduce pixel user channels. Traditionally we utilize 4 channels, red, green, blue, and alpha. For CMYK we also have a black channel. User channels are designed to contain whatever additional channel information that makes sense for your application. Some examples include extra channels in TIFF or PSD images or perhaps you require a channel with infrared information for the pixel. You can associate traits with the user channels so that they when they are acted upon by an image processing algorithm (e.g. blur) the pixels are copied, acted upon by the algorithm, or even blended with the alpha channel if that makes sense.</p>
[all...] |
| architecture.html | 65 <p>An image typically consists of a rectangular region of pixels and metadata. To convert, edit, or compose an image in an efficient manner, we need convenient access to any pixel anywhere within the region (and sometimes outside the region). And in the case of an image sequence, we need access to any pixel of any region of any image in the sequence. However, there are hundreds of image formats such JPEG, TIFF, PNG, GIF, etc., that makes it difficult to access pixels on demand. Within these formats we find differences in:</p>
101 <p>ImageMagick consists of nearly a half million lines of C code and optionally depends on several million lines of code in dependent libraries (e.g. JPEG, PNG, TIFF libraries). Given that, one might expect a huge architecture document. However, a great majority of image processing is simply accessing pixels and its metadata and our simple, elegant, and efficient implementation makes this easy for the ImageMagick developer. We discuss the implementation of the pixel cache and getting and setting image properties and profiles in the next few sections. Next, we discuss using ImageMagick within a <a href="architecture.html#threads">thread</a> of execution. In the final sections, we discuss <a href="architecture.html#coders">image coders</a> to read or write a particular image format followed by a few words on creating a <a href="architecture.html#filters">filter</a> to access or update pixels based on your custom requirements.</p>
[all...] |
| command-line-processing.html | 163 the better known JPEG, PNG, TIFF and others. ImageMagick must know the format
[all...] |
| /external/dng_sdk/source/ |
| dng_shared.cpp | 1042 // Read header. Like a TIFF header, but with different magic number
[all...] |
| dng_parse_utils.cpp | 270 { tcTIFF_EP_StandardID, "TIFF/EPStandardID" },
[all...] |
| dng_read_image.cpp | [all...] |
| /external/swiftshader/src/Reactor/ |
| SubzeroLLVMDependencies.vcxproj.filters | 14 <Extensions>rc;ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe;resx;tiff;tif;png;wav;mfcribbon-ms</Extensions>
|
| /frameworks/av/media/libstagefright/httplive/ |
| M3UParser.cpp | [all...] |
| /frameworks/native/headers/media_plugin/media/openmax/ |
| OMX_AsString.h | 334 case OMX_IMAGE_CodingTIFF: return "TIFF"; // unused
[all...] |
| /frameworks/opt/telephony/tests/telephonytests/src/com/android/internal/telephony/ |
| Wap230WspContentTypeTest.java | 69 WELL_KNOWN_SHORT_MIME_TYPES.put(0x1F, "image/tiff");
[all...] |
| /external/ImageMagick/ |
| Makefile.in | 528 coders/tiff.c coders/webp.c coders/wmf.c coders/x.c \
[all...] |
| /external/ImageMagick/MagickCore/ |
| magick-baseconfig.h | [all...] |
| /external/google-breakpad/src/client/mac/sender/ |
| Breakpad.xib | 360 <string>NeXT TIFF v4.0 pasteboard type</string>
[all...] |
| /external/opencv/ |
| NOTICE | [all...] |
| /external/ImageMagick/Magick++/ |
| ChangeLog | 445 endian option for formats which support this notion (e.g. TIFF).
448 for formats which support this notion (e.g. TIFF).
[all...] |
| /external/ImageMagick/coders/ |
| psd.c | 669 (void) SetImageProperty(image,"tiff:XResolution",value,exception);
676 (void) SetImageProperty(image,"tiff:YResolution",value,exception);
[all...] |
