  "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.
  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

  I'm also interested in receiving coins or stamps from around the world for
  my collection.


AVAILABILITY

  ImageMagick is available as

    ftp://ftp.wizards.dupont.com/pub/ImageMagick/ImageMagick-5.1.1.tar.gz

  ImageMagick client executables are available for some platforms. See

    ftp://ftp.wizards.dupont.com/pub/ImageMagick/binaries
    ftp://ftp.wizards.dupont.com/pub/ImageMagick/mac
    ftp://ftp.wizards.dupont.com/pub/ImageMagick/nt
    ftp://ftp.wizards.dupont.com/pub/ImageMagick/vms
    ftp://ftp.wizards.dupont.com/pub/ImageMagick/linux

  I want ImageMagick to be of high quality, so if you encounter a
  problem I will investigate.  However, be sure you are using the most
  recent version from ftp://ftp.wizards.dupont.com/pub/ImageMagick
  before submitting any bug reports or suggestions.  Report any problems
  via the web-based reporting facility at
  http://www.simplesystems.org/ImageMagick/bugs.html.


WWW

  The official ImageMagick WWW page is

    http://www.wizards.dupont.com/cristy/ImageMagick.html

  To use display as your external image viewer, edit the global
  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

  to majordomo@wizards.dupont.com.  You will receive a welcome message
  which tells you how to post messages to the list,
  magick@wizards.dupont.com.


MEMORY REQUIREMENTS

  You should allocate sufficient swap space on your system before
  running ImageMagick; otherwise, you may experience random server or
  application crashes. Anything less than 80 megabytes of swap space is
  likely to cause random crashes.

  On many systems, you will find that 80 megabytes is insufficient and
  you will have to allocate more swap space.  You should also have at
  least 32 megabytes of real memory although 64 megabytes or more is
  recommended.


