On Tue 07-Dec-2010 at 02:54 -0800, Olivier Croquette wrote:
resolution needs to be by factors higher, plus there are 12 times more input pictures, so the size of the final picture is not manageable by home computers. To solve this, Hugin would have output tiles of the big picture instead of a single file, without loading the whole in memory. I could imagine this requires quite some design changes.
There is a 'gigatile' tool which uses the Hugin cropping feature to render the output as multiple 4096x4096 tiles: http://search.cpan.org/dist/Panotools-Script/bin/gigatile
It also generates a JPEG pyramid for viewing with the Google Maps API, but you don't need this bit (and it would be nice if someone fixed it to use OSM rather than Google Maps).
-- 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
