|author||Ching-Sung Li <firstname.lastname@example.org>||Fri Feb 21 11:30:19 2020 +0800|
|committer||Haibo Huang <email@example.com>||Tue Feb 25 22:19:00 2020 +0000|
ImageMagick: only build the jpeg coder. The sole user of ImageMagick (the legacy wallpapers) only needs jpeg, so let's get out of the business of supporting every other format known to man. Test: wallpaper app still works on taimen Change-Id: I7c5673a90aec445c6e03c3557aec4dc780f8df0a ImageMagick: have DDS and XC coders added The user of ImageMagick (the legacy wallpapers) needs DDS and XC coders. Also move the Android-specific list of coders to the top of coders-list.h to avoid merge conflicts. Test: wallpaper should run in walleye Change-Id: If8915d51ac2f3e7a4427241e5dfbe52a2f5b5447 Bug: 136733674
Use ImageMagick® to create, edit, compose, or convert bitmap images. It can read and write images in a variety of formats (over 200) including PNG, JPEG, GIF, HEIC, TIFF, DPX, EXR, WebP, Postscript, PDF, and SVG. Use ImageMagick to resize, flip, mirror, rotate, distort, shear and transform images, adjust image colors, apply various special effects, or draw text, lines, polygons, ellipses and Bézier curves.
The functionality of ImageMagick is typically utilized from the command line or you can use the features from programs written in your favorite programming language. Choose from these interfaces: G2F (Ada), MagickCore (C), MagickWand (C), ChMagick (Ch), ImageMagickObject (COM+), Magick++ (C++), JMagick (Java), L-Magick (Lisp), NMagick (Neko/haXe), MagickNet (.NET), PascalMagick (Pascal), PerlMagick (Perl), MagickWand for PHP (PHP), IMagick (PHP), PythonMagick (Python), magick (R), RMagick (Ruby), or TclMagick (Tcl/TK). With a language interface, use ImageMagick to modify or create images dynamically and automagically.
ImageMagick utilizes multiple computational threads to increase performance and can read, process, or write mega-, giga-, or tera-pixel image sizes.
ImageMagick is free software delivered as a ready-to-run binary distribution or as source code that you may use, copy, modify, and distribute in both open and proprietary applications. It is distributed under a derived Apache 2.0 license.
The ImageMagick development process ensures a stable API and ABI. Before each ImageMagick release, we perform a comprehensive security assessment that includes memory error and thread data race detection to prevent security vulnerabilities.
The current release is the ImageMagick 7.0.8 series. It runs on Linux, Windows, Mac Os X, iOS, Android OS, and others.
The authoritative ImageMagick web site is https://imagemagick.org. The authoritative source code repository is https://github.com/ImageMagick. We maintain a source code mirror at https://gitlab.com/ImageMagick.
We continue to maintain the legacy release of ImageMagick, version 6, at https://legacy.imagemagick.org.
Here are just a few examples of what ImageMagick can do:
Examples of ImageMagick Usage, shows how to use ImageMagick from the command-line to accomplish any of these tasks and much more. Also, see Fred's ImageMagick Scripts: a plethora of command-line scripts that perform geometric transforms, blurs, sharpens, edging, noise removal, and color manipulations. With Magick.NET, use ImageMagick without having to install ImageMagick on your server or desktop.
Now that ImageMagick version 7 is released, we continue to maintain the legacy release of ImageMagick, version 6. Learn how ImageMagick version 7 differs from previous versions with our porting guide.
ImageMagick best practices strongly encourages you to configure a security policy that suits your local environment.
As an analog to linear (RGB) and non-linear (sRGB) color colorspaces, as of ImageMagick 7.0.7-17, we introduce the LinearGray colorspace. Gray is non-linear grayscale and LinearGray is linear (e.g. -colorspace linear-gray).
Want more performance from ImageMagick? Try these options:
If these options are prohibitive, you can reduce the quality of the image results. The default build is Q16 HDRI. If you disable HDRI, you use half the memory and instead of predominately floating point operations, you use the typically more efficient integer operations. The tradeoff is reduced precision and you cannot process out of range pixel values (e.g. negative). If you build the Q8 non-HDRI version of ImageMagick, you again reduce the memory requirements in half-- and once again there is a tradeoff, even less precision and no out of range pixel values. For a Q8 non-HDRI build of ImageMagick, use these configure script options: --with-quantum-depth=8 --disable-hdri.