Legacy ImageMagick Discussions Archive

magick wrote:Here's an easy fix. Add -density 5 to your command line, before the SVG image filename. That will create a reasonably sized result.

Thanks a ton, 5 created blurry results (because im using -scale) but 90 (as pointed out by snibgo) seems to produce good results while being gentle on memory.

So just to get this right; IM tries to render the vector in full size to then shrink it to the desired resolution?
That doesn't sound very efficient to me... Can't I tell IM to directly render it to the desired resolution?

Your IM and GS versions are both old. An upgrade may solve the problem. Thanks, I've updated IM to ImageMagick 6.8.3-9 2013-03-11 Q16 http://www.imagemagick.org but the described behaviour persists (aborted at 8GB this time). GS is provided by my package maintainer (debian stable), so I have still ...

When I'm trying to generate a roughly 300x300 render of a few specific vector files (so far SVG and EPS), after calling gs (which is GhostScript to decode the vector data, i believe), ImageMagick is processing the data and memory usage goes astronomically. So far I've been able to record as much as ...

tomriddle wrote:Hmm... have you maybe tried supplying RGB values instead of hex?

Oh I'm sorry if my palette confused you.
I'm passing an image with those colors to -remap, not hex values.
The palette image is 8 pixels wide and 1 pixel high, it only contains those eight mentioned colors.

Greetings folks! let's start right away; I'm having a quite specialized Problem. I am remapping images (mainly photographs) to the eight 'base colors' (which are #000/black, #fff/white, #f00/red, #0f0/green, #00f/blue, #ff0/yellow, #0ff/cyan and #f0f/magenta) in order to roughly index present colors ...