Dear Hugin users, I´m working with thermal single band aerial images and have been trying to create mosaics with hugin using manual control points and attitude information (yaw,pitch and roll), the result seems ok, but when i tried to create the mosaic it gives me an error related with image format. Here (https://www.dropbox.com/sh/r1w22ps0aammxyi/j1hVquoSfd) is the log file with error description,project file (.pto) and a sample TIFF image.
What should be the format of my images so hugin doesn´t have problems to work with? Any help would be very appreciated, thanks! Inti El viernes, 9 de noviembre de 2012 10:14:44 UTC-6, Julien Schroder escribió: > > Thanks for your answer > I use FLIR thermal imagery, my TIFF are extracted from a video sequence > recorded by plane by this thermal camera. > So basically my Tiff is displaying floating values such as temperature in > one band. > I might be able to create a 16 bit rgb tiff and store the temperature in > one of the band, the problem is that for the moment hugin doesn't accept it > (it crashes). > I don't really know what is the kind of 16 bit tiff structure that hugin > is expecting > Thanks > > Le vendredi 9 novembre 2012 02:52:19 UTC-9, dex Otaku a écrit : >> >> Salut alouest, >> >> On Thursday, 8 November 2012 14:01:32 UTC-6, alouest wrote: >>> >>> 'm using a sotware which can export RGB tiff and 32 bit tiff. I can >>> produce panoramic with hugin of the RGB but not of the 32 bit tiff. >>> If I extract both RGB and 32 bit tiff, then I create my panorama from >>> the RGB pictures and save the project file. >>> Would I be able to use all the settings (and control points, >>> basically everything) used before and apply them to my 32 bit tiff that >>> hugin see totally blank? >>> I tried quickly with nona but it crashed. >>> >>> To summary could hugin or another tool could apply the settings from a >>> working panoramic creation into empty tiff (they off course have the exact >>> same extent). >>> >>> Is that crazy or that could work? >>> >> >> To my knowledge, Hugin and its included tools only work with TIFF images >> that: >> * use 16 bits per colour channel or less [no 32bpc TIFF, no floating >> point TIFF], >> * are RGB or RGBA [no CMYK support], >> * use only a single image layer [no multi-layers TIFF support], >> * and must be <4GB in file size [a limitation of base-standard TIFF] >> >> What are you using that creates 32-bit [I assume that's per colour >> channel] output? HDR images from something? >> >> Is there a practical reason to maintain that bit depth as far in your >> processing chain as Hugin? Chances are, even if you're going to be >> post-processing the images after stitching, 16 bits per channel will be >> sufficient. >> >> My suggestion [which is probably your only option with Hugin, Nona, >> etc.]: reduce the bit depth of the images to 16bpc or less and use those >> with Hugin. If you require >16 bit per channel image support, you may need >> to find other tools to use. >> >> Cheers, >> D >> > -- -- 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 --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
