Thank you both! Monkey - your guess was spot on. Adding that blend-colorspace option got it working. I also tried adding mutliblend, and got it to generate a stiched image as well, although at least for now the enblend version is better because it preserved the ICC profile, which multiblend appears to have discarded. Theoretically I can add it after the fact, but that brings me to the second problem I discovered...
...and I think already answered by Bruno. I *just* tried to open the stiched image in GIMP to mess with the color settings, and was getting an error about the height being out of range. I couldn't figure out why, but I suspect it has to do with the canvas size issue you pointed out. Now that I know what to look for, let me fiddle with the settings a bit and see if I can fix that. I have one additional question, if you don't mind - the stiching came out well, but the blending is off. Here's a much smaller version of the stiched image for reference: https://boxdog.legroom.net/public/ffmap-example.jpg Note that the left column is darker than the rest. The source images aren't like that - they're uniformly blue. I suspect it's those dark splotches, I guess some kind of oil or water stains, that's throwing off the blending. Is there any reasonably straightforward way to tune that to get the original brighter blue across the full image? Both enblend and multiblend produced similar results. Thank you so much for the help so far. On Tuesday, April 6, 2021 at 3:32:23 PM UTC-5 [email protected] wrote: > On Mon 05-Apr-2021 at 19:40 -0700, Jared wrote: > > > >enblend: > > >/tmp/portage/media-gfx/enblend-4.2.0_p20161007-r1/work/enblend-4.2.0_p20161007/src/fixmath.h:487: > >double enblend::PyramidScale<PyramidIntegerBits, > >PyramidFractionBits>::scale_lightness_for_pyramid(double) const [with int > >PyramidIntegerBits = 9; int PyramidFractionBits = 7]: Assertion `result >= > >0.0' failed. > > >I tried multiple times but always get the same error. The images are > >large, about maybe 300 MB TIFFs (x8) when uncompressed, so I thought maybe > >I was running out of RAM or disk or something, but I have 32 GB of ram and > >still had 14.5 GB reported free when running in a 1 second loop the last > >time it failed. Disk also looks good. > > The error is new to me, but looking at your project, although the > crop area is a reasonable 32600x21922 pixels, the panorama canvas is > 53210x1061398 (which is 50+ gigapixels). > > I would try reducing the canvas area, as it is possible the big > offset numbers are confusing enblend, click the Fit button in the > Preview window or Calculate Field of View in the Stitcher tab (which > does the same thing). I would also use Calculate Optimal Size in > the Stitcher tab, and centre the output in the panorama using the > Drag tool. > > Attached, a more modest 680 megapixel version of your project. This > should be ok, if it isn't then there some problem with the images > themselves. > > -- > Bruno > -- 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/e2e2b431-c7e9-4509-a07b-edfcff2c8a0dn%40googlegroups.com.
