Tryag File Manager

//proc/self/root/usr/share/doc/ImageMagick-6.2.8/www/miff.html

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
 <style type="text/css"></style>
 <title>ImageMagick: Magick Image File Format</title>
 <meta http-equiv="Content-Language" content="en-US"/>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
 <meta http-equiv="Reply-to" content="magick-users@imagemagick.org"/>
 <meta name="Generator" content="PHP"/>
 <meta name="Keywords" content="magick, image, file, format, ImageMagick, PerlMagick, Magick++, Image, Magick"/>
 <meta name="Description" content="ImageMagick (TM) is a free software suite to create, edit and compose bitmap images. It can read, convert and write images in a large variety of formats. Images can be cropped, colors can be changed, various effects can be applied, images can be rotated and combined, and text, lines, polygons, ellipses and Bézier curves can be added to images and stretched and rotated. ImageMagick is free software: it is delivered with full source code and can be freely used, copied, modified and distributed. Its license is compatible with the GPL. It runs on all major operating systems. Most of the functionality of ImageMagick can be used interactively from the command line; more often, however, the features are used from programs written in the programming languages Perl, C, C++, Python, PHP, Ruby or Java, for which ready-made ImageMagick interfaces (PerlMagick, Magick++, PythonMagick, MagickWand for PHP, RubyMagick, and JMagick) are available. This makes it possible to modify or create images automatically and dynamically. ImageMagick supports many image formats (over 90 major formats) including popular formats like TIFF, JPEG, PNG, PDF, PhotoCD, and GIF."/>
 <meta name="Rating" content="GENERAL"/>
 <meta name="Robots" content="INDEX, FOLLOW"/>
 <meta name="Generator" content="ImageMagick Studio LLC"/>
 <meta name="Author" content="ImageMagick Studio LLC"/>
 <meta name="Revisit-after" content="2 DAYS"/>
 <meta name="Resource-type" content="document"/>
 <meta name="Copyright" content="Copyright (c) 1999-2006 ImageMagick Studio LLC"/>
 <meta name="Distribution" content="Global"/>
 <link rel="shortcut icon" href="/../images/wand.ico" type="image/x-icon"/>
</head>

<tr valign="top" style="height: 100%;">
 <td id="menu" width="1%" height="100%">
 <a href="#main">Skip to page contents</a>
 [
 <a href="../index.html">About ImageMagick</a>
 <a href="../www/command-line-tools.html">Command-line Tools</a>
 <a href="../www/command-line-processing.html" class="sub">Processing</a>
 <a href="../www/command-line-options.html" class="sub">Options</a>
 <a href="../www/api.html">Program Interfaces</a>
 <a href="../www/magick-wand.html" class="sub">MagickWand</a>
 <a href="../www/magick-core.html" class="sub">MagickCore</a>
 <a href="../www/perl-magick.html" class="sub">PerlMagick</a>
 <a href="../www/architecture.html">Architecture</a>
 ] [
 <a href="../www/install-source.html">Install from Source</a>
 <a href="../www/install-source.html#unix" class="sub">Unix</a>
 <a href="../www/install-source.html#windows" class="sub">Windows</a>
 <a href="../www/binary-releases.html">Binary Releases</a>
 <a href="../www/binary-releases.html#unix" class="sub">Unix</a>
 <a href="../www/binary-releases.html#windows" class="sub">Windows</a>
 <a href="../www/resources.html">Resources</a>
 ] [
 <a href="../www/download.html">Download</a>
 ] [
 <a href="../www/links.html">Links</a>
 ] [
 <a href="../www/sponsors.html">Sponsors</a>
 <a href="http://www.webservertalk.com" class="sponsor" target="sponsor">Server Administration Support Forum</a>
 ]
 </td>

<td id="main" valign="top">
[<a href="#header">MIFF Header</a> | <a href="#binary">MIFF Binary Data</a>]

The Magick Image File Format (MIFF) is ImageMagick's own platform-independent format for storing bitmap images. It has an advantage over other image formats in that it stores all metadata known to ImageMagick (e.g. image color profiles, comments, author, copyright, etc.), whereas, other formats may only support a small portion of available metadata or none at all. A MIFF image file consist of two sections. The first section is a header composed of keys describing the image in text form. The next section is the binary image data. We discuss these sections in detail below.

<div style="margin: auto;">
 <h2><a name="header"></a>MIFF Header</h2>
</div>

The MIFF header is composed entirely of ISO-8859-1 characters. The fields
in the header are key and value combination in the key = value format, with each key and value separated by an equal sign (<kbd>=</kbd>). Each key = value combination is delimited by at least one control or whitespace character. Comments may appear in the header section and are always delimited by braces. The MIFF header always ends with a colon (<kbd>:</kbd>) character, followed by a ctrl-Z character. It is also common to proceed the colon with a formfeed and a newline character. The formfeed prevents the listing of binary data when using the <kbd>more</kbd> Unix program, whereas, the ctrl-Z has the same effect with the <kbd>type</kbd> command on the Windows command line.

