I think, that it should not use entire memory 12Gb at once. The algorithm should be aware that there are machine limitations and should not allocate all possible memory even if the size of canvas is absurdity. For me the correct behaviour would be allocating less memory and freeing it when done, doing things at steps. Also if this is not possible, then at least there should be a confirmation dialog, "Do You really want to do that ... or You wanted this..." and then choose. Anyway much better solution would be fixing algorithm then interface if possible.
On Oct 10, 10:37 pm, Bruno Postle <[email protected]> wrote: > It is a bug (because Hugin should stop you from doing this), but > also the correct behaviour for what you are asking Hugin to do. > > The Assistant resets the pixel dimensions of the canvas to best fit > the data. In particular it ensures that the canvas is big enough to > represent all the detail without any part being downscaled. > > A 350° wide stereographic panorama probably really does need to be > rendered with hundreds of gigapixels, otherwise the middle section > has much less detail than the original photos - You really don't > intend to lose information do you? > > If you ever did manage to stitch this enormous file and zoomed in to > the middle at 1:1, then you would find it was just about right. > > Alternatively if you set the canvas size to something practical > before stitching, then zoom in to the middle, you will find that > everything is far too small with significant aliasing artefacts. > > -- > 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
