Looks like there are some problems with the seam generation in Enblend that
can lead to some of the problems you are seeing. Try turning off seam
optimisation to see if that helps (
http://enblend.sourceforge.net/enblend.doc/enblend_4.2.xhtml/enblend.html#sec%3Amask-generation-options).
To isolate the problem, you can generate the remapped images in Hugin and
save them, then run Enblend separately with different options. You can also
run different image blenders on the remapped images to see what works.
You also want to try generating HDR (e.g. EXR format) files from your
exposure stacks first before stitching them in Hugin. I've used this method
previously with success.
Daniel.
On Sunday, 12 May 2019 05:14:19 UTC+1, Albert Szostkiewicz wrote:
>
> Thanks for suggestions!
>
> Same set of photos without any intervention in different program works
> like a charm out of the box and stitches 100% correct HDR pano.
> Just trying to understand, whenever it is a limitation of Hugin or a
> design that would require user in-depth knowledge of different algorithms
> that need to be used to get this result (if possible?)
>
> [image: pano_ssies.jpg]
>
>
> Hey @Matija ! I have tried wider lenses but I am happy with sharp quality
> result of 16mm fisheye. Other software deals with it without issues, but I
> am trying my best to give Hugin a shot as it is (to my knowledge) only
> Linux pano tool that could be scripted
>
> Thanks once again!
>
> On Saturday, May 11, 2019 at 6:56:52 AM UTC-7, Matija Kogoj wrote:
>>
>> Many of us have the same problem. In my experience it seems to be related
>> to Enblend blender.
>> Switching this to Verdandi ("builtin") option in the stitcher tab
>> (advanced and expert modes) might help. The result will not be perfect; in
>> my case there were often visible seams left over, but it generally changed
>> the output.
>> Khan deghosting takes a f**kton of time; avoid it.
>>
>> At the following link you can read about my latest conversation about
>> this, and all the accompanying notes:
>>
>> https://groups.google.com/forum/#!searchin/hugin-ptx/exr$20breaks%7Csort:date/hugin-ptx/b9qM0oQKZuk/mK6t9eTSCwAJ
>> I should note that what solved the issue then does not work in my latest
>> batch. I believe it is due to high parralax more than .
>>
>> For your case I would like to summarize two points:
>>
>> 1. if the photometric calc returns too many grey values *(30+ stops)*
>> you will probably have black holes ("gaps" in my text). You should expect
>> a
>> certain amount of EV levels and watch for breaches of that number. I have
>> noticed this usually influences the next point.
>> 2. if the stitching takes a long time or hangs at certain points the
>> panorama will probably be broken. Usually the worse it is the longer it
>> takes. Here it helps to look at the log output and expect relatively
>> regular progression in stitching and calculating new views. If it takes
>> 30
>> minutes to calculate 1 picture you are either working for NASA or you can
>> press cancel. ← exaggeration, use your own metric.
>>
>>
>> I use a circular fisheye and make 5 views by 6-10 exposures for
>> equirectangular exr output. In best cases the whole process took less than
>> an hour including corrections.
>>
>
--
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 hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/81e6921d-f32f-4b22-bafb-da96b5ffc9ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
