You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a PNG with a lot of of XMP metadata (8MB+). After removing some of the metadata using Adobe XMP Toolkit I get the following exception:
Unhandled Exception: ImageMagick.MagickCoderErrorException: iTXt: chunk data is too large `E:\images\blank_after.png' @ error/png.c/MagickPNGErrorHandler/1711
Here is a link to the file that is used prior to removing XMP metadata:
And a link to the file after the removing the XMP metadata.
I am able to open the file using Adobe Photoshop and other image editors.
Adobe XMP Toolkit does not reduce the file size after removing metadata, I wanted to open / save using Magick.NET to reduce the file size.
Sorry for the late response but I completely forgot about this issue.
It looks like you are running into a limit inside the libpng library. The size of your iTXt chunk is larger than that limit. At this moment we have no method to change/remove this limit but I will try to add that later this week. I was about to publish a new release but I will wait with that and add this feature to ImageMagick (and Magick.NET) first.
Hi,
I have a PNG with a lot of of XMP metadata (8MB+). After removing some of the metadata using Adobe XMP Toolkit I get the following exception:
Unhandled Exception: ImageMagick.MagickCoderErrorException: iTXt: chunk data is too large `E:\images\blank_after.png' @ error/png.c/MagickPNGErrorHandler/1711
Here is a link to the file that is used prior to removing XMP metadata:
And a link to the file after the removing the XMP metadata.
I am able to open the file using Adobe Photoshop and other image editors.
Adobe XMP Toolkit does not reduce the file size after removing metadata, I wanted to open / save using Magick.NET to reduce the file size.
Looks like a dup of #105.
I am using Magick.NET-Q16-HDRI-AnyCPU 7.4.6.0
The text was updated successfully, but these errors were encountered: