hugin-devs team mailing list archive

[Christoph Spiel <cspiel@xxxxxxxxxx>]

You supplied three input images to Hugin, namely
"_1020988.jpg", "_1020989.jpg", and "_1020990.jpg".  As they
stand, they are _not_ suited for input in Enblend, because neither
are they aligned, nor do they have an alpha-channel.

   To track down a problem, we need input image sets suited for
Enblend.  Nothing else matters in this bug tracker.

I created a Hugin project out of _10209*.jpg.  Aligned, remapped,
cropped to rectangular, and created three TIFF-files:
    $ identify *.tif
    image0000.tif TIFF 787x987 787x987+24+22 8-bit DirectClass 1.875MB 0.000u 0:00.000
    image0001.tif[1] TIFF 783x987 783x987+442+22 8-bit DirectClass 1.832MB 0.000u 0:00.000
    image0002.tif[2] TIFF 773x987 773x987+829+22 8-bit DirectClass 1.786MB 0.000u 0:00.000
Running Enblend on them
    $ ./enblend image000[012].tif
resulted in the neatly aligned and definitely sandy panorama "a.tif".

No problems encountered.

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

Title:
  Enblend 4.0 output better than Enblend 4.1

Status in Enblend:
  New

Bug description:
  When running enblend 4.1 from PTAssembler 6.0, the preview is correct.
  However, the output image generated by Enblend 4.1 has black areas in
  the image. These areas can be different when rerunning the blend.

  Attached are a screen shot of the preview, the panorama generated via
  enblend 4.0, and two panos generated with Enblend 4.1.

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