Legacy ImageMagick Discussions Archive

I'd use the montage command, with a suitable geometry to get the gap between the images.

The ^ (caret) means "don't resize unless at least one dimension is greater than what I want".

I use Windows, and ^ is a special character, so I need the quotes.

In compilation, you can choose which features (especially which file formats) to support.

You can get somewhere close to the Photoshop image with: convert freckles.jpg -selective-blur 0x2+08% defreckle1.png optionally followed by this, repeated a few times: convert defreckle1.png -selective-blur 0x1+5% defreckle1.png Fiddle with the numbers for some variety. Or you might try: convert ...

Thanks for the explanation. I want to avoid caching to disk, as that kills performance of IM and my computer in general. input.png is 75 M pixels. At 8 bytes per pixel, replicated 3 times, it needs 1.8 GB, which sometimes gives me the disk-caching dead-computer syndrome. I suspect I'll go the ...

Ah, thanks. Is the pre-fix/post-fix distiction documented somewhere? Are there plans to "regularise" the parsers across the utilities? I realise my code above would need work even if "swap" worked with Montage. This code does what I want:: montage ^ ( input.png -gravity East -crop 10x100+0+0 ...

Why can't montage use the "swap" option? I want to extend a 360-degree panorama by glueing a crop from the right to left, and another crop from the left to the right. To avoid re-reading the input file, I want to use clone, something like: montage ^ input.png ^ ( +clone -gravity East -crop 10x100+0 ...

To answer my own question: I have now looked at the APIs and source code. It seems that pixels are addressed by "unsigned long". This also applies to resizing, so zooming in will also result in quantisation jerks. Of course, IM is geared towards the production of individual images, rather than ...

Sorry for the quick semi-correction. I'm a newbie. The architecture document (http://www.imagemagick.org/script/architecture.php) is worth reading. If there's not enough memory, IM will store pixels on disk. I tried this out by creating a one billion pixel file: convert -size 1000x1000000 xc:red x ...

You might make a copy, trimming off the top (say) 25% of the image. Maybe also the bottom 5%, as scans can be dirty there.

Do your calculations based on that copy, then apply those numbers to the original.

The solution is messy, but it's bound to be.

I've never tried SVG in MH. Instead, I use Inkscape. (Judging from the MH documentation, this seems the best option.)

Command:
inkscape -f x.svg -e x.png

1,000,000 x 60kB = 60 GB. And that's the compressed size, but I gather MH stores the image uncompressed in memory. I don't think Windows XP allows you to have 60 GB virtual memory. So I think you are asking the impossible. Some other software might work line-by-line, without storing the image in RAM ...

I'm using 6.5.8-Q16 on Windows 7, seeing how suitable IM might be for generating frames for a movie from photographs using pan/zoom/etc. A typical command pastes part of an image to a background: composite -compose Copy -geometry +22.53+10.673 ( srcB.jpg -resize "54.9399%" ) iv_bgnd.png iv_srcB.png ...