Trouble with large pano images and plug-ins (e.g., Topaz)

[dangelic0]

I see I can create 40,000x40,000 pixel images in PSP X9 (I am running 64-bit Win 10). But trying to send anything through to a Topaz plugin greater than 32,767 pixels results in an infite loop, whereby the PSP process uses up all the available hard drive space until it crashes (or I abort via task manager). It creates some massive files in <user>\AppData\Local\Temp\boost_interprocess_* until all space is exhausted.

Anyone know if this is a PSP issue or perhaps a Topaz issue? I would guess Topaz. I did contact their tech support but no reply yet. Interesting to note that 32,767 pixels works but not 32,768. This limit is of course 2^15 - 1. So the interface is dependent on a signed 16-but number for the image dimension. Sad really

Appreciate your insights
Thanks
Dean

[dangelic0]

Here is what Topaz said in response to my inquiry:

"The largest resolution that InFocus can reliably handle on the widest edge is 8,000px wide. I would suggest editing your image one section at a time if it extends beyond this width."

This is not really consistent with my own experience. I have been able to get the Topaz InFocus plug-in to work on larger images than 8000 px on a side. Perhaps that is all they test and support.

Nor is their suggestion suitable really. Processing images in separate pieces and then stitching them back together almost always leaves artifacts. Sure thy can be smoothed but I am trying not to make work here.

The 32,767 image size limit is true; likely due to the interface from PSP to its plugins. Bizarre that a 64-bit application would use a signed short (16-bits) to pass the image dimension to a plug-in. At least if they had used an unsigned short it would have provided images with size up to 65,535!