snibgo
snibgo
The source code in xcf.c (https://github.com/ImageMagick/ImageMagick/blob/main/coders/xcf.c) says: ``` /* BOGUS: we don't write these yet because we aren't reading them properly yet :( image->resolution.x = xres; image->resolution.y = yres; */...
For me, v7.1.0-42 on Windows 8.1, the command ... ``` magick sbucks.png x.png ``` ... where sbucks.png is the OP input (377705 bytes) makes an output 985806 bytes. Exiftool says...
Yes, but the input file has no alpha, 256 unique colours, with palette. So the problem isn't the PNG format, but a restriction within IM.
The input file that I have called sbucks.png has transparency. One of the 256 entries in the palette is (90,89,102,254). IM reads the file with no problem. But IM can...
"info:" tells us that frames have different sizes with offsets ... ``` f:\web\im>%IMG7%magick original.webp info: original.webp[0] WEBP 80x80 80x80+0+0 8-bit sRGB 30170B 0.000u 0:00.001 original.webp[1] WEBP 32x36 80x80+6+16 8-bit sRGB...
Those files are too large for me to download. How many pixels do they have? How much memory does your computer have? I suspect you are running out of memory....
IM needs to store the entire image in memory. If not enough RAM is available, it will use disk. 69536 * 22230 pixels, assuming three channels, 4 bytes per channel,...
> magick convert androm.psb androm.png -limit memory 1MB -limit map 1MB That would limit the memory (RAM) usage *after* reading the PSB and writing the PNG. I suggest doing it...
`magick convert` will read the command assuming IM v6 syntax. Plain `magick` will assume v7 syntax. V7 is better than v6. I suggest that `magick convert` should *only* be used...
> Should I try a larger file ...? See my calculation above: > 69536 * 22230 pixels, assuming three channels, 4 bytes per channel, needs 18.5 GB of memory.