UNIX/Cygwin COMPILATION

  Type:

    gzip -dc ImageMagick-5.0.0.tar.gz | tar xvf -
    cd ImageMagick-5.0.0

  If you do not have gunzip(1), it is available as
  prep.ai.mit.edu:pub/gnu/gzip-1.2.4.shar.

  There are currently two mechanisms available to create makefiles to
  build ImageMagick: 1) GNU configure;  2: X11 imake.  Each is described
  in the following paragraphs.

  * * *

  GNU configure:

    This option is easiest to use and is recommended when ImageMagick
    is to be installed outside of the X11 distribution or working imake
    configuration files are not available.  Use of 'configure' enables
    automated configuration, building, and installation of PerlMagick.

    If you are willing to accept configure's default options, type:

        ./configure

    and watch the configure script output to verify that it finds
    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,
    compilation flags, or libraries, you can give `configure' initial
    values for variables by setting them in the environment.  Using a
    Bourne-compatible shell, you can do that on the command line like
    this:

        CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

    Or on systems that have the `env' program, you can do it like this:

        env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

    The configure variables you should be aware of are:

        CC          Name of C compiler (e.g. 'cc -Xa') to use
        CFLAGS      Compiler flags (e.g. '-g -O2') to compile with
        CPPFLAGS    Include paths (-I/somedir) to look for header files
        LDFLAGS     Library paths (-L/somedir) to look for libraries
                    Systems that support the notion of a library
                    run-path may additionally require -R/somedir or
                    '-rpath /somedir' in order to find shared libraries
                    at run time.
        LIBS        Extra libraries (-lsomelib) required to link

    Any variable (e.g. CPPFLAGS or LDFLAGS) which requires a directory
    path must specify an absolute path rather than a relative path.

    By default, `make install' will install the package's files in
    `/usr/local/bin', `/usr/local/man', etc.  You can specify an
    installation prefix other than `/usr/local' by giving `configure'
    the option `--prefix=PATH'.

    Configure can usually find the X include and library files
    automatically, but if it doesn't, you can use the `configure'
    options `--x-includes=DIR' and `--x-libraries=DIR' to specify their
    locations.

    The configure script provides a number of ImageMagick specific
    options.  When disabling an option --disable-something is equivalent
    to specifying --enable-something=no and --without-something is
    equivalent to --with-something=no.  The configure options are as
    follows (execute 'configure --help' to see all options).

      --enable-shared      build shared libraries (default is no)
      --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)
      --enable-socks       enable use of SOCKS 5 library and 'rftp'
      --with-frozenpaths   enable frozen delegate paths (default is yes)
      --with-perl          enable build/install of PerlMagick (default is yes)
      --with-bzlib         enable BZlib (default is yes)
      --with-dps           enable Display Postscript (default is yes)
      --with-fpx           enable FlashPIX (default is yes)
      --with-hdf           enable HDF (default is yes)
      --with-jbig          enable JBIG (default is yes)
      --with-jpeg          enable JPEG (default is yes)
      --with-png           enable PNG (default is yes)
      --with-tiff          enable TIFF (default is yes)
      --with-ttf           enable TrueType (default is yes)
      --with-zlib          enable Zlib (default is yes)
      --with-x             use the X Window System

    ImageMagick options represent either features to be enabled or
    packages to be included in the build.  When a feature is enabled
    (via --enable-something), it enables code already present in
    ImageMagick.  When a package is enabled (via --with-something), the
    configure script will search for it, and if is is properly
    installed and ready to use (headers and built libraries are found
    by compiler) it will be included in the build.  The configure script
    is delivered with all features disabled and all packages enabled
    (except for PERL). In general, the only reason to disable a package
    is if a package exists but it is unsuitable for the build (perhaps
    an old version or not compiled with the right compilation flags).

    Several configure options require special note:

      o --enable-shared: the shared libraries are built. Shared
        libraries are valuable because they are *shared* across more
        than one invocation of an ImageMagick or PerlMagick client. In
        addition, the clients take much less disk space and shared
        libraries are required in order for PERL to dynamically load the
        PerlMagick extension.

        ImageMagick built with delegates (see MAGICK PLUG-INS below) can
        pose additional challenges.  You can build all the delegates
        statically and link them into the ImageMagick shared library
        (i.e. libMagick.so) or alternatively you can build the delegates
        as shared libraries (some systems already have delegates
        installed as shared libraries).  Shared libraries compilation
        flags differ from vendor to vendor (gcc's is -fPIC).  However,
        you must compile all shared library source with the same flag
        (for gcc use -fPIC rather than -fpic).

      o --disable-static: static archive libraries (with extension .a)
        are not built.  If you are building shared libraries, there is
        little value to building static libraries. Reasons to build
        static libraries include: 1) they can be easier to debug; 2) the
        clients do not have external dependencies (i.e. libMagick.so);
        3) building PIC versions of the delegate libraries may take
        additional expertise and effort; 4) you are unable to build
        shared libraries.

      o --without-frozenpaths: By default, the configure script will
        determine the location of all delegates (external programs) and
        incorporate the full paths within the delegates.mgk file. This
        is the default because it is assumed that the installer's
        environment is appropriately configured and that the operation
        of ImageMagick should not be subject to the end-user's
        environment. However, if it is desireable to allow the end user
        to define their own environment or possible that the end user's
        environment does not match the installer's environment (e.g. for
        binary distributions), --without-frozenpaths may be specified so
        that only the delegate's name is included in the delegates.mgk
        file.

      o --without-perl: By default, PerlMagick is conveniently compiled
        and installed in one step. When --without-perl is specified, you
        must first install ImageMagick, change to the PerlMagick
        subdirectory, build, and finally install PerlMagick. Note,
        PerlMagick is configured even if --without-perl is specified. If
        --enable-shared is not specified, a new PERL interpreter
        (PerlMagick) is built which is statically linked against the
        PerlMagick extension. This new interpreter is installed
        alongside your existing PERL interpreter. If --enable-shared is
        specified, the PerlMagick extension is built as a dynamically
        loadable object which is loaded into your current PERL
        interpreter at run-time. Use of dynamically-loaded extensions is
        preferable over statically linked extensions so --enable-shared
        should be specified if possible. If the argument
        --with-perl=/path/to/perl is supplied, then /path/to/perl will
        be taken as the PERL interpreter to use.

      o --without-x: By default, ImageMagick will use X11 libraries if
        they are available. When --without-x is specified, use of X11 is
        disabled. The display, animate, and import programs are not
        built or installed. The remaining programs have reduced
        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
      http://dao.gsfc.nasa.gov/software/grads/win32/X11R6.4/. Use the
      same procedure as for Unix except that building DLLs is not yet
      supported so do not specify --enable-shared option to configure.

    Dealing with configuration failures:

      While configure is designed to ease installation of ImageMagick,
      it often discovers problems that would otherwise be encountered
      later when compiling ImageMagick. The configure script tests for
      headers and libraries by executing the compiler (CC) with the
      specified compilation flags (CFLAGS), pre-processor flags
      (CPPFLAGS), and linker flags (LDFLAGS). Any errors are logged to
      the file 'config.log'. If configure fails to discover a header or
      library please review this log file to determine why, however,
      please be aware that *errors in the config.log are normal* because
      configure works by trying something and seeing if it fails. An
      error in config.log is only a problem if the test should have
      worked on your system.. After taking corrective action, be sure to
      remove the 'config.cache' file before running configure so that
      configure will re-inspect the environment rather than using cached
      values.

      Common causes of configure falures are: 1) a delegate header is not
      in the header include path (CPPFLAGS -I option); 2) a delegate
      library is not in the linker search/run path (LDFLAGS -L/-R
      option); 3) a delegate library is missing a function (old
      version?); 4) compilation environment is faulty.

      If all reasonable corrective actions have been tried and the
      problem appears to be due to a flaw in the configure script,
      please send a bug report to the configure script maintainer
      (currently bfriesen@simple.dallas.tx.us). All bug reports should
      contain the operating system type (as reported by 'uname -a') and
      the compiler/compiler-version. A copy of the configure script
      output and/or the config.log file may be valuable in order to find
      the problem. If you send a config.log, please also send a script
      of the configure output and a description of what you expected to
      see (and why) so the failure you are observing can be identified
      and resolved.

  * * *

  X11 Imake:

    Use this option if working imake configuration files are available,
    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 a
    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

    if you are using X11R6 imake.  Here, GNU configure is used to
    initialize the delegates/delegates.mgk file.

  * * *

  To confirm your build of the ImageMagick distribution was
  successful, type:

      display

  If the program faults ensure that you have not inadvertingly linked to
  an older version of the libMagick library. To ensure this is not the
  case type

      cd ImageMagick/magick
      make install
      cd ..
      make

  If the image colors are not correct use this command:

      display -visual default

  Be sure to read the manual pages for the display(1), animate(1),
  montage(1), import(1), mogrify(1), identify(1), combine(1), and
  convert(1) utilities. Also read the ImageMagick frequently asked
  questions in the file www/Magick.html. This is required reading. Most
  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 name
  for other clients (e.g. Animate, Montage, etc).  To execute display(1)
  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:

    o ImageMagick requires the BZLIB library from

          http://sourceware.cygnus.com/bzip2/index.html

      to read and write BZip compressed MIFF images.

    o ImageMagick requires ralcgm from

          http://www.agocg.ac.uk/train/cgm/ralcgm.htm

      to read the Computer Graphics Metafile image format (may not compile
      under linux).  You also need Ghostscript (see below).

    o ImageMagick requires fig2dev from

          ftp://ftp.x.org/contrib/applications/drawing_tools/transfig

      to read the TransFig image format.

    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/

      to read the Postscript or the Portable Document format.  It is used
      to annotate an image when an X server is not available.  See the
      FreeType library above for another means to annotate an image.  Note,
      Ghostscript must support the ppmraw device (type gs -h to verify).
      If Ghostscript is unavailable, the Display Postscript extension is
      used to rasterize a Postscript document (assuming you define HasDPS).
      The DPS extension is less robust than Ghostscript in that it will only
      rasterize one page of a multi-page document.

    o ImageMagick requires the NCSA HDF library available via anonymous FTP
      as

          ftp://ftp.ncsa.uiuc.edu/HDF/HDF/HDF_Current

      to read and write the HDF image format.

    o ImageMagick requires hp2xx available from

          http://www.gnu.org/software/hp2xx/hp2xx.html

      to read the HP-GL image format.

    o ImageMagick requires gnuplot available via anonymous FTP as

          ftp://ftp.dartmouth.edu/pub/gnuplot/gnuplot3.5.tar.Z

      to read GNUPLOT plot files (with extension gplt).

    o ImageMagick requires html2ps available from

          http://www.tdb.uu.se/~jan/html2ps-1.0b1.zip

      to read the HTML image format.

    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.

      Apply this JPEG patch to Independent JPEG Group's source distribution to
      read lossless jpeg-encoded DICOM images:

          ftp://ftp.wizards.dupont.com/pub/ImageMagick/delegates/
            ljpeg-6b.tar.gz

      Concerning iterative JPEG compression:  see Kinoshita and
      Yamamuro, Journal of Imaging Science and Technology, "Image
      Quality with Reiterative JPEG Compression", Volume 39, Number 4,
      July 1995, 306-312 who claim that (1) the iterative factor of the
      repetitive JPEG operation had no influence on image quality, and
      (2) the first compression determined base image quality.

    o ImageMagick requires the MPEG library available via
      anonymous FTP as

          ftp://ftp.mpeg.org/pub/mpeg/mssg/mpeg2vidcodec_v12.tar.gz

      to read or write the MPEG image format.

    o ImageMagick requires the PNG library, version 1.0 or above, from

          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

          http://radsite.lbl.gov/radiance/HOME.html

      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

          ftp://ftp.cs.utah.edu/pub/urt-3.1b.tar.Z

      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/

      to read the TIFF image format.  It in turn optionally requires
      the JPEG and ZLIB libraries.

    o ImageMagick requires wmftogif available from

          http://www.csn.ul.ie/~caolan/docs/libwmf.html

      to read the Windows Meta File image format.

    o ImageMagick requires GET(1) available via the Web as

          http://www.linpro.no/lwp/

      to read images specified with a World Wide Web (WWW) uniform
      resource locator (URL).  If you do not have a HTTP server, you
      can use xtp(1), available in the ImageMagick distribution, for
      URL's whose protocol is FTP.

    o ImageMagick requires an X server for display and animate to work
      properly.  There is a nearly free X server available for Windows and
      Macintosh at

        http://www.microimages.com/freestuf/mix/

    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.

    o ImageMagick requires SOCKS version 5 available via the Web at

          http://www.socks.nec.com/

      in order for 'xtp' to work across a SOCKS5-based firewall. In
      particular, 'xtp' makes use of SOCKS5 'rftp' as an external
      program and supports use of the SOCKS5 library to perform DNS
      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

  NOTE: The following procedure describes how to build ImageMagick
  extension libraries in subdirectories of the ImageMagick directory.
  An alternative to these procedures is to install one or more of
  these under your system's regular include/lib directory (e.g. the
  directory specified by --prefix to configure or /usr/local). This
  allows the libraries to be shared by other packages. When using the
  configure script, the two schemes may be mixed. Also, please note
  that when the configure option --enable-shared is not disabled,
  these procedures must be supplemented with whatever compilation
  flags are required on your system to generate PIC code. In the case
  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
  format, get the respective archives and build ImageMagick as follows:

    BZLIB:
      cd ImageMagick
      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.4.tar.gz | tar xvof -
      mv tiff-v3.5.4 tiff
      cd tiff
      ./configure
      make
      cd ..

    TTF:
      cd ImageMagick
      gunzip -c freetype-1.3.1.tar.gz | tar xvof -
      mv freetype-1.3.1 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

  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

  If prefer to use 'configure' rather than Imake:

      configure
      make clean
      make -k

  You can now convert or display images in the JPEG, TIFF, PNG, etc.
  image formats.


