310 lines
13 KiB
XML
310 lines
13 KiB
XML
<?xml version="1.0" encoding="utf-8" ?>
|
||
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
||
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
|
||
<refentry id="Using-vipsthumbnail.md">
|
||
|
||
|
||
<para>
|
||
<refmeta> <refentrytitle>Using <literal>vipsthumbnail</literal></refentrytitle> <manvolnum>3</manvolnum> <refmiscinfo>libvips</refmiscinfo> </refmeta>
|
||
</para>
|
||
<para>
|
||
<refnamediv> <refname><literal>vipsthumbnail</literal></refname> <refpurpose>Introduction to <literal>vipsthumbnail</literal>, with examples</refpurpose> </refnamediv>
|
||
</para>
|
||
<para>
|
||
libvips ships with a handy command-line image thumbnailer, <literal>vipsthumbnail</literal>. This page introduces it, with some examples.
|
||
</para>
|
||
<para>
|
||
The thumbnailing functionality is implemented by <literal>vips_thumbnail()</literal> and <literal>vips_thumbnail_buffer()</literal> (which thumbnails an image held as a string), see the docs for details. You can use these functions from any language with a libvips binding. For example, from PHP you could write:
|
||
</para>
|
||
<programlisting>
|
||
$filename = "image.jpg";
|
||
$image = Vips\Image::thumbnail($filename, 200, ["height" => 200]);
|
||
$image->writeToFile("my-thumbnail.jpg");
|
||
</programlisting>
|
||
<refsect3 xml:id="libvips-options">
|
||
<title>libvips options</title>
|
||
<para>
|
||
<literal>vipsthumbnail</literal> supports the usual range of vips command-line options. A few of them are useful:
|
||
</para>
|
||
<para>
|
||
<literal>--vips-cache-trace</literal> shows each operation as libvips starts it. It can be handy to see exactly what operations <literal>vipsthumbnail</literal> is running for you.
|
||
</para>
|
||
<para>
|
||
<literal>--vips-leak</literal> turns on the libvips memory leak checker. As well as reporting leaks (hopefully there are none) it also tracks and reports peak memory use.
|
||
</para>
|
||
<para>
|
||
<literal>--vips-progress</literal> runs a progress indicator during computation. It can be useful to see where libvips is looping and how often.
|
||
</para>
|
||
<para>
|
||
<literal>--vips-info</literal> shows a higher level view of the operations that <literal>vipsthumbnail</literal> is running.
|
||
</para>
|
||
</refsect3>
|
||
<refsect3 xml:id="looping">
|
||
<title>Looping</title>
|
||
<para>
|
||
<literal>vipsthumbnail</literal> can process many images in one command. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail *.jpg
|
||
</programlisting>
|
||
<para>
|
||
will make a thumbnail for every jpeg in the current directory. See the <link linkend="output-directory">Output directory</link> refsect3 below to see how to change where thumbnails are written.
|
||
</para>
|
||
<para>
|
||
<literal>vipsthumbnail</literal> will process images one after the other. You can get a good speedup by running several <literal>vipsthumbnail</literal>s in parallel, depending on how much load you want to put on your system. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ parallel vipsthumbnail ::: *.jpg
|
||
</programlisting>
|
||
</refsect3>
|
||
<refsect3 xml:id="thumbnail-size">
|
||
<title>Thumbnail size</title>
|
||
<para>
|
||
You can set the bounding box of the generated thumbnail with the <literal>--size</literal> option. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail shark.jpg --size 200x100
|
||
</programlisting>
|
||
<para>
|
||
Use a single number to set a square bounding box. You can omit either number but keep the x to mean resize just based on that axis, for example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail shark.jpg --size 200x
|
||
</programlisting>
|
||
<para>
|
||
Will resize to 200 pixels across, no matter what the height of the input image is.
|
||
</para>
|
||
<para>
|
||
You can append <literal><</literal> or <literal>></literal> to mean only resize if the image is smaller or larger than the target.
|
||
</para>
|
||
<para>
|
||
You can append <literal>!</literal> to force a resize to the exact target size, breaking the aspect ratio.
|
||
</para>
|
||
</refsect3>
|
||
<refsect3 xml:id="cropping">
|
||
<title>Cropping</title>
|
||
<para>
|
||
<literal>vipsthumbnail</literal> normally shrinks images to fit within the box set by <literal>--size</literal>. You can use the <literal>--smartcrop</literal> option to crop to fill the box instead. Excess pixels are trimmed away using the strategy you set. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail owl.jpg --smartcrop attention -s 128
|
||
</programlisting>
|
||
<para>
|
||
Where <literal>owl.jpg</literal> is an off-centre composition:
|
||
</para>
|
||
<para>
|
||
<inlinemediaobject>
|
||
<imageobject>
|
||
<imagedata fileref="owl.jpg" />
|
||
</imageobject>
|
||
</inlinemediaobject>
|
||
</para>
|
||
<para>
|
||
Gives this result:
|
||
</para>
|
||
<para>
|
||
<inlinemediaobject>
|
||
<imageobject>
|
||
<imagedata fileref="tn_owl.jpg" />
|
||
</imageobject>
|
||
</inlinemediaobject>
|
||
</para>
|
||
<para>
|
||
First it shrinks the image to get the vertical axis to 128 pixels, then crops down to 128 pixels across using the <literal>attention</literal> strategy. This one searches the image for features which might catch a human eye, see <literal>vips_smartcrop()</literal> for details.
|
||
</para>
|
||
</refsect3>
|
||
<refsect3 xml:id="linear-light">
|
||
<title>Linear light</title>
|
||
<para>
|
||
Shrinking images involves combining many pixels into one. Arithmetic averaging really ought to be in terms of the number of photons, but (for historical reasons) the values stored in image files are usually related to the voltage that should be applied to the electron gun in a CRT display.
|
||
</para>
|
||
<para>
|
||
<literal>vipsthumbnail</literal> has an option to perform image shrinking in linear space, that is, a colourspace where values are proportional to photon numbers. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail fred.jpg --linear
|
||
</programlisting>
|
||
<para>
|
||
The downside is that in linear mode, none of the very fast shrink-on-load tricks that <literal>vipsthumbnail</literal> normally uses are possible, since the shrinking is done at encode time, not decode time, and is done in terms of CRT voltage, not photons. This can make linear light thumbnailing of large images extremely slow.
|
||
</para>
|
||
<para>
|
||
For example, for a 10,000 x 10,000 pixel JPEG I see:
|
||
</para>
|
||
<programlisting>
|
||
$ time vipsthumbnail wtc.jpg
|
||
real 0m0.317s
|
||
user 0m0.292s
|
||
sys 0m0.016s
|
||
$ time vipsthumbnail wtc.jpg --linear
|
||
real 0m4.660s
|
||
user 0m4.640s
|
||
sys 0m0.016s
|
||
</programlisting>
|
||
</refsect3>
|
||
<refsect3 xml:id="output-directory">
|
||
<title>Output directory</title>
|
||
<para>
|
||
You set the thumbnail write parameters with the <literal>-o</literal> option. This is a pattern which the input filename is pasted into to produce the output filename. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail fred.jpg jim.tif -o tn_%s.jpg
|
||
</programlisting>
|
||
<para>
|
||
For each of the files to be thumbnailed, <literal>vipsthumbnail</literal> will drop the extension (<literal>.jpg</literal> and <literal>.tif</literal> in this case) and then substitute the name into the <literal>-o</literal> option, replacing the <literal>%s</literal> So this example will write thumbnails to <literal>tn_fred.jpg</literal> and <literal>tn_jim.jpg</literal>.
|
||
</para>
|
||
<para>
|
||
If the pattern given to <literal>-o</literal> is an absolute path, any path components are dropped from the input filenames. This lets you write all of your thumbnails to a specific directory, if you want. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail fred.jpg ../jim.tif -o /mythumbs/tn_%s.jpg
|
||
</programlisting>
|
||
<para>
|
||
Now both thumbnails will be written to <literal>/mythumbs</literal>, even though the source images are in different directories.
|
||
</para>
|
||
<para>
|
||
Conversely, if <literal>-o</literal> is set to a relative path, any path component from the input file is prepended. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail fred.jpg ../jim.tif -o mythumbs/tn_%s.jpg
|
||
</programlisting>
|
||
<para>
|
||
Now both input files will have thumbnails written to a subdirectory of their current directory.
|
||
</para>
|
||
</refsect3>
|
||
<refsect3 xml:id="output-format-and-options">
|
||
<title>Output format and options</title>
|
||
<para>
|
||
You can use <literal>-o</literal> to specify the thumbnail image format too. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail fred.jpg ../jim.tif -o tn_%s.png
|
||
</programlisting>
|
||
<para>
|
||
Will write thumbnails in PNG format.
|
||
</para>
|
||
<para>
|
||
You can give options to the image write operation as a list of comma-separated arguments in square brackets. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail fred.jpg ../jim.tif -o tn_%s.jpg[Q=90,optimize_coding]
|
||
</programlisting>
|
||
<para>
|
||
will write jpeg images with quality 90, and will turn on the libjpeg coding optimizer.
|
||
</para>
|
||
<para>
|
||
Check the image write operations to see all the possible options. For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vips jpegsave
|
||
save image to jpeg file
|
||
usage:
|
||
jpegsave in filename
|
||
where:
|
||
in - Image to save, input VipsImage
|
||
filename - Filename to save to, input gchararray
|
||
optional arguments:
|
||
Q - Q factor, input gint
|
||
default: 75
|
||
min: 1, max: 100
|
||
profile - ICC profile to embed, input gchararray
|
||
optimize-coding - Compute optimal Huffman coding tables, input gboolean
|
||
default: false
|
||
interlace - Generate an interlaced (progressive) jpeg, input gboolean
|
||
default: false
|
||
no-subsample - Disable chroma subsample, input gboolean
|
||
default: false
|
||
trellis-quant - Apply trellis quantisation to each 8x8 block, input gboolean
|
||
default: false
|
||
overshoot-deringing - Apply overshooting to samples with extreme values, input gboolean
|
||
default: false
|
||
optimize-scans - Split the spectrum of DCT coefficients into separate scans, input gboolean
|
||
default: false
|
||
quant-table - Use predefined quantization table with given index, input gint
|
||
default: 0
|
||
min: 0, max: 8
|
||
strip - Strip all metadata from image, input gboolean
|
||
default: false
|
||
background - Background value, input VipsArrayDouble
|
||
</programlisting>
|
||
<para>
|
||
The <literal>strip</literal> option is especially useful. Many image have very large IPCT, ICC or XMP metadata items embedded in them, and removing these can give a large saving.
|
||
</para>
|
||
<para>
|
||
For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail 42-32157534.jpg
|
||
$ ls -l tn_42-32157534.jpg
|
||
-rw-r–r– 1 john john 6682 Nov 12 21:27 tn_42-32157534.jpg
|
||
</programlisting>
|
||
<para>
|
||
<literal>strip</literal> almost halves the size of the thumbnail:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail 42-32157534.jpg -o x.jpg[optimize_coding,strip]
|
||
$ ls -l x.jpg
|
||
-rw-r–r– 1 john john 3600 Nov 12 21:27 x.jpg
|
||
</programlisting>
|
||
</refsect3>
|
||
<refsect3 xml:id="colour-management">
|
||
<title>Colour management</title>
|
||
<para>
|
||
<literal>vipsthumbnail</literal> will optionally put images through LittleCMS for you. You can use this to move all thumbnails to the same colour space. All web browsers assume that images without an ICC profile are in sRGB colourspace, so if you move your thumbnails to sRGB, you can strip all the embedded profiles. This can save several kb per thumbnail.
|
||
</para>
|
||
<para>
|
||
For example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail shark.jpg
|
||
$ ls -l tn_shark.jpg
|
||
-rw-r–r– 1 john john 7295 Nov 9 14:33 tn_shark.jpg
|
||
</programlisting>
|
||
<para>
|
||
Now transform to sRGB and don’t attach a profile (you can also use <literal>strip</literal>, though that will remove <emphasis>all</emphasis> metadata from the image):
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail shark.jpg --eprofile srgb -o tn_shark.jpg[profile=none]
|
||
$ ls -l tn_shark.jpg
|
||
-rw-r–r– 1 john john 4229 Nov 9 14:33 tn_shark.jpg
|
||
</programlisting>
|
||
<para>
|
||
(You can use the filename of any RGB profile. The magic string <literal>srgb</literal> selects a high-quality sRGB profile that’s built into libvips.)
|
||
</para>
|
||
<para>
|
||
<literal>tn_shark.jpg</literal> will look identical to a user, but it’s almost half the size.
|
||
</para>
|
||
<para>
|
||
You can also specify a fallback input profile to use if the image has no embedded one. This can often happen with CMYK images, producing an error message like:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail kgdev.jpg
|
||
vipsthumbnail: unable to thumbnail kgdev.jpg
|
||
vips_colourspace: no known route from 'cmyk' to 'srgb'
|
||
</programlisting>
|
||
<para>
|
||
If you supply a CMYK profile, it will be able to convert the image, for example:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail kgdev.jpg --iprofile cmyk
|
||
</programlisting>
|
||
<para>
|
||
(As before, the magic string <literal>cmyk</literal> selects a high-quality CMYK profile that’s built into libvips, but you can use any CMYK profile you like.)
|
||
</para>
|
||
</refsect3>
|
||
<refsect3 xml:id="final-suggestion">
|
||
<title>Final suggestion</title>
|
||
<para>
|
||
Putting all this together, I suggest this as a sensible set of options:
|
||
</para>
|
||
<programlisting>
|
||
$ vipsthumbnail fred.jpg \
|
||
--size 128 \
|
||
--eprofile srgb \
|
||
-o tn_%s.jpg[optimize_coding,strip] \
|
||
--eprofile srgb
|
||
</programlisting>
|
||
</refsect3>
|
||
|
||
|
||
</refentry>
|