On Fri 22-May-2009 at 21:00 -0700, Michael Witten wrote: >Does nothing besides Hugin and its ilk deal with cropped TIFFs properly?
cinepaint is ok, the Gimp is fine when the TIFF is multilayer, I seem to remember recent versions of ImageMagick are ok too (though I may be wrong). It's a valid and useful part of the TIFF spec (and PNG too), so fixing Gimp would be a generally useful thing to do. >Besides noticing that you called the output 'junk' ;-P (that is, :-D) That is just a reminder to myself to delete the file. >, I noticed that your output has a lot more of the pond than it >*should* have. I was utterly confused until I realized that the >image pixel data is completely available--it is only made >transparent by the alpha data (how does unassociated alpha fit in >to this?) This is a (minor) bug in enblend, although it respects the alpha channels for placing seams, the RGB data of the first image is used as background for the panorama as a whole (or something like that). >I'm not sure why forcing more levels in the pyramids is able to >deal better with my narrowly overlapping regions. Why is this? Does >it force a larger region of pixel data to be used automatically? Yes, with one level the seam is two pixels wide and you get a harsh blend, with two levels it's four pixels, with three levels it's eight etc... -- Bruno --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
