Legacy ImageMagick Discussions Archive

I agree and I dont think it would be that big of a change. If you keep the initial image in memory. Then save out each tile to file rather than storing it memory it would resolve a lot of the problems.

This seems like it will facilitate at least the taking apart of images.

THX magick .mpc image format sorted it. Since the .mpc format is native image format used by imagemagick it does not need to convert the initial image it just cuts out the piece that it needs. This is the case with the second script I setup. See below how I got it working. Lats say you have a 50000x...

magick wrote:Convert your source image to MPC once then tile, something like

• convert -limit area 2mb srcimage srcimage.mpc
  for each tile
  convert srcimage.mpc -crop axb+c+d tile.png

This might sound like a silly question but is "for each tile" part of the script?

Using tile crop will generate a new image for each and every tile! Of course each will only be sized to fit that tiles data, but then you also make have a lotoof extra meta data associsated too. Than means you at least double the memory usage when you do a tile crop. My idea would be to crop one 'r...

i am passing in a massive 40000x40000 tif it manges to load in the image into memory. but it seems to crop each image and keep it in memory till the end of the process. which is no good cause in writes like 50gig to my swap disk then kills my computer. ideally i would need to modify this so it write...