VMS COMPILATION

  You might want to check the values of certain program definitions
  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::

  where node_name is the DECNET X server to contact.

  Finally type:

      display

  Alternatively, get a zipped distribution (with JPEG, PNG, TIFF, TTF) from

      ftp://ftp.wizards.dupont.com/pub/ImageMagick/vms/ImageMagick-4.1.zip

  The VMS JPEG, PNG, TIFF, and TTF  source libraries are available on
  axp.psl.ku.dk in [anonymous.decwindows.lib].

  Thanks to pmoreau@cenaath.cena.dgac.fr for supplying
  invaluable help as well as the VMS versions of the JPEG, PNG, TTF, and
  TIFF libraries.


Windows NT/95 VISUAL C++ 6.0 COMPILATION

  The Visual C++ distribution targeted at Windows NT or Windows 95
  is provided in the "VisualMagick" subdirectory of the distribution.
  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
    VisualMagickX11.dsw : The one used to build everything as DLL's
                          but enabling X11 support using the DLL's
                          and libraries supplied with the distribution
    VisualMagickStatic.dsw: The one used to build everything as
                            static standalone executable

  A complete build can be accomplished by simply doing:

    Build: Batch Build: Clean
    Build: Batch Build: Build

  The "Clean" step is needed in order to make sure that all of the
  target support libraries are updated with any patches needed to
  get them to compile properly on Windows.

  All of the required files that are needed to run any of the command
  line tools will be found in the "bin" subdirectory of the VisualMagick
  subdirectory. This includes EXE, and DLL files. You should be able
  to test the build directly from this directory without having to
  move anything to any of the global SYSTEM or SYSTEM32 areas in the
  operating system installation.

  NOTE: The two utilities "display" and "animate" will only be compiled
  when using the VisualMagickX11 workspace. The other build environments
  uses the X11 stubs to supply non-functional stubs for the X-Window
  functionality. There is no support for a "static" build of the X11
  support because the build procedures for the X11 libraries do not seem
  to support this.

  To view any image in a Microsoft window, type

      convert image.ext win:

  Make sure gswin32 (Ghostscript) is in your execution path (see
  Autoexec.bat), otherwise, you will be unable to convert or view
  a Postscript document.

  Make sure iexplore (Internet Explorer) is in your execution path (see
  Autoexec.bat), otherwise, you will be unable to browse the ImageMagick
  documentation.

  The NT executables will work under Windows 95/98.


