Enblend --no-optimize produces black holes into panoramas

Bug #785803 reported by Janne on 2011-05-20
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description


How it should look:

Win7 x64 w/ 32bit and x64 Hugin 2011.1 RC1 (2011.0.0.8f1447ab8649 built by Matthew Petroff), multithreaded Enblend. Project contains less than ten fisheye images encompassing the whole panosphere, so it's your average spherical panorama. You can see how much the images overlap here: http://i.imgur.com/KuAqU.jpg I think the issue could be related to too small overlap between images.

Felix Hagemann (flixh) wrote :

I am moving this to the enblend bug tracker.

affects: hugin → enblend
Felix Hagemann (flixh) wrote :

The result looks identical to bug 766501, although this "image is black" phenomenon is triggered there by --fine-mask.

Janne (jannefoo) wrote :

Actually, using --fine-mask with --no-optimize works correctly.

Bruno Postle (brunopostle) wrote :

This is a bug I've seen lots of times, but this is without the --no-optimize parameter.

I usually find that it goes away if I rearrange the order of photos in the project, or rotate the scene slightly to give the blending a different geometry.

Can you upload the .pto project as a test case? Since it shows the bug without seam optimisation it might be useful tracking it down.

Janne (jannefoo) wrote :

Example .pto attached.

Bruno Postle (brunopostle) wrote :

Unfortunately I can' t reproduce with this .pto project and dummy photos.

Felix Hagemann (flixh) wrote :

If I remove the --fine-mask option and process the pto with dummy images I can reproduce the problem in each of the 5 exposures.

Changed in enblend:
status: New → Confirmed
Bruno Postle (brunopostle) wrote :

I can reproduce the bug, everything is ok with --fine-mask, but the artefacts appear in practically every image pair of this project when it is not set (even though the images are blank and --no-optimize is set).

I'll attach a small test case with two images, this command shows the problem in the output:

  enblend --no-optimize -o output_bad.tif project_exposure_layers_0006.tif project_exposure_layers_0010.tif

Christoph Spiel (cspiel) wrote :

Check out rev 6d6c88dcdc63 or later. Keep optimization
switched off and -- at your discretion GraphCut -- to get
reliable results.

Christoph Spiel (cspiel) on 2013-12-17
Changed in enblend:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers