Legacy ImageMagick Discussions Archive

Playing with this further, I notice two more things. 1. The time required to do the conversion seems to be decreased with CacheShift set to 3. My test image time to process was decreased by about one second on my desktop. 2. The amount of RAM required for the conversion goes up with increased image ...

Can you tell me what the CacheShift define does then? Experimenting with high-color images shows no clear image quality difference between having CacheShift set to 2 vs having it set to 3, while the memory usage differences are huge . This has apparently been previously identified as an issue when ...

Looking the source for quantize.c, I noticed that the amount of RAM allocated for the reduction is dependent on the CacheShift define which when built for the iPhone is 3, but on the PC is 2. Changing that define to use 3 on my system makes the output image look perfect while using less than 1 MB of ...

I understand that bitmap images are loaded completely into memory to be worked on, but I do not believe that to be the issue. This isn't a 130 MB image when in bitmap format, it's only a bit over 100KB. I further don't believe that the bitmap loader has much to do with it because I can create a 1x1 ...

You might try "-treedepth". See http://www.imagemagick.org/script/command-line-options.php#treedepth Thanks for the tip but -treedepth does not seem to affect the memory usage in any way. I ran the conversion with a treedepth of 0 through 20 and it was always 137,563,412+-1 $ for i in $(seq 0 20 ...

I am having an issue converting images from png to an 8-bit bitmap with only 256 colors. I need to do this conversion on an embedded device with a very small amount of RAM, only about 24MB free, and every command I try to do this results in an out of memory error: convert: Memory allocation failed ...