MACINTOSH COMPILATION

  The Macintosh distribution contains MetroWerks Codewarrior
  Professional projects for compilation.  For those who do not have
  access to CodeWarrior, the binaries for the command line utilities
  are enclosed.  I had to comment the inline intrinsic functions in
  math.h in order to compile.  If you have a better solution, let me
  know.

  Display(1), animate(1), and import(1) currently do not work on the
  Macintosh.

  I am looking for a volunteer to get display(1) and animate(1) to work
  on the Macintosh.  I also need a volunteer is needed to write a
  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.
  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:

      mogrify +map -colors 256 scenes/dna.[0-9]*

  Alternatively, you can use a Standard Colormap; or a static, direct,
  or true color visual.  You can define a Standard Colormap with
  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:

      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.
  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.
  [0..255] for each of red, green, blue, and transparency components).
  Any 16-bit image is scaled to 8-bits before any image viewing or
  processing occurs.  If you want to work directly with 16-bit images
  (e.g. [0..65535]), edit Magick.tmpl and define QuantumLeap or use
  -enable-16bit with configure.  Next, type:

      make clean
      make

  In 16-bit mode expect to use about 33% more memory on the average.
  Also expect some processing to be slower than in 8-bit mode (e.g.
  Oil Painting, Segment, etc).

  In general, 16-bit mode is only useful if you have 16-bit images that
  you want to manipulate and save the transformed image back to a
  16-bit image format (e.g. PNG, VIFF).


