Legacy ImageMagick Discussions Archive

It's been going for 5 days now, the memory utilization is at 12gb now, down from 21gb. I'm not sure what's going on, as there is still zero disk activity.

Well, it's been running for about 3 days now, still no signs of progress

https://www.dropbox.com/sh/qwz43i5fy78n ... ELjPa?dl=0

There's access to the images and the script i've been using if anyone wants to take a crack at it.

You did the conversion of my images?

So, right now after about 17 hours of processing, there is zero disk activity, 25gb of 32gb of ram is being used without fluctuations, and the CPU utilization for montage.exe is stuck at 17.5%. Could it have crashed? Or do I need to just wait longer?

this is the policy xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE policymap [ <!ELEMENT policymap (policy)+> <!ELEMENT policy (#PCDATA)> <!ATTLIST policy domain (delegate|coder|filter|path|resource) #IMPLIED> <!ATTLIST policy name CDATA #IMPLIED> <!ATTLIST policy rights CDATA #IMPLIED ...

I just realized I was in the wrong working directory! Thanks for pointing that out! I didn't install jpg and tiff delegates. How do I do that? It's processing now. Hopefully it won't error out. What is the file size/pixel dimension limits for tiff? Could i be exceeding that? This is magick -version ...

After uninstalling 6.9.x and installing mageMagick-7.0.8-8-Q16-x64-dll.exe" I get this error now: D:\gigapan\Jerusalem_Gigapan\Python27>montage -define registry:temporary-path=/data/tmp -limit memory 8000mb -verbose -depth 8 -geometry 256x256+0+0 -mode concatenate -tile 127x *.jpg tiff64:stitchX ...

You are not running the latest release of ImageMagick. Type magick --version It should report version 7.0.8-8. If not, upgrade your release of ImageMagick and try your command again. What is the difference between ImageMagick-7.0.8-8-Q16-x64-static.exe and ImageMagick-7.0.8-8-Q16-x64-dll.exe? Which ...

After 8 hours of processing, now i'm getting this error: https://www.dropbox.com/s/ix69yh5qq3aohcp/Clipboard01.jpg?dl=0 A ton of these: montage: unable to open file `magick-16188shKu7TTUf-rE': Too many open files @ error/cache.c/WritePixelCachePixels/5942. then this: montage: too many exceptions ...

Well...i think we're getting somewhere. I don't know what you mean by filelist.txt, so i used *.jpg and it seemed to start to work. I had 150GB free when I started this. Do I just need to free up space or is there another issue with the cache I should know about? This is what I used: montage -define ...

That gives me this:

montage: unable to open image `@filelist.txt': No such file or directory @ error/blob.c/OpenBlob/2761.montage: missing an image filename `tiff64:stitchX.tiff' @ error/montage.c/MontageImageCommand/1795.

Thank you so much for your help!

Well, I installed ImageMagick-6.9.9-37-Q16-HDRI-x64-dll Tried this: D:\gigapan\Jerusalem_Gigapan\Python27\143766>montage -define registry:temporary-path=data/tmp -limit memory 8000mb -verbose -depth 8 -geometry 256x256+0+0 -mode concatenate -tile 127x @filelist tiff64:stitchX.tiff got this: montage ...

Your command works without complaint for us. We're using ImageMagick 6.8.10-9, the current release. We saved all the image file names to a file "filelist" to reduce the command line arguments size, then ran this command: $ montage -define registry:temporary-path=/data/tmp -limit memory 16mb ...

D:\gigapan\Jerusalem_Gigapan\Python27\143766>montage -define registry:temporary- path=data/tmp limit memory 8000mb -verbose -depth 8 -geometry 256x256+0+0 -mode concatenate -tile 107x @filelist tiff64:stitchX.tiff montage.exe: unable to open image `limit': No such file or directory @ error/blo b.c ...

Hmm. would limiting it to just 16mb exponentially increase the time it takes to process? it already takes hours. why not like 20GB?