Public bug reported:

In certain situations, enblend seems to just completely skip an image. So far 
it has only happend with an image on the bottom edge of the panorama, but who 
knows...
Messing around with the crop, resolution and what images to include changes the 
behavior, so it seems kind of random. Happens both with multithreading and a 
single thread.

This only happens in enblend 4.2, going back to 4.1.5 fixes the problem.
Not sure whether the fault is in Hugin (bad or out of date command line)
or in enblend.


Here is a zip file with files needed to reproduce the bug (I hope):
http://ajpanton.se/hugin_enblend_bugreport.zip
I've removed as many input files as possible to make it smaller and faster to 
process. That's why there's so much empty space in the output.

Steps to reproduce:

1a. Have Windows (tested on Windows 10, 64-bit).
1b. Have enblend 4.2 (tested both with the "official" build and the one 
included in 2016.2 beta, both x64).
1c. Have Hugin (testeed with 2015.0 and 2016.2 beta, both x64) with default 
settings.
2. Open the .pto file with Hugin.
3. Stitch.

The output will look like "output 4.2.JPG", with one input image
missing. enblend 4.1.5 does it correctly in "output 4.1.5.JPG"

** Affects: hugin
     Importance: Undecided
         Status: New

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

Title:
  enblend 4.2 bug

Status in Hugin:
  New

Bug description:
  In certain situations, enblend seems to just completely skip an image. So far 
it has only happend with an image on the bottom edge of the panorama, but who 
knows...
  Messing around with the crop, resolution and what images to include changes 
the behavior, so it seems kind of random. Happens both with multithreading and 
a single thread.

  This only happens in enblend 4.2, going back to 4.1.5 fixes the
  problem. Not sure whether the fault is in Hugin (bad or out of date
  command line) or in enblend.

  
  Here is a zip file with files needed to reproduce the bug (I hope):
  http://ajpanton.se/hugin_enblend_bugreport.zip
  I've removed as many input files as possible to make it smaller and faster to 
process. That's why there's so much empty space in the output.

  Steps to reproduce:

  1a. Have Windows (tested on Windows 10, 64-bit).
  1b. Have enblend 4.2 (tested both with the "official" build and the one 
included in 2016.2 beta, both x64).
  1c. Have Hugin (testeed with 2015.0 and 2016.2 beta, both x64) with default 
settings.
  2. Open the .pto file with Hugin.
  3. Stitch.

  The output will look like "output 4.2.JPG", with one input image
  missing. enblend 4.1.5 does it correctly in "output 4.1.5.JPG"

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

_______________________________________________
Mailing list: https://launchpad.net/~hugin-devs
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp

Reply via email to