64-BIT MACHINES

  Each pixel, within ImageMagick, is represented by the PixelPacket
  structure found in magick/image.h. Only 8 bits are required for each
  color component for a total of 4 bytes. If QuantumLeap is defined (see
  16-BIT IMAGING above), the color component size increases to 16 bits
  for a total of 8 bytes. Some 64-bit machines pad the structure which
  can cause a significant 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;
      } PixelPacket;

  before compiling.

  I'm not sure if this will work on other 64-bit machines that pad. If
  you know a better solution, please send me E-mail. Note, that the Dec
  Alpha apparently does not pad the structure so ImageMagick should be
  fine on this particular 64-bit machine.


Magick++

  If you would like to build and install the Magick++ C++ programming
  interface to ImageMagick, first build and install ImageMagick
  according to the instructions in this file (configure script method
  for Unix) and then build and install Magick++ according to the
  instructions in the INSTALL file in the Magick++ subdirectory.
  Magick++ is currently supported using the egcs 1.1.2 version of GNU
  g++ (or later) under Unix and Microsoft Visual C++ 6.0 under Windows
  NT or Windows 95/98.


COPYRIGHT

  Copyright (C) 2000 ImageMagick Studio, a non-profit organization
  dedicated to making software imaging solutions freely available.

  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,
  including without limitation the rights to use, copy, modify, merge,
  publish, distribute, sublicense, and/or sell copies of ImageMagick,
  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.

  The software is provided "as is", without warranty of any kind,
  express or implied, including but not limited to the warranties of
  merchantability, fitness for a particular purpose and
  noninfringement.  In no event shall ImageMagick Studio be liable for
  any claim, damages or other liability, whether in an action of
  contract, tort or otherwise, arising from, out of or in connection
  with ImageMagick or the use or other dealings in ImageMagick.

  Except as contained in this notice, the name of the ImageMagick
  Studio shall not be used in advertising or otherwise to promote the
  sale, use or other dealings in ImageMagick without prior written
  authorization from the ImageMagick Studio.
