[ptx] hugin has problems with particular imageset

[Rich]

well, this method unfortunately doesn't work in some cases when image is 
heavily moved upwards (or possibly, downwards) - it just gets clipped.

also, button for fitting the resulting image changes nothing in such a case

manouchk wrote:
> Le Jeudi 25 Août 2005 03:51, Rich a écrit :
> 
>>pablo.dangelo at informatik.uni-ulm.de wrote:
>>
>>>Zitat von Rich <rich at hq.vsaa.lv>:
> 
> there is a preview window made for this. In that preview window there are 2 
> buttons that helps you center and adjust field of view.. (to center well the 
> pano you have to specify a picture that is near the center as a reference 
> picture...)
..
>>>This is a very big image, 491 Megapixels. A single remapped image of the
>>>entire panorama requires
>>>31570*15580 * 4 = 1.8 GB. Nona might need 2 times the output image size
>>>in TIFF_m mode, so this is up to 2.6 GB. A future version will be much
>>>more memory efficient. Remember that on a 32 bit processor, each process
>>>can only access up to 2 or 3 GB, no matter how big your swapspace is.
>>
>>i finally managed to stich this panorama. the reason why image was so
>>big was that hugin for some reason left a very big empty space below all
>>images - the problem also mentioned on this list several times.
>>
>>usually i can significantly reduce that space by changing horizontal
>>control point pairs, but this time i was not able to do so.
>>
>>anyway, after cropping it in gimp to the furthest edges it was reduced
>>to 31184x3615
>>
>>so ability to crop output (probably in preview window ?) would help in
>>cases when resulting images are too large because of empty space added.
-- 
  Rich