hugin-devs team mailing list archive

[rew <721136@xxxxxxxxxxxxxxxxxx>]

I used to have the strong impression that it was the image_cache that
caused this... Now you are contradicting that feeling.....

If you manage to change the configuration (yes/no openmp ...  yes/no
imagecache) and isolate the cases where it happens, that would help
locate the problem.

Keep in mind that the size of the stitched images matters. And the
limits might differ from configuration to configuration. So if you
disable openMP your 500Mpixel stitch might suddenly work, because the
limit for the bug to appear moved from 400Mpixel to 600Mpixel in that
configuration, and not because openmp actually causes the bug.

So, even in this stage there are debugging challenges.

>From there, try to "dump" the current in-memory  images to see where
things go wrong. I expect an unintialized pointer or buffer overrun.

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

Title:
  enblend creates an unexplainable black area.

Status in Enblend:
  Confirmed

Bug description:
  enblending       http://prive.bitwizard.nl/t80001.tif
  and                  http://prive.bitwizard.nl/t80003.tif
  results in          http://prive.bitwizard.nl/t8a.tif

  I cannot say I expected that black triangle in the output. My enblend
  was pulled from hg this morning (no changes) and built without
  imagecache or openMP. (imagecache causes corruption of the output
  similar but different to this. )

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