>   "I swear by my life and my love of it that I will never live?    for the sake of another man, nor ask another man to live for     mine"  >                     John Galt in "Atlas Shrugged", by Ayn Rand     AUTHOR  @   The author is magick@wizards.dupont.com.  This software is NOT@   shareware.  However, I am interested in who might be using it.E   Please consider sending me a picture postcard of the area where you    live.  Send postcards to       John Cristy      P.O. Box 40      Landenberg, PA  19350      USA   L   I'm also interested in receiving coins or stamps from around the world for   my collection.     AVAILABILITY     ImageMagick is available as   I     ftp://ftp.wizards.dupont.com/pub/ImageMagick/ImageMagick-5.1.0.tar.gz   F   ImageMagick client executables are available for some platforms. See  9     ftp://ftp.wizards.dupont.com/pub/ImageMagick/binaries 4     ftp://ftp.wizards.dupont.com/pub/ImageMagick/mac3     ftp://ftp.wizards.dupont.com/pub/ImageMagick/nt 4     ftp://ftp.wizards.dupont.com/pub/ImageMagick/vms6     ftp://ftp.wizards.dupont.com/pub/ImageMagick/linux  A   I want ImageMagick to be of high quality, so if you encounter a F   problem I will investigate.  However, be sure you are using the mostB   recent version from ftp://ftp.wizards.dupont.com/pub/ImageMagickH   before submitting any bug reports or suggestions.  Report any problems)   via the web-based reporting facility at 5   http://www.simplesystems.org/ImageMagick/bugs.html.      WWW   &   The official ImageMagick WWW page is  9     http://www.wizards.dupont.com/cristy/ImageMagick.html   ?   To use display as your external image viewer, edit the global G   mail-cap file or your personal mail-cap file .mailrc (located at your %   home directory) and put this entry:        image/*; display %s      MAILING LIST  ?   There is a mailing list for discussions and bug reports about -   ImageMagick.  To subscribe send the message        subscribe magick  F   to majordomo@wizards.dupont.com.  You will receive a welcome message3   which tells you how to post messages to the list,    magick@wizards.dupont.com.     MEMORY REQUIREMENTS   A   You should allocate sufficient swap space on your system before E   running ImageMagick; otherwise, you may experience random server or G   application crashes. Anything less than 80 megabytes of swap space is !   likely to cause random crashes.   F   On many systems, you will find that 80 megabytes is insufficient andE   you will have to allocate more swap space.  You should also have at D   least 32 megabytes of real memory although 64 megabytes or more is   recommended.     UNIX/Cygwin COMPILATION      Type:   1     gzip -dc ImageMagick-5.0.0.tar.gz | tar xvf -      cd ImageMagick-5.0.0  2   If you do not have gunzip(1), it is available as*   prep.ai.mit.edu:pub/gnu/gzip-1.2.4.shar.  E   There are currently two mechanisms available to create makefiles to H   build ImageMagick: 1) GNU configure;  2: X11 imake.  Each is described   in the following paragraphs.     * * *      GNU configure:  E     This option is easiest to use and is recommended when ImageMagick G     is to be installed outside of the X11 distribution or working imake F     configuration files are not available.  Use of 'configure' enablesF     automated configuration, building, and installation of PerlMagick.  C     If you are willing to accept configure's default options, type:            ./configure   A     and watch the configure script output to verify that it finds D     everything that you think it should. If it does not, then adjust%     your environment so that it does.   =     If you are not happy with configure's choice of compiler, E     compilation flags, or libraries, you can give `configure' initial E     values for variables by setting them in the environment.  Using a E     Bourne-compatible shell, you can do that on the command line like 	     this:   2         CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure  G     Or on systems that have the `env' program, you can do it like this:   @         env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure  7     The configure variables you should be aware of are:   =         CC          Name of C compiler (e.g. 'cc -Xa') to use B         CFLAGS      Compiler flags (e.g. '-g -O2') to compile withG         CPPFLAGS    Include paths (-I/somedir) to look for header files D         LDFLAGS     Library paths (-L/somedir) to look for libraries@                     Systems that support the notion of a libraryC                     run-path may additionally require -R/somedir or G                     '-rpath /somedir' in order to find shared libraries                       at run time.@         LIBS        Extra libraries (-lsomelib) required to link  F     Any variable (e.g. CPPFLAGS or LDFLAGS) which requires a directoryC     path must specify an absolute path rather than a relative path.   B     By default, `make install' will install the package's files in@     `/usr/local/bin', `/usr/local/man', etc.  You can specify anE     installation prefix other than `/usr/local' by giving `configure'      the option `--prefix=PATH'.   >     Configure can usually find the X include and library filesA     automatically, but if it doesn't, you can use the `configure' G     options `--x-includes=DIR' and `--x-libraries=DIR' to specify their      locations.  B     The configure script provides a number of ImageMagick specificH     options.  When disabling an option --disable-something is equivalentB     to specifying --enable-something=no and --without-something isD     equivalent to --with-something=no.  The configure options are as<     follows (execute 'configure --help' to see all options).  A       --enable-shared      build shared libraries (default is no) B       --enable-static      build static libraries (default is yes)=       --enable-lzw         enable LZW support (default is no) ?       --enable-16bit-pixel enable 16 bit pixels (default is no) C       --enable-socks       enable use of SOCKS 5 library and 'rftp' H       --with-frozenpaths   enable frozen delegate paths (default is yes)N       --with-perl          enable build/install of PerlMagick (default is yes)8       --with-bzlib         enable BZlib (default is yes)E       --with-dps           enable Display Postscript (default is yes) ;       --with-fpx           enable FlashPIX (default is yes) 6       --with-hdf           enable HDF (default is yes)7       --with-jbig          enable JBIG (default is yes) 7       --with-jpeg          enable JPEG (default is yes) 6       --with-png           enable PNG (default is yes)7       --with-tiff          enable TIFF (default is yes) ;       --with-ttf           enable TrueType (default is yes) 7       --with-zlib          enable Zlib (default is yes) 2       --with-x             use the X Window System  B     ImageMagick options represent either features to be enabled orD     packages to be included in the build.  When a feature is enabled@     (via --enable-something), it enables code already present inG     ImageMagick.  When a package is enabled (via --with-something), the >     configure script will search for it, and if is is properlyE     installed and ready to use (headers and built libraries are found H     by compiler) it will be included in the build.  The configure scriptD     is delivered with all features disabled and all packages enabledG     (except for PERL). In general, the only reason to disable a package F     is if a package exists but it is unsuitable for the build (perhapsE     an old version or not compiled with the right compilation flags).   3     Several configure options require special note:   ?       o --enable-shared: the shared libraries are built. Shared D         libraries are valuable because they are *shared* across moreF         than one invocation of an ImageMagick or PerlMagick client. InB         addition, the clients take much less disk space and sharedH         libraries are required in order for PERL to dynamically load the         PerlMagick extension.   H         ImageMagick built with delegates (see MAGICK PLUG-INS below) canD         pose additional challenges.  You can build all the delegatesD         statically and link them into the ImageMagick shared libraryH         (i.e. libMagick.so) or alternatively you can build the delegates@         as shared libraries (some systems already have delegatesE         installed as shared libraries).  Shared libraries compilation F         flags differ from vendor to vendor (gcc's is -fPIC).  However,E         you must compile all shared library source with the same flag .         (for gcc use -fPIC rather than -fpic).  F       o --disable-static: static archive libraries (with extension .a)F         are not built.  If you are building shared libraries, there isC         little value to building static libraries. Reasons to build H         static libraries include: 1) they can be easier to debug; 2) theF         clients do not have external dependencies (i.e. libMagick.so);C         3) building PIC versions of the delegate libraries may take C         additional expertise and effort; 4) you are unable to build          shared libraries.   D       o --without-frozenpaths: By default, the configure script willG         determine the location of all delegates (external programs) and F         incorporate the full paths within the delegates.mgk file. ThisA         is the default because it is assumed that the installer's F         environment is appropriately configured and that the operation>         of ImageMagick should not be subject to the end-user'sG         environment. However, if it is desireable to allow the end user G         to define their own environment or possible that the end user's H         environment does not match the installer's environment (e.g. forH         binary distributions), --without-frozenpaths may be specified soF         that only the delegate's name is included in the delegates.mgk
         file.   G       o --without-perl: By default, PerlMagick is conveniently compiled H         and installed in one step. When --without-perl is specified, you@         must first install ImageMagick, change to the PerlMagickB         subdirectory, build, and finally install PerlMagick. Note,H         PerlMagick is configured even if --without-perl is specified. If@         --enable-shared is not specified, a new PERL interpreterD         (PerlMagick) is built which is statically linked against the?         PerlMagick extension. This new interpreter is installed G         alongside your existing PERL interpreter. If --enable-shared is E         specified, the PerlMagick extension is built as a dynamically >         loadable object which is loaded into your current PERLH         interpreter at run-time. Use of dynamically-loaded extensions isG         preferable over statically linked extensions so --enable-shared 8         should be specified if possible. If the argumentF         --with-perl=/path/to/perl is supplied, then /path/to/perl will0         be taken as the PERL interpreter to use.  F       o --without-x: By default, ImageMagick will use X11 libraries ifH         they are available. When --without-x is specified, use of X11 isC         disabled. The display, animate, and import programs are not ?         built or installed. The remaining programs have reduced D         functionality such as no access to X11 fonts (consider using.         Postscript or TrueType fonts instead).       Building under Cygwin   >       ImageMagick may be built under the Windows NT/'9X Cygwin=       Unix-emulation environment which may be downloaded from @       http://sourceware.cygnus.com/cygwin/. Pre-compiled X11R6.4-       libraries for Cygwin are available from E       http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.4/. Use the E       same procedure as for Unix except that building DLLs is not yet F       supported so do not specify --enable-shared option to configure.  (     Dealing with configuration failures:  F       While configure is designed to ease installation of ImageMagick,E       it often discovers problems that would otherwise be encountered F       later when compiling ImageMagick. The configure script tests forC       headers and libraries by executing the compiler (CC) with the ?       specified compilation flags (CFLAGS), pre-processor flags F       (CPPFLAGS), and linker flags (LDFLAGS). Any errors are logged toG       the file 'config.log'. If configure fails to discover a header or D       library please review this log file to determine why, however,H       please be aware that *errors in the config.log are normal* becauseD       configure works by trying something and seeing if it fails. AnC       error in config.log is only a problem if the test should have H       worked on your system.. After taking corrective action, be sure toE       remove the 'config.cache' file before running configure so that H       configure will re-inspect the environment rather than using cached
       values.   I       Common causes of configure falures are: 1) a delegate header is not D       in the header include path (CPPFLAGS -I option); 2) a delegateA       library is not in the linker search/run path (LDFLAGS -L/-R ?       option); 3) a delegate library is missing a function (old 6       version?); 4) compilation environment is faulty.  B       If all reasonable corrective actions have been tried and theB       problem appears to be due to a flaw in the configure script,A       please send a bug report to the configure script maintainer F       (currently bfriesen@simple.dallas.tx.us). All bug reports shouldG       contain the operating system type (as reported by 'uname -a') and C       the compiler/compiler-version. A copy of the configure script H       output and/or the config.log file may be valuable in order to findF       the problem. If you send a config.log, please also send a scriptG       of the configure output and a description of what you expected to F       see (and why) so the failure you are observing can be identified       and resolved.      * * *      X11 Imake:  G     Use this option if working imake configuration files are available, C     the package is to be installed where ever imake installs things @     (usually the X11 distribution directory), and you don't mind@     editing a configuration file.  Use of this scheme requires aC     seperate step to install PerlMagick (see the README file in the      PerlMagick subdirectory).   =     Edit Magick.tmpl and set the variables to suit your local      environment.  Now type:            ./configure 
         xmkmf          make Makefiles       or just            ./configure          xmkmf -a  A     if you are using X11R6 imake.  Here, GNU configure is used to 0     initialize the delegates/delegates.mgk file.     * * *   ;   To confirm your build of the ImageMagick distribution was    successful, type:   
       display   H   If the program faults ensure that you have not inadvertingly linked toF   an older version of the libMagick library. To ensure this is not the   case type          cd ImageMagick/magick        make install       cd .. 
       make  7   If the image colors are not correct use this command:          display -visual default   B   Be sure to read the manual pages for the display(1), animate(1),A   montage(1), import(1), mogrify(1), identify(1), combine(1), and B   convert(1) utilities. Also read the ImageMagick frequently askedG   questions in the file www/Magick.html. This is required reading. Most A   of the questions I get via electronic mail are answered in this    document.   ,   Place display(1) X application defaults in>   /usr/lib/X11/app-defaults/Display.  Use the appropriate nameH   for other clients (e.g. Animate, Montage, etc).  To execute display(1)F   from as a menu item of any window manager (olwm, mwm, twm, etc), use         logo:Untitled      MAGICK DELEGATES  =   To further enhance the capabilities of ImageMagick, you may *   want to get these programs or libraries:  1     o ImageMagick requires the BZLIB library from   7           http://sourceware.cygnus.com/bzip2/index.html   4       to read and write BZip compressed MIFF images.  &     o ImageMagick requires ralcgm from  5           http://www.agocg.ac.uk/train/cgm/ralcgm.htm   J       to read the Computer Graphics Metafile image format (may not compile;       under linux).  You also need Ghostscript (see below).   '     o ImageMagick requires fig2dev from   E           ftp://ftp.x.org/contrib/applications/drawing_tools/transfig   (       to read the TransFig image format.  G     o ImageMagick requires the FreeType software, version 1.1 or above,        available as  !          http://www.freetype.org/   &       to annotate with TrueType fonts.  >     o ImageMagick requires Ghostscript software available from  '          http://www.cs.wisc.edu/~ghost/   I       to read the Postscript or the Portable Document format.  It is used F       to annotate an image when an X server is not available.  See theK       FreeType library above for another means to annotate an image.  Note, H       Ghostscript must support the ppmraw device (type gs -h to verify).H       If Ghostscript is unavailable, the Display Postscript extension isK       used to rasterize a Postscript document (assuming you define HasDPS). L       The DPS extension is less robust than Ghostscript in that it will only2       rasterize one page of a multi-page document.  :     o ImageMagick requires the FlashPix SDK available from  >           http://www.kodak.com/US/en/drg/productsTechnologies/"             prodTechFlashPix.shtml  -       to read and write the FPX image format.   K     o ImageMagick requires the NCSA HDF library available via anonymous FTP        as  5           ftp://ftp.ncsa.uiuc.edu/HDF/HDF/HDF_Current   -       to read and write the HDF image format.   /     o ImageMagick requires hp2xx available from   6           http://www.gnu.org/software/hp2xx/hp2xx.html  %       to read the HP-GL image format.   A     o ImageMagick requires gnuplot available via anonymous FTP as   >           ftp://ftp.dartmouth.edu/pub/gnuplot/gnuplot3.5.tar.Z  7       to read GNUPLOT plot files (with extension gplt).   1     o ImageMagick requires html2ps available from   5           http://www.tdb.uu.se/~jan/html2ps-1.0b1.zip   $       to read the HTML image format.  H     o ImageMagick requires the JBIG-Kit software available via anonymous       FTP as  @           ftp://ftp.informatik.uni-erlangen.de/pub/doc/ISO/JBIG/             jbigkit-1.1.tar.gz  $       to read the JBIG image format.  @     o ImageMagick requires the Independent JPEG Group's software$       available via anonymous FTP as  ;           ftp://ftp.uu.net/graphics/jpeg/jpegsrc.v6b.tar.gz   $       to read the JPEG image format.  N       Apply this JPEG patch to Independent JPEG Group's source distribution to.       read lossless jpeg-encoded DICOM images:  A           ftp://ftp.wizards.dupont.com/pub/ImageMagick/delegates/              ljpeg-6b.tar.gz   ?       Concerning iterative JPEG compression:  see Kinoshita and A       Yamamuro, Journal of Imaging Science and Technology, "Image F       Quality with Reiterative JPEG Compression", Volume 39, Number 4,G       July 1995, 306-312 who claim that (1) the iterative factor of the F       repetitive JPEG operation had no influence on image quality, and>       (2) the first compression determined base image quality.  9     o ImageMagick requires the MPEG library available via        anonymous FTP as  C           ftp://ftp.mpeg.org/pub/mpeg/mssg/mpeg2vidcodec_v12.tar.gz   -       to read or write the MPEG image format.   F     o ImageMagick requires the PNG library, version 1.0 or above, from  3           http://www.cdrom.com/pub/png/pngcode.html   #       to read the PNG image format.   ;     o ImageMagick requires ra_ppm from Greg Ward's Radiance -       software available via anonymous FTP as   3           http://radsite.lbl.gov/radiance/HOME.html   F       to read the Radiance image format (may not compile under linux).  @     o ImageMagick requires rawtorle from the Utah Raster Toolkit$       available via anonymous FTP as  2           ftp://ftp.cs.utah.edu/pub/urt-3.1b.tar.Z  B       to write the RLE image format (may not compile under linux).  )     o ImageMagick requires scanimage from   &           http://www.mostang.com/sane/  ,       to import image from a scanner device.  @     o ImageMagick requires Sam Leffler's TIFF software available       via anonymous FTP as  !           http://www.libtiff.org/   D       to read the TIFF image format.  It in turn optionally requires"       the JPEG and ZLIB libraries.  2     o ImageMagick requires wmftogif available from  7           http://www.csn.ul.ie/~caolan/docs/libwmf.html   1       to read the Windows Meta File image format.   :     o ImageMagick requires GET(1) available via the Web as  #           http://www.linpro.no/lwp/   B       to read images specified with a World Wide Web (WWW) uniformD       resource locator (URL).  If you do not have a HTTP server, youD       can use xtp(1), available in the ImageMagick distribution, for"       URL's whose protocol is FTP.  F     o ImageMagick requires an X server for display and animate to workJ       properly.  There is a nearly free X server available for Windows and       Macintosh at  0         http://www.microimages.com/freestuf/mix/  0     o ImageMagick requires the ZLIB library from  :           http://www.cdrom.com/pub/infozip/zlib/index.html  =       to read or write the PNG or Zip compressed MIFF images.   C     o ImageMagick requires SOCKS version 5 available via the Web at   #           http://www.socks.nec.com/   C       in order for 'xtp' to work across a SOCKS5-based firewall. In A       particular, 'xtp' makes use of SOCKS5 'rftp' as an external C       program and supports use of the SOCKS5 library to perform DNS C       lookups via the firewall rather than the internal DNS server.   <     o ImageMagick requires a background texture for the TILE@       format and for the -texture option of montage(1).  You can&       use your own or get samples from  &           http://the-tech.mit.edu/KPT/     HOW TO COMPILE  B   NOTE: The following procedure describes how to build ImageMagickE   extension libraries in subdirectories of the ImageMagick directory. A   An alternative to these procedures is to install one or more of C   these under your system's regular include/lib directory (e.g. the C   directory specified by --prefix to configure or /usr/local). This E   allows the libraries to be shared by other packages. When using the C   configure script, the two schemes may be mixed. Also, please note A   that when the configure option --enable-shared is not disabled, A   these procedures must be supplemented with whatever compilation E   flags are required on your system to generate PIC code. In the case E   of gcc, this usually means that -fPIC must be added to the compiler <   options (i.e. CFLAGS) when building each delegate library.  =   To display images in the HDF, JBIG, JPEG, PNG, TIFF, or TTF G   format, get the respective archives and build ImageMagick as follows:   
     BZLIB:       cd ImageMagick0       gunzip -c bzip2-0.9.5d.tar.gz | tar xvof -       mv bzip2-0.9.5d bzlib        cd bzlib
       make       cd ..        HDF:       cd ImageMagick+       gunzip -c HDF4.1r3.tar.gz | tar xvf -        mv HDF4.1r3 hdf        cd hdf       configure        make -k hdf-libnofortran       cd ..   	     JBIG:        cd ImageMagick/       gunzip -c jbigkit-1.1.tar.gz | tar xvof -        mv jbigkit jbig 
       cd jbig 
       make       cd ..   	     JPEG:        cd ImageMagick/       gunzip -c jpegsrc.v6b.tar.gz | tar xvof -        mv jpeg-6b jpeg 
       cd jpeg        configure 
       make       cd ..        PNG:       cd ImageMagick,       gunzip -c libpng-1.0.5.tgz | tar xvf -       mv libpng-1.0.5 png        cd png
       make       cd ..   	     TIFF:        cd ImageMagick/       gunzip -c tiff-v3.5.2.tar.gz | tar xvof -        mv tiff-v3.5.2 tiff 
       cd tiff        ./configure 
       make       cd ..        TTF:       cd ImageMagick0       gunzip -c freetype-1.3.tar.gz | tar xvof -       mv freetype-1.3 ttf        cd ttf!       ./configure -disable-shared 
       make       cd ..   	     ZLIB:        cd ImageMagick-       gunzip -c zlib-1.1.3.tar.gz | tar xvf -        mv zlib-1.1.3 zlib
       cd zlib 
       make       cd ..   <   If your computer system supports shared libraries you must   type         make install  8   Finally, perform the following if you are using Imake:         cd ImageMagick;       < edit Magick.tmpl and define Has???? as instructed >        xmkmf        make Makefiles       make clean
       make  1   If prefer to use 'configure' rather than Imake:          configure        make clean
       make -k   D   You can now convert or display images in the JPEG, TIFF, PNG, etc.   image formats.     VMS COMPILATION   C   You might want to check the values of certain program definitions D   before compiling.  Verify the definitions in delegates.mgk to suit'   your local requirements.  Next, type.      Type  !       unzip ImageMagick-5.0.0.zip         set default [.imagemagick]       @make )       set display/create/node=node_name::   4   where node_name is the DECNET X server to contact.     Finally type:   
       display   K   Alternatively, get a zipped distribution (with JPEG, PNG, TIFF, TTF) from   J       ftp://ftp.wizards.dupont.com/pub/ImageMagick/vms/ImageMagick-4.1.zip  E   The VMS JPEG, PNG, TIFF, and TTF  source libraries are available on .   axp.psl.ku.dk in [anonymous.decwindows.lib].  6   Thanks to pmoreau@cenaath.cena.dgac.fr for supplyingH   invaluable help as well as the VMS versions of the JPEG, PNG, TTF, and   TIFF libraries.     ( Windows NT/95 VISUAL C++ 6.0 COMPILATION  B   The Visual C++ distribution targeted at Windows NT or Windows 95E   is provided in the "VisualMagick" subdirectory of the distribution. A   There are two workspaces (DSW files) that can be used to do the    complete build:   @     VisualMagick.dsw : The one used to build everything as DLL's?     VisualMagickStatic.dsw: The one used to build everything as 8                             static standalone executable  7   A complete build can be accomplished by simply doing:        Build: Batch Build: Clean      Build: Batch Build: Build   B   The "Clean" step is needed in order to make sure that all of theA   target support libraries are updated with any patches needed to *   get them to compile properly on Windows.  E   All of the required files that are needed to run any of the command H   line tools will be found in the "bin" subdirectory of the VisualMagickD   subdirectory. This includes EXE, and DLL files. You should be ableB   to test the build directly from this directory without having toD   move anything to any of the global SYSTEM or SYSTEM32 areas in the    operating system installation.  B   NOTE: The two utilities "display" and "animate" will compile andE   link but not function in the default build environment. This is due C   to the fact that the default build environment uses the X11 stubs D   to supply non-functional stubs for X-Window functionality. This isB   due to the lack of a high need for this on a Windows NT or Win95D   only system. Work is underway to add X11 libraries to the standard"   distribution in the neat future.  /   To view any image in a Microsoft window, type          convert image.ext win:  @   Make sure gswin32 (Ghostscript) is in your execution path (seeA   Autoexec.bat), otherwise, you will be unable to convert or view    a Postscript document.  G   Make sure iexplore (Internet Explorer) is in your execution path (see H   Autoexec.bat), otherwise, you will be unable to browse the ImageMagick   documentation.  3   The NT executables will work under Windows 95/98.      MACINTOSH COMPILATION   <   The Macintosh distribution contains MetroWerks CodewarriorC   Professional projects for compilation.  For those who do not have D   access to CodeWarrior, the binaries for the command line utilitiesC   are enclosed.  I had to comment the inline intrinsic functions in D   math.h in order to compile.  If you have a better solution, let me   know.   D   Display(1), animate(1), and import(1) currently do not work on the   Macintosh.  G   I am looking for a volunteer to get display(1) and animate(1) to work A   on the Macintosh.  I also need a volunteer is needed to write a B   simple Mac program to call the libMagick routines and display an   image in a window.    	 ANIMATION   ;   To prevent color flashing on visuals that have colormaps, ?   animate(1) creates a single colormap from the image sequence. 8   This can be rather time consuming.  You can speed this=   operation up by reducing the colors in the image before you =   `animate' them.  Use mogrify(1) to color reduce the images:   0       mogrify +map -colors 256 scenes/dna.[0-9]*  F   Alternatively, you can use a Standard Colormap; or a static, direct,@   or true color visual.  You can define a Standard Colormap withA   xstdcmap(1).  For example, to use the "best" Standard Colormap,    type:          xstdcmap -best)       animate -map best scenes/dna.[0-9]*       or to use a true color visual:  1       animate -visual truecolor scenes/dna.[0-9]*   @   Image filenames can appear in any order on the command line if>   the scene keyword is specified in the MIFF image.  Otherwise<   the images display in the order they appear on the command@   line.  A scene is specified when converting from another image=   format to MIFF by using the "scene" option with any filter. 8   Be sure to choose a scene number other than zero.  For?   example, to convert a TIFF image to a MIFF image as scene #2,    type:   ,       convert -scene 2 image.tiff image.miff     16-BIT IMAGING  <   By default, ImageMagick uses a color depth of 8 bits (e.g.F   [0..255] for each of red, green, blue, and transparency components).B   Any 16-bit image is scaled to 8-bits before any image viewing orE   processing occurs.  If you want to work directly with 16-bit images C   (e.g. [0..65535]), edit Magick.tmpl and define QuantumLeap or use ,   -enable-16bit with configure.  Next, type:         make clean
       make  D   In 16-bit mode expect to use about 33% more memory on the average.C   Also expect some processing to be slower than in 8-bit mode (e.g.    Oil Painting, Segment, etc).  G   In general, 16-bit mode is only useful if you have 16-bit images that A   you want to manipulate and save the transformed image back to a '   16-bit image format (e.g. PNG, VIFF).      64-BIT MACHINES   C   Each pixel, within ImageMagick, is represented by the PixelPacket G   structure found in magick/image.h.  Only 8 bits are required for each E   color component and 16 bits for the colormap index for a total of 6 C   bytes.  If QuantumLeap is defined (see 16-BIT IMAGING above), the D   color component size increases to 16 bits for a total of 10 bytes.F   Some 64-bit machines pad the structure which can cause a significantB   waste of memory.  For the cray, change the PixelPacket structure	   to this   !       typedef struct _PixelPacket        {          unsigned char            red : QuantumDepth,            green : QuantumDepth,            blue : QuantumDepth,!           opacity : QuantumDepth;            unsigned short           index : 16;        } PixelPacket;     before compiling.   K   I'm not sure if this will work on other 64-bit machines that pad.  If you J   know a better solution, please send me E-mail.  Note, that the Dec AlphaH   apparently does not pad the structure so ImageMagick should be fine on!   this particular 64-bit machine.      Magick++  E   If you would like to build and install the Magick++ C++ programming ?   interface to ImageMagick, first build and install ImageMagick E   according to the instructions in this file (configure script method @   for Unix) and then build and install Magick++ according to theH   instructions in the README file in the Magick++ subdirectory. Magick++D   is currently supported using the egcs 1.1.1 version of GNU g++ (orH   later) under Unix and Microsoft Visual C++ under Windows NT or Windows   95/98.    	 COPYRIGHT   B   Copyright (C) 2000 ImageMagick Studio, a non-profit organizationB   dedicated to making software imaging solutions freely available.  G   Permission is hereby granted, free of charge, to any person obtaining <   a copy of this software and associated documentation files>   ("ImageMagick"), to deal in ImageMagick without restriction,F   including without limitation the rights to use, copy, modify, merge,E   publish, distribute, sublicense, and/or sell copies of ImageMagick, F   and to permit persons to whom the ImageMagick is furnished to do so,&   subject to the following conditions:  @   The above copyright notice and this permission notice shall be@   included in all copies or substantial portions of ImageMagick.  A   The software is provided "as is", without warranty of any kind, D   express or implied, including but not limited to the warranties of7   merchantability, fitness for a particular purpose and F   noninfringement.  In no event shall ImageMagick Studio be liable for@   any claim, damages or other liability, whether in an action ofD   contract, tort or otherwise, arising from, out of or in connection?   with ImageMagick or the use or other dealings in ImageMagick.   A   Except as contained in this notice, the name of the ImageMagick E   Studio shall not be used in advertising or otherwise to promote the B   sale, use or other dealings in ImageMagick without prior written,   authorization from the ImageMagick Studio.