#380 graphicsmagick file size limitation?

[danielfleming]

I have an app that does file conversion to JP2 using graphicsmagick. For some reason graphicsmagick complains about certain images, but I cannot identify what the issue is. I was wondering if there is a max file size that is preventing it to convert? I couldn't find this in the documentation. The source files are uncompressed TIF images, 450 DPI and are fairly large. Thanks!

[Bob Friesenhahn]

On Wed, 6 Apr 2016, danielfleming wrote:

I have an app that does file conversion to JP2 using graphicsmagick. For some reason graphicsmagick complains about certain images, but I
cannot identify what the issue is. I was wondering if there is a max file size that is preventing it to convert? I couldn't find this in
the documentation. The source files are uncompressed TIF images, 450 DPI and are fairly large. Thanks!

GraphicsMagick uses the Jasper library to read/write JP2.
Unfortunately, the Jasper library was coded using 32-bit data types
which can work on any modern computer and did not do anything special
to support large files (not even improving its capability in 64-bit
applications). A more modern alternative called OpenJPEG (not yet
supported by GraphicsMagick) also has problems with large files. It
is necessary to turn to proprietary software in order to deal with
large JP2 files.

It is possible to interface proprietary command-line oriented software
(e.g. Kakadu) with GraphicsMagick using its configurable delegates
subsystem (configured via the delegates.mgk file).

[Bob Friesenhahn]

This is not an issue that we can fix. When we add support for OpenJPEG it may or may not help with the maximum image size issue. The maximum image size that Jasper can support (unknown to me but surely less than 2GB of raw pixel data) is likely dependent to some extent on the image data since it is implementing a compression algorithm.