Removing the orphaned groups or adding control points to connect them fixed the problem, and I have both rendering now, they will look great. So it was entirely the disconnected groups which were causing the issue in both projects. Thanks! I tend to leave the control points in exposure brackets as it will provide more control points in blown out or shadow areas. And generally, I've not had issues with optimization taking too long. I guess the change is in the way I do things.
Using the quick preview, its very obvious when you have multiple image groups. But I rarely use that any more. I just need to pay more attention to this. -- Bob On Monday, March 2, 2015 at 5:02:00 PM UTC-5, Tduell wrote: > > On Tue, 03 Mar 2015 04:26:04 +1100, T. Modes <[email protected] > <javascript:>> wrote: > > Having pondered a bit on this project, I came to a similar conclusion. > I would reckon that a good approach for a project of this size (number and > > depth of stacks), would be to pre-align each stack (align_image_stack), > which with a bit of shell scripting magic could make use a bit of parallel > > processing, then align and stitch the stacks linked by position. > This is something which might be better done within hugin, and would be > good GSOC project if we can ever get back into that. > > Cheers, > -- > Regards, > Terry Duell > -- 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/ae7a7e1b-5ea3-4ebe-adb2-a1ae142ff231%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
