Questions and postings pertaining to the usage of ImageMagick regardless of the interface. This includes the command-line utilities, as well as the C and C++ APIs. Usage questions are like "How do I use ImageMagick to create drop shadows?".
...the RAM usage maxes out (16gb), rendering the computer useless during the operation. After waiting 5 minutes, I ended the command (ctrl+c). I have yet to successfully convert these large multipage tiff files.
Any ideas?
Running ImageMagick-6.9.2-Q16 on Windows 7 (same issue with PowerShell & CMD prompt)
Sounds like you are running out of RAM. The whole 700 page TIFF file must be loaded into RAM. Do you have enough RAM? If not, then you need to use disk for RAM. See
It should then work, but may take quite some time to read and write 700 pages of the file. If you have any doubts, then post your TIFF file to some place such as dropbox.com and put the URL here so we can test and see if the file works or is corrupted.
If you want to test the file, then just read the image and save just the first page, but it still may take some time to read all the pages:
Thank you for your help. I apologize but I am unable to share the document, it's IP belonging to my employer. I am hoping to use ImageMagick to "revolutionize" how we handle these documents.
I was able to successfully and quickly produce single page .tif & .pdf using convert. I also selected different pages, no issues...however I get this odd message:
This field is made up of a set of 32 flag bits. Unused bits must be set to 0. Bit 0 is the low-order bit.
The specification defines these bits:
Bit 0 is 1 for 2-dimensional coding (otherwise 1-dimensional is assumed). For 2-D coding, if more than one strip is specified, each strip must begin with a 1-dimensionally coded line. That is, RowsPerStrip should be a multiple of Parameter K, as documented in the CCITT specification.
Bit 1 is 1 if uncompressed mode is used.
Bit 2 is 1 if fill bits have been added as necessary before EOL codes such that EOL always ends on a byte boundary, thus ensuring an EOL-sequence of 1 byte preceded by a zero nibble: xxxx-0000 0000-0001.
So I would guess the tif file is not in a format Imagemagick likes. You could try generating the tif with some other software and see what you get.
I suppose this could be an indication of the problem: Options for Group 3 Fax compression
The warnings are not errors. They just identify that IM does not recognize some custom tag in the file. You can avoid getting the messages by adding -quit right after convert and before the input image.
Looks like the file works fine. I suspect it is just taking longer to process all 683 pages than you might think in terms of reading them all in and writing them all out