hugin-devs team mailing list archive

[Yuv <685893@xxxxxxxxxxxxxxxxxx>]

versions prior to 4.0 had a completely different algorithm.  If there
was one mistake in the move from 3.x to 4.x, it was that the 4.x
algorithm *replaced* the 3.x algorithm instead of complementing it (with
an option to choose which one to run).

the current GSoC project on Enblend is adding modularity to enable
multiple seam placement algorithms under the same code base.  It will
bring a new challenge (how to determine which one of the multiple
choices of seams is the best one?) that is already being thought of.
Maybe it is also an opportunity to resurrect the old 3.x algorithm as
one of the many options - one that is obviously superior in the cases
that trigger this error.

as for the deliberate nature of the "questionable" behavior, have you
tried to change the arbitrary threshold and see what happens?  the
changeset linked in comment #4 is very well documented.  set
overlap_threshold to 0 and run a test case against a recompiled version
of enblend.  please report interesting results here.

-- 
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