Hello,

I've documented my problem in the following tarball:

    http://rapidshare.com/files/235284536/problem.tar.bz2.html
    MD5: 727BAE9EF9F93CDD64215BE01E704CD5

Here is the associated README.sh:

#!/bin/bash

# I used tif2svg/inkscape to create the seams by hand and then enblend-svg
# to create the blendable images, of which {05,09,10,11}.tif are a selection.
#
# The scene involves the Sun, which I've decided I want to be a white 'hole'
# in the final panorama. However, just clipping out the region in inkscape is
# not enough, because enblend will leave hard edges---it doesn't like to blend
# unless non-transparent pixels overlap.
#
# The obvious solution is to add another picture---one that is just white and
# cut the seams appropriately in inkscape. Unfortunately, I've run into 2
# problems:
#
#  * I wanted 11.tif to provide the white area with which {05,09,10}.tif
#    could be blended nicely. However, enblend gives up when the pixels
#    are white, saying that 11.tif is grayscale while the other input
#    images are color. After searching online, I've concluded that this
#    is likely the fault of ImageMagick, which tries to optimize for space:
#    finding that there is only white pixel data, it creates a grayscale
#    tiff rather than an RGB tiff.
#
#  * As an experiment, I converted the white area into a yellowy area
#    in the hope that it would bypass the first problem. Fortunately, it
#    works, but emblend itself misbehaves: The golden area is shifted up
#    in the image and blended with the wrong parts. The behavior is utterly
#    bizarre. I ended up opening {05,09,10,11}.tif in GIMP and then copying
#    them all into one image (in that same order): The result is the image
#    05_09_10_11.png, which clearly shows that everything should match up
#    perfectly. WTF is going on?
#
# Use this to build the panorama and see for yourself:

enblend --fine-mask -o pano.png 05.tif 09.tif 10.tif 11.tif

# The `--fine-mask' handles the thinly overlapping seams that I have created;
# without it, I've experienced some horrendous artifacts such as completely
# blackened regions.

I'm currently using enblend 3.2 (CVS HEAD segfaults).

Sincerely,
Michael Witten


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~----------~----~----~----~------~----~------~--~---

Reply via email to