[email protected] schrieb am Samstag, 5. Februar 2022 um 14:49:42 UTC+1: > Yes. That does work. I was intending to do something that works much > better than that. I wanted the feature committed before I start on the > performance increase.
Don't rely on to be written code. Nobody knows which code you will write - and if this code will work at all. So this is step 1 - write the optimized code - and the code using the optimized code is step 2 and not vice versa. > > At 3 bytes per pixel, and applying to just two of the input images, not > the whole panorama, I didn't think memory was the issue I should be > worrying about. > A memory usage of *several* GB is always something to worry. -- 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/a5d9e968-b629-47bc-ab8d-ecbdf84b90c8n%40googlegroups.com.
