hugin-devs team mailing list archive

[Erik Krause <685893@xxxxxxxxxxxxxxxxxx>]

This might or might not be true, I can't judge. However, the comment to
patch
http://enblend.hg.sourceforge.net/hgweb/enblend/enblend/rev/5c2c0a81fcb3
says: "Prevent enblending of the "same" image. Sometimes a user tries to
feed images to Enblend that are meant to be the input to Enfuse."
Christoph Spiel emphasized this same reason in a personal mail to me.
All this doesn't sound as if the algorithm required the change.

To summarize: 
- The mentioned error message does not appear in any case it should appear as shown in a test case. 
- Enblend runs on 100% overlapping images without troubles. 
- Stopping the program without output is a major annoyance at this stage of processing.

I think this are enough reasons to raise the importance from "wishlist"
to medium or even high, especially since the fix looks easy: simply
remove the above mentioned patch.

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685893

Title:
  arbitrary stop errors because of excessive overlap

Status in Enblend:
  Confirmed

Bug description:
  Sometimes enblend stops with error code 1 and a message "excessive
  overlap detected; remove one of the images". This behavior is
  arbitrary. F.e. a test project with 8 images all in the exact same
  place on an equirectangular canvas doesn't cause the error. The
  message is probably related to
  http://enblend.hg.sourceforge.net/hgweb/enblend/enblend/rev/5c2c0a81fcb3

  enblend versions prior to 4.0 used to warn on redundant images and in
  fact version 4.0 still does f.e in case of the above mentioned project
  with 8 images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/685893/+subscriptions