Oh man, you sent me in the wrong direction. The stacks show clearly the same gaps as the final image. So there are 2 issues: The first one is the blender
Am Mittwoch, 12. Dezember 2018 22:35:08 UTC+1 schrieb Matija Kogoj: > > Enblend > https://www.dropbox.com/s/0pfxi7gkpidwap9/A3_exr_Enblend.JPG?dl=1 > > Enblend with NFT: > https://www.dropbox.com/s/behos2r38ru0vze/enblend_nft.JPG?dl=1 > Enblend with NFT is ok (and all with the internal blender). The gaps are already in the merged HDR stacks. These gaps are caused by a combination of 2 factors: By default Hugin is looking at the overlap to determine with images belongs to one stack. With the high overlap between 2 stacks in your project these images from 2 shooting stacks will be merged into one (output) stack. The assigned stack numbers will be ignored by default. See https://wiki.panotools.org/Hugin_Stitcher_tab Now a second issue adds it contribution. Under HDR merge option the option "-c consider only pixel that are defined in all images" is activated. These 2 aspects together result in the gaps. To solve this switch to expert mode, go to photo tab and select grouped by output stacks. Under "Minimum overlap" say -1 to use your assigned stacks. (I will extend the tooltip for this input field.) Maybe when the issue with the gap is solved the blending issue is also solved, because there are now other seams. -- 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/53fcb082-ddf1-4822-a438-7a8780bfa0cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
