On Saturday, January 22, 2022 at 3:57:29 AM UTC-5 T. Modes wrote:
> > This is not so trivial. The current implementation keeps the full scaled > image in memory. So a 800 % zoom will require several GB of RAM only for > the cp tab. > In my initial testing of the feature, something fails badly as soon as the rescaled image is larger than 2Gb. I expect that means some code is using an int instead of correctly std::sizet to store the number of bytes in the image. I would have been less surprised at misuse of an int for the number of pixels in an image. But the number of pixels is much smaller. I'll try tomorrow to find the exact spot in the code that goes wrong. I'm a bit surprised no one has worked with an image that gets this large even at 200%. My image needs well over 400% to get over 2Gb, but mine was taken with a cheap phone. -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/83e50370-911b-47d0-a685-7c5546bb1450n%40googlegroups.com.