The following is a partial list of key = value combinations that are typically be found in a MIFF file:

<ul>
<dt>background-color = color<dt>
<dt>border-color = color</dt>
<dt>matte-color = color</dt>
 <dd>these optional keys reflect the image background, border, and matte colors respectively. A <a href="../www/color.html">color</a> can be a name (e.g. white) or a hex value (e.g. #ccc).</dd> 
<dt>class = DirectClass</dt>
<dt>class = PseudoClass</dt>
 <dd>the type of binary pixel data stored in the MIFF file. If this key is not present, DirectClass pixel data is assumed.</dd> 
<dt>colors = value</dt>
 <dd>the number of colors in a DirectClass image. For a PseudoClass image, this key specifies the number of entires in the colormap. If this key is not present in the header, and the image is PseudoClass, a linear 256 color grayscale colormap is is assumed. The maximum number of colormap entries is 65536.</dd> 
<dt>colorspace = RGB</dt>
<dt>colorspace = CMYK</dt>
 <dd>the colorspace of the pixel data. The default is RGB.</dd> 
<dt>columns = value</dt>
 <dd>the width of the image in pixels. This is a required key and has no default value.</dd> 
<dt>compression = BZip</dt>
<dt>compression = Fax</dt>
<dt>compression = None</dt>
<dt>compression = RLE</dt>
<dt>compression = Zip</dt>
 <dd>the type of algorithm used to compress the image data. If this key is not present, the pixel data is assumed to be uncompressed.</dd> 
<dt>delay = microseconds</dt>
 <dd>the interframe delay in an image sequence in microseconds.</dd> 
<dt>depth = 8</dt>
<dt>depth = 16</dt>
<dt>depth = 32</dt>
 <dd>the depth of a single color value representing values from 0 to 255 (depth 8), 0 - 65535 (depth 16), or 0 - 4294967295 (depth 32). If this key is absent, a depth of 8 is assumed.</dd> 
<dt>dispose = value</dt>
 <dd>GIF disposal method.</dd> 
 <dd>Here are the valid methods:<dd>

<dd><ul>
 <dd>0. No disposal specified.</dd>
 <dd>1. Do not dispose between frames.</dd>
 <dd>2. Overwrite frame with background color from header.</dd>
 <dd>3. Overwrite with previous frame.</dd>
</ul></dd><dd>

<dt>gamma = value</dt>
 <dd>the gamma of the image. If it is not specified, a gamma of 1.0 (linear brightness response) is assumed.</dd>

<dt>id = ImageMagick</dt>
 <dd>identifies the file as a MIFF-format image file. This key is required and has no default. Although this key can appear anywhere in the header, it should start as the first key of the header in column 1. This will allow programs like <kbd>file</kbd>(1) to easily identify the file as MIFF.</dd>

<dt>iterations = value</dt>
 <dd>the number of times an image sequence loops before stopping.</dd>

<dt>label = { string }</dt>
 <dd>defines a short title or caption for the image. If any whitespace appears in the label, it must be enclosed within braces.</dd>

<dt>matte = True</dt>
<dt>matte = False</dt>
 <dd>specifies whether a the image has matte data. Matte data is generally useful for image compositing.</dt>

<dt>montage = &lt;width&gt;x&lt;height&gt;{+-}&lt;x offset&gt;{+-}&lt;y offset&gt;</dt>
 <dd>size and location of the individual tiles of a composite image.</dd>

<dd>Use this key when the image is a composite of a number of different tiles. A tile consists of an image and optionally a border and a label. Width is the size in pixels of each individual tile in the horizontal direction and height is the size in the vertical direction. Each tile must have an equal number of pixels in width and equal in height. However, the width can differ from the height. X offset is the offset in number of pixels from the vertical edge of the composite image where the first tile of a row begins and y offset is the offset from the horizontal edge where the first tile of a column begins.</dd>

<dd>If this key is specified, a directory of tile names must follow the image header. The format of the directory is explained below.</dd>

<dt>page = value</dt>
 <dd>preferred size and location of an image canvas.</dd>

<dt>profile-icc = value</dt>
 <dd>the number of bytes in the International Color Consortium color profile. The profile is defined by the ICC profile specification located at <a href="ftp://sgigate.sgi.com/pub/icc/icc34.ps">ftp://sgigate.sgi.com/pub/icc/icc34.ps</a>.</dd>

<dt>red-primary = x,y</dt>
<dt>green-primary = x,y</dt>
<dt>blue-primary = x,y</dt>
<dt>white-point = x,y</dt>
 <dd>this optional key reflects the chromaticity primaries and white point.</dd>

<dt>rendering-intent = saturation</dt>
<dt>rendering-intent = perceptual</dt>
<dt>rendering-intent = absolute</dt>
<dt>rendering-intent = relative</dt>
 <dd>Rendering intent is the CSS-1 property that has been defined by the International Color Consortium (<a href="http://www.color.org">http://www.color.org</a>).</dd>

<dt>resolution = &lt;x-resolution&gt;x&lt;y-resolution&gt;</dt>
 <dd>vertical and horizontal resolution of the image. See units for the specific resolution units (e.g. pixels per inch).</dd>

<dt>rows = value</dt>
 <dd>the height of the image in pixels. This is a required key and has no default value.</dd>

<dt>scene = value</dt>
 <dd>the sequence number for this MIFF image file. This optional key is useful when a MIFF image file is one in a sequence of files used in an animation.</dd>

<dt>signature = value</dt>
 <dd>this optional key contains a string that uniquely identifies the image pixel contents. NIST's SHA-256 message digest algorithm is recommended.</dd>

<dt>units = pixels-per-inch</dt>
<dt>units = pixels-per-centimeter</dt>
 <dd>image resolution units.</dd>
</ul>

Other key value pairs are permitted. If a value contains whitespace it must be enclosed with braces as illustrated here:

<pre class="text">
 id=ImageMagick
 class=PseudoClass colors=256 matte=False
 columns=1280 rows=1024 depth=8
 compression=RLE
 colorspace=RGB
 copyright={Copyright (c) 1999-2006 ImageMagick Studio LLC}
 <FF>
 :
</pre>

Note that key = value combinations may be separated by newlines or spaces and may occur in any order within the header. Comments (within braces) may appear anywhere before the colon.

If you specify the montage key in the header, follow the header with a directory of image tiles. This directory consists of a name for each tile of the composite image separated by a newline character. The list is terminated with a NULL character.

If you specify the color-profile key in the header, follow the header (or montage directory if the montage key is in the header) with the binary color profile.

The header is separated from the image data by a <kbd>:</kbd> character immediately followed by a newline.

<div style="margin: auto;">
 <h2><a name="binary"></a>MIFF Binary Data</h2>
</div>

Next comes the binary image data itself. How the image data is formatted depends upon the class of the image as specified (or not specified) by the value of the class key in the header.

DirectClass images are continuous-tone, images stored as RGB (red, green, blue), RGBA (red, green, blue, alpha), CMYK (cyan, yellow, magenta, black), or CMYKA (cyan, yellow, magenta, black, alpha) intensity values as defined by the colorspace key. Each intensity value is one byte in length for images of depth 8 (0..255), two bytes for a depth of 16 (0..65535), and images of depth 32 (0..4294967295) require four bytes in most significant byte first order.

PseudoClass images are colormapped RGB images. The colormap is stored as a series of red, green, and blue pixel values, each value being a byte in size. If the image depth is 16, each colormap entry consumes two bytes with the most significant byte being first. The number of colormap entries is defined by the colors key. The colormap data occurs immediately following the header (or image directory if the montage key is in the header). PseudoClass image data is an array of index values into the color map. If there are 256
or fewer colors in the image, each byte of image data contains an index value. If the image contains more than 256 colors or the image depth is 16, the index value is stored as two contiguous bytes with the most significant byte being first. If matte is true, each colormap index is followed by a 1 or 2-byte alpha value.

The image pixel data in a MIFF file may be uncompressed, runlength encoded, Zip compressed, or BZip compressed. The compression key in the header defines how the image data is compressed. Uncompressed pixels are stored one scanline at a time in row order. Runlength-encoded compression counts runs of identical adjacent pixels and stores the pixels followed by a length byte (the number of identical pixels minus 1). Zip and BZip compression compresses each row of an image and precedes the compressed row with the length of compressed pixel bytes as a word in most significant byte first order.

MIFF files may contain more than one image. Simply concatenate each individual image (composed of a header and image data) into one file.
 </td>
 <td id="margin" width="1%" height="100%" valign="top" align="right">&nbsp;</td>
 </tr>
 </tbody>
 </table>
 <div id="linkbar">
 <a href="http://redux.imagemagick.org/discussion-server" target="263402580">Discourse Server</a> |
 <a href="../www/mailing-list.html">Mailing Lists</a> |
 <a href="http://redux.imagemagick.org/gallery" target="1209915705">Image Gallery</a> |
 <a href="http://studio.webbyland.com/MagickStudio/scripts/MagickStudio.cgi" target="307053884">ImageMagick Studio</a>
 </div>
 <div>
 &copy; 1999-2006 ImageMagick Studio LLC
 </div>
 <div style="clear: both; margin: 0; width: 100%; "></div>
</body>